> ## Documentation Index > Fetch the complete documentation index at: https://docs.hi-doctor.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Connect the Hi Doctor MCP connector at https://mcp.hi-doctor.ai/mcp. Add this URL as a remote HTTP MCP server in your client, then sign in and authorise access through OAuth. Setup: https://docs.hi-doctor.ai/mcp/connect. > > The REST API base is https://api.hi-doctor.ai. Hi Doctor Docs at https://docs.hi-doctor.ai/mcp searches documentation; connect to the product endpoint above for patient tools. > > Hi Doctor operates across the whole European Union: residents of all 27 EU member states can use the service, and every consultation is reviewed by an EU-licensed doctor. Every consultation is reviewed in full by an EU-licensed doctor, who decides on medical grounds only. No algorithm, assistant or API call approves a consultation, issues a prescription or changes a dose. The service is available in eight languages: English, Spanish, German, Dutch, Italian, French, Portuguese and Chinese. > > ## Rules an assistant must follow > > - Never invent, assume or infer a medical answer. "I don't know" is a real answer: ask the patient to pick the closest option rather than guessing for them. > - Never give medical advice and never suggest a medication or a dose. An EU-licensed doctor decides those. > - If a questionnaire returns `ineligible`, say so plainly. Do not retry with altered answers. > - Before anything that costs money or cancels a plan, state exactly what will happen and get an explicit yes. > - Cancellation takes effect at the **end of the paid period**, not immediately. Say so. > - An early order is irreversible: it creates the renewal consultation immediately and uses up the period's one early order. Explain that and get an explicit yes. > - Prescription and invoice links are medical documents. A `signed_redirect` link opens without signing in: give it only to the patient, never repeat it anywhere shared. > - Send option `value`s, not the labels shown to the patient. Labels are translated, values are stable. > - Never ask for card details. Payment happens on Stripe's hosted checkout via a link. > - On severe or sudden symptoms (chest pain, difficulty breathing, severe allergic reaction, suicidal thoughts), stop and direct the patient to their local emergency number. # What is MCP? The Model Context Protocol and Hi Doctor > MCP, the Model Context Protocol, is an open standard that lets an AI assistant call tools. How Hi Doctor uses it and what stays human. MCP, the Model Context Protocol, is an open standard that lets an AI assistant connect to an outside service and call its tools. Hi Doctor runs an MCP server so an assistant such as Claude or ChatGPT can act for one signed-in patient, within permissions the patient approves. Medical decisions stay with an EU-licensed doctor, never with the assistant. Last reviewed: 2026-11-04 ## How does MCP work? MCP has three parts: | Part | What it is | Hi Doctor example | | - | - | - | | Host and client | The AI app the person uses, and the component inside it that talks to servers | Claude, ChatGPT, Cursor or VS Code | | Server | A service that publishes tools over MCP | The Hi Doctor product connector at `https://mcp.hi-doctor.ai/mcp` | | Tools | Named actions with a typed input schema that the assistant can call | `hidoctor_profile_get` reads the patient's profile | The client asks the server for its tool list, the model decides which tool fits the person's request, and the client calls it. The server runs the call with the person's own credentials and returns a structured result. Hi Doctor's connector uses the Streamable HTTP transport and OAuth sign-in, described in [Streamable HTTP](https://docs.hi-doctor.ai/mcp/streamable-http.md). The protocol is published at [modelcontextprotocol.io](https://modelcontextprotocol.io). ## What can an assistant do through the Hi Doctor connector? With the patient's permission, an assistant can read the patient's profile, consultations, prescriptions and messages, and guide the patient through a consultation questionnaire. The [patient tool reference](https://docs.hi-doctor.ai/mcp/tools/patient.md) lists every tool. The patient chooses which permissions to approve when connecting; see [permissions](https://docs.hi-doctor.ai/mcp/permissions.md). Actions with consequences, such as submitting a questionnaire, sending a message or cancelling a plan, use an [approval link](https://docs.hi-doctor.ai/mcp/approvals.md). The tool prepares the exact action, the patient approves it on Hi Doctor, and only then does the assistant commit it. ## What can an assistant never do? * Approve a consultation, issue a prescription or change a dose. Every consultation is reviewed in full by an EU-licensed doctor, who decides on medical grounds only; see [safety](https://docs.hi-doctor.ai/essentials/safety.md). * Answer medical questions for the patient or suggest a medicine. * Take payment or see card details. The patient pays on a hosted payment page. * Reach another patient's account. A connection belongs to one signed-in account. ## Which MCP servers does Hi Doctor run? | Server | Endpoint | Access | | - | - | - | | Product connector | `https://mcp.hi-doctor.ai/mcp` | Acts on one patient's account after sign-in and consent | | Docs search | `https://docs.hi-doctor.ai/mcp` | Searches this public documentation only; no account access | ## How is MCP different from a REST API? A REST API is called by code that a developer writes for each endpoint. MCP describes tools in a standard way, so any compatible AI app can discover and call them without custom code. Hi Doctor offers both: the MCP connector for assistants and the patient REST API for your own application. [Integration options](https://docs.hi-doctor.ai/businesses/integration-options.md) compares them. ## Frequently asked questions ### Is MCP specific to Hi Doctor? No. MCP is an open standard used by many AI apps and services. Hi Doctor runs one MCP server for patient accounts and one for searching its documentation. ### Which AI apps can connect to Hi Doctor? Any MCP client that supports remote servers over Streamable HTTP with OAuth sign-in. The docs include setup guides for Claude, ChatGPT, Cursor and VS Code. ### Does connecting share my whole account with the AI app? No. The patient approves specific permissions at sign-in, and the assistant can use only the tools those permissions allow. ### Can an AI assistant prescribe through MCP? No. Every consultation is reviewed in full by an EU-licensed doctor, who decides on medical grounds only. No algorithm, assistant or API call approves a consultation, issues a prescription or changes a dose. ### Do I need to write code to use the Hi Doctor connector? No. A patient adds the connector address in a supported AI app and signs in. Developers who build their own app can use the REST API instead. ## Next steps > [card] [For AI agents](https://docs.hi-doctor.ai/ai/index.md) > > Interfaces, safety rules and human handoffs. > [card] [Agent quickstart](https://docs.hi-doctor.ai/ai/quickstart.md) > > Connect, list tools and guide a questionnaire. > [card] [Connect the connector](https://docs.hi-doctor.ai/mcp/connect.md) > > Sign in, consent and disconnect. > [card] [MCP connector overview](https://docs.hi-doctor.ai/mcp/overview.md) > > Supported apps and what the connector covers. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.