Skip to main content
This is the full reference for the tools a patient account sees after connecting the Hi Doctor MCP connector. Each tool acts as the signed-in patient and can only read or change that patient’s own records, under the same rules as the website. Tools with consequences use an approval link, so nothing happens until the patient approves the exact action on Hi Doctor. Last reviewed: 2026-11-04 As of 2026-11-04 the catalog lists 70 tools. The tool list your client shows is the source of truth for your connection, and changes are recorded in the changelog. Tools whose permission the patient did not approve are left out of the client’s tool list. For step-by-step tasks, see Workflows.
Two older names stay callable but are hidden from the tool list. Update saved prompts and scripts to the new names:
  • hidoctor_progress_injections_log now runs hidoctor_progress_injection_log
  • hidoctor_progress_notes_add now runs hidoctor_progress_note_log

Which permission does each tool area need?

Each tool needs one or more permissions (OAuth scopes). A few actions need two or three, and the tables below say so next to the tool. See Permissions for what each permission grants.

What do the hints mean?

Each tool carries hints that MCP clients use to decide when to ask you for confirmation. Hints describe behaviour; they never replace Hi Doctor’s own permission checks. They come from the server and lean towards caution: a tool that can overwrite something already saved, such as a questionnaire answer, is marked Destructive even when the patient can change it again later. Approval-link tools also accept mode, confirmation_id and idempotency_key. They are left out of the parameter lists below.

What do results and errors look like?

Results include structuredContent that matches each tool’s output schema, plus the same data as JSON text. List tools page with limit, offset and detail (concise or full); see Lists and pagination. Documents, PDFs and exports come back as links with metadata, never as bytes in the result. Errors come back as tool results with isError: true and an error object with code, message, retryable, field_errors, state, next_action and correlation_id. Follow next_action rather than retrying blindly; the codes are explained on Build on Hi Doctor with AI.

Profile

Permission: hidoctor:profile

Approvals

Permission: hidoctor:profile

Account and data

Permission: hidoctor:profile

Consultations

Permission: hidoctor:consultations

Questionnaires

Permission: hidoctor:questionnaires

Checkout and billing

Permission: hidoctor:checkout, hidoctor:consultations

Renewals

Permission: hidoctor:consultations

Prescriptions

Permission: hidoctor:consultations

Messages

Permission: hidoctor:messages

Health documents

Permission: hidoctor:consultations

Records

Permission: hidoctor:consultations

Safety reports

Permission: hidoctor:consultations

Progress journal

Permission: hidoctor:progress

Referrals

Permission: hidoctor:consultations

Guides and verification

Permission: hidoctor:profile

What can no tool do?

No tool approves an action for the patient: approval happens only on Hi Doctor, after the patient signs in. Approving a consultation, issuing or changing a prescription and changing a dose are decisions for the patient’s doctor, and no tool available to a patient performs them. Clinical eligibility is decided by Hi Doctor’s servers when a questionnaire is submitted. See Safety.

Next steps

Workflows

Common tasks, step by step.

Build on Hi Doctor with AI

The questionnaire loop and the rules an assistant follows.

Approval links

How the patient approves an action on Hi Doctor.

Permissions

What each permission grants and how to add one.
Ready to try it? Connect Hi Doctor in your client.