Skip to main content
You can connect Hi Doctor to Cursor by adding the server URL https://mcp.hi-doctor.ai/mcp to an mcp.json file and signing in on hi-doctor.ai. Cursor supports remote MCP servers over Streamable HTTP with OAuth, so no API key or header is needed. Its agent can then read your consultations, messages and journal, and prepare actions for your approval. Last reviewed: 2026-11-04 Sign-in and approval are the same as in every client; see Connect.

​
Who is Cursor useful for?

Cursor suits patients who already work in it every day and want to check a consultation, read a message from the medical team or log a weight entry without switching apps. It also suits developers testing how an agent behaves with the Hi Doctor tools before building on Streamable HTTP.

​
Add the server

Add Hi Doctor to an mcp.json file. Use .cursor/mcp.json in a project to make it available in that project, or ~/.cursor/mcp.json to make it available everywhere.
mcp.json
Do not add headers, API keys or client credentials. Cursor discovers Hi Doctor’s sign-in endpoints and registers itself automatically. Sign-in tokens are stored by Cursor, never in mcp.json, so a committed .cursor/mcp.json should contain only the server name and URL, as above.

​
Sign in and enable tools

1

Open Customize

Open Customize in Cursor’s sidebar and find hi-doctor among the MCP servers. Turn it on with its toggle.
2

Sign in

When Cursor asks you to sign in, your browser opens Hi Doctor’s sign-in page. Sign in and approve as described on Connect.
3

Use the tools

Cursor’s agent uses the tools listed under the server’s available tools when they are relevant. You can also ask for one directly, for example “use Hi Doctor to list my consultations”.
Cursor asks for your approval before it runs an MCP tool by default. Keep that on for Hi Doctor, especially for tools that send messages, submit a questionnaire, create a checkout link or delete journal entries. If you do not need Hi Doctor in a project, turn the server off in Customize for that project.

​
Troubleshooting in Cursor

  • Open the Output panel (Cmd+Shift+U on macOS) and choose MCP Logs to see connection and sign-in errors.
  • If sign-in completes in the browser but Cursor still shows the server as signed out, turn the server off and on again in Customize.
  • Other symptoms are covered on Troubleshooting.

​
Disconnect

Turn the server off, or delete its entry from mcp.json. See Disconnecting for how long access already issued lasts.

​
Sources

Checked on 2026-11-04 against Cursor’s Model Context Protocol documentation. Cursor also documents install links; Hi Doctor does not publish one. If a step differs, follow Cursor’s current page. If a step fails, see Troubleshooting.

​
Frequently asked questions

​
Do I need an API key to use Hi Doctor in Cursor?

No. Add only the server URL to mcp.json. Cursor discovers Hi Doctor’s sign-in endpoints and registers itself.

​
Should mcp.json be project or global?

Use .cursor/mcp.json for one project or ~/.cursor/mcp.json to make Hi Doctor available in every project.

​
Will Cursor run Hi Doctor tools without asking?

By default Cursor asks for your approval before it runs an MCP tool. Keep that on for Hi Doctor, and actions with consequences also need your approval on Hi Doctor.

​
Can I turn off Hi Doctor tools I do not need?

Turn the hi-doctor server off in Customize when you do not need it; Cursor documents server toggles, not per-tool switches.

​
Where do I see Hi Doctor connection errors in Cursor?

Open the Output panel and choose MCP Logs.

​
Next steps

Workflows

Common tasks step by step.

Patient tools

Every tool the agent can use with your account.
Ready to see a doctor? Start a consultation on hi-doctor.ai.