Skip to main content
The Hi Doctor MCP changelog lists every change that affects clients connected to https://mcp.hi-doctor.ai/mcp, newest first. Tool names stay stable unless an entry says otherwise, and a renamed tool keeps its old name working for at least one release. Each entry carries its release date. Last reviewed: 2026-11-04
Approval links, revocation and guided questionnaires
Approval links, a record changes permission, guided questionnaires and new patient tools.
  • Approval links. Tools with consequences now prepare the exact action and return an approval_url. The account owner signs in on Hi Doctor and approves or declines; the assistant then commits with unchanged arguments. Links expire after 15 minutes. This applies to existing tools too, including hidoctor_message_send, hidoctor_questionnaire_submit and the subscription changes. See Approval links.
  • hidoctor_operation_get reads an operation’s state: awaiting_human, approved, declined, expired, executing, uncertain, succeeded or failed.
  • Safe retries. Commits take an idempotency_key. Repeating a commit with the same key returns the original result and never runs the action twice. See the idempotency guide.
  • Record changes permission: hidoctor:records:write, for uploading or deleting your own documents and consultation photos and for account deletion. Existing connections keep their grant and must reconnect to add it and to use approval links. See Permissions.
  • Guided questionnaires. hidoctor_questionnaire_answer accepts explicit skips of optional questions, single grid items (values_key) and follow-ups (option_input_key), and atomic batches in answers. hidoctor_questionnaire_back can return to a single item. See Workflows.
  • New patient tools: account export and deletion, health documents and consultation photos, message attachments, conversation details, renewals, credit notes, referrals, guides and prescription verification.
  • Prescription, invoice and other documents are now protected downloads that need authentication.
  • Token revocation. POST /revoke (RFC 7009) revokes the whole connection, and every token from it is rejected on the next request. See Streamable HTTP.
  • The HTTP 401 challenge now lists every scope the server supports in its scope parameter. Hi Doctor grants the ones the account can hold and drops the rest. See Streamable HTTP.
  • Errors carry retryable, field_errors, state, next_action and correlation_id.
  • What completes now. Messages and attachments, questionnaire submission, plan cancellation, reactivation and early orders, renewal confirmation, health documents and consultation photos commit after approval. See What can complete today.
  • Available on the website. The other approval-link actions, including checkout with a payment link, profile updates and deletions, can be prepared and approved but are completed on hi-doctor.ai, not through the connector. See Actions that cannot complete yet.
Permission step-up and size-capped results
Permission step-up, size-capped results and renamed journal tools.
  • A tool call that needs a permission you did not approve now gets an HTTP 403 insufficient_scope challenge naming the permission. Clients that support step-up send you back to approve it and retry; others ask you to reconnect. A tool that is not available to the account gets HTTP 403 forbidden.
  • The HTTP 401 challenge now includes a scope parameter: the permission the requested tool needs, or hidoctor:profile.
  • Authorization redirects, including error redirects, carry the RFC 9207 iss parameter.
  • Every result is capped in size. Lists that do not fit come back shorter with truncated, has_more and next_offset; concise lists honor limit up to 50 rows and continue exactly from next_offset. A record that cannot fit returns result_too_large. See Lists and pagination.
  • Read-only, destructive and repeat-safe hints were corrected to match what each tool does, so clients ask for confirmation in the right places. See the patient tools reference.
  • The patient conversation tool no longer creates a conversation when it is read; the first message sent creates it.
  • Two progress-journal tools were renamed. The old names stay callable for at least one release but no longer appear in the tool list:
    • hidoctor_progress_injections_log now runs hidoctor_progress_injection_log
    • hidoctor_progress_notes_add now runs hidoctor_progress_note_log
  • Injection plans accept the older preferred times morning, afternoon and evening, stored as 09:00, 14:00 and 19:00. HH:MM is the canonical form.
Sign-in moved to hi-doctor.ai
Sign-in moved to hi-doctor.ai.
  • Connecting now sends you to hi-doctor.ai to sign in, where password and Google sign-in, account creation and password reset all work. The connector no longer shows its own password form.
Clearer tools and a chat questionnaire over HTTP
Clearer tools and a chat questionnaire over HTTP.
  • Every tool has a title and an output schema, and list tools return a concise summary by default, with detail: "full" for the complete page.
  • The conversational questionnaire is also available as plain HTTP endpoints for chat apps. See HTTP chat integration.
  • Patients without an account could create one during connection.
  • Ordering a refill early moved under the Payment permission, and document links that open without sign-in are flagged as confidential.
  • Invoice and prescription PDF tools no longer fail on content negotiation.
Launch
Launch.
  • Remote MCP server over stateless Streamable HTTP with OAuth 2.1 (authorization code with PKCE, dynamic client registration).
  • Single-use authorization codes.
  • The endpoint also answers at the root URL and accepts wildcard Accept headers, for client compatibility.

Current limits

Rate limits, the result size cap, token lifetimes and the supported protocol versions are kept up to date on Streamable HTTP. In short: results are capped at about 20,000 tokens, the 2026-07-28 protocol is not supported, and clients register dynamically because client ID metadata documents are not supported.

Frequently asked questions

How do I know when Hi Doctor changes a tool?

Every change that affects connected clients is listed here, newest first. A renamed tool keeps its old name working for at least one release.

Do I need to reconnect after an update?

Only when an entry says so; today that means connections made before 2026-10-07, which must reconnect to get the record changes permission and approval links.

Can I revoke a connection now?

Yes. Since 2026-10-07 the server supports token revocation at /revoke, which ends the whole connection at once.

Does Hi Doctor support the 2026-07-28 MCP protocol?

No. The server negotiates protocol versions 2025-11-25 and earlier, down to 2024-10-07.

Next steps

Streamable HTTP

Endpoint, OAuth, token lifetimes and limits.

Agent quickstart

Build an agent on the current tools.