Search clients, appointments, intakes, notes and invoices in IntakeQ, and book or cancel visits. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"intakeq": {
"url": "https://intakeq.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"intakeq": {
"type": "http",
"url": "https://intakeq.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Patient data: Do not use this server with protected health information (PHI). We do not sign HIPAA Business Associate Agreements (BAAs). See Terms, Health data.
The login page asks for your IntakeQ API key.
Find it in IntakeQ → More → Settings → Integrations → Developer API. Only the main account owner can generate it, and the Developer API requires a paid IntakeQ plan. Generating a new key invalidates the old one. Your key is used only to call the IntakeQ API on your behalf and to derive a private account id; it is never shown to anyone. No patient data from your IntakeQ account is logged or stored by this server. Sign IntakeQ's BAA before using real patient data.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your IntakeQ API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the IntakeQ connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
intakeq_list_clients | read | Search clients Search the practice's clients (patients) by name, email or client number, by created/updated date range, by external id, or by a custom field. Without include_profile it returns Name, Email, Phone and ClientNumber; with include_profile=true it returns the full profile (address, insurance, tags, custom fields, linked clients). Max 100 per page. IntakeQ: GET /clients. |
intakeq_get_client_diagnoses | read | Get a client's diagnoses List the diagnoses recorded for one client: code, description, start/end date and the treatment note they came from. IntakeQ: GET /client/{clientId}/diagnoses. |
intakeq_list_appointments | read | List appointments Query appointments by client name/email, date range, status, practitioner or last-modified date. Max 100 per page. IntakeQ: GET /appointments. |
intakeq_get_appointment | read | Get one appointment Fetch one appointment: client, practitioner, service, location, start/end, status, price, invoice, telehealth link and cancellation details. IntakeQ: GET /appointments/{id}. |
intakeq_get_booking_settings | read | Get booking settings List the scheduler's locations, services (with duration and price) and practitioners — the ids you need to create an appointment. IntakeQ: GET /appointments/settings. |
intakeq_list_intakes | read | List intake forms Query submitted intake questionnaires (summaries: client, status, questionnaire, practitioner, dates). By default only completed forms; set all=true for every status (Sent, Partial, Completed, Offline). Max 100 per page. IntakeQ: GET /intakes/summary. |
intakeq_get_intake | read | Get a full intake form Fetch one intake questionnaire with every question and answer, its consent forms and linked appointment. IntakeQ: GET /intakes/{id}. |
intakeq_list_questionnaires | read | List questionnaire templates List the intake questionnaire templates in the account (id, name, archived, anonymous) — the ids you need to send one. IntakeQ: GET /questionnaires. |
intakeq_list_practitioners | read | List practitioners List the practitioners in the account (id, name, email, external id). IntakeQ: GET /practitioners. |
intakeq_list_notes | read | List treatment notes Query treatment note summaries by client, lock status, date range or last-updated date. Max 100 per page. IntakeQ: GET /notes/summary. |
intakeq_get_note | read | Get a full treatment note Fetch one treatment note with every question and answer and its linked appointment. IntakeQ: GET /notes/{id}. |
intakeq_list_invoices | read | List invoices Query invoices by client, issue date range, status, practitioner or last-updated range. Each invoice includes items, payments and amounts due/paid. Max 100 per page. IntakeQ: GET /invoices. |
intakeq_get_invoice | read | Get one invoice Fetch one invoice: line items, taxes, discounts, payments, totals and amount due. IntakeQ: GET /invoices/{id}. |
intakeq_save_client | write | Create or update a client Create a client, or update one. With ClientId the existing client is updated. WITHOUT ClientId IntakeQ still tries to match an existing client by first name + email (or first name + phone) and updates that one instead of creating a duplicate. For updates, fetch the full profile first (intakeq_list_clients with include_profile=true) and send it back with your changes, so no field is unintentionally cleared. Field names are IntakeQ's own. Dates are Unix timestamps in milliseconds. IntakeQ: POST /clients. |
intakeq_add_client_tag | write | Tag a client Add a tag to a client. The tag is created if it does not exist; adding one the client already has is a no-op. IntakeQ: POST /clientTags. |
intakeq_create_appointment | write | Create an appointment Book an appointment in the PracticeQ scheduler. Get PractitionerId, ServiceId and LocationId from intakeq_get_booking_settings. All fields are required by IntakeQ. Status must be Confirmed or WaitingConfirmation; SendClientEmailNotification may be true only when Status is Confirmed. IntakeQ: POST /appointments. |
intakeq_update_appointment | write | Update or reschedule an appointment Change an appointment's time, service, location, status or reminder type. Id and UtcDateTime are required (send the current time to keep it); include only the other fields you are changing. The client and practitioner cannot be changed, and a Confirmed appointment cannot go back to WaitingConfirmation. IntakeQ: PUT /appointments. |
intakeq_cancel_appointment | write | Cancel an appointment Cancel an appointment, with an optional reason. This changes the client's booking and cannot be undone through the API — book a new appointment to replace it. IntakeQ: POST /appointments/cancellation. |
intakeq_send_questionnaire | write | Send an intake questionnaire Send an intake questionnaire to a client by email or SMS. This MESSAGES THE CLIENT. Identify the client by ClientId, or by ClientName plus ClientEmail and/or ClientPhone (omit ClientEmail to force SMS). PractitionerId is optional. Returns the new intake. IntakeQ: POST /intakes/send. |
intakeq_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
intakeq_request_feature | Request a missing feature Tell usefulapi that the user needs something the IntakeQ tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
intakeq_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on IntakeQ (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
intakeq_cancel_subscription | Cancel the Pro subscription Cancel the caller's IntakeQ Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run intakeq_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this IntakeQ server only. Subscribe with intakeq_upgrade (it returns a Stripe Checkout link). Cancel any time with intakeq_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running intakeq_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by IntakeQ. The server calls the IntakeQ API with your own IntakeQ access, so it sees only the data that your account can see.
No. Do not use this server with protected health information (PHI). We do not sign HIPAA Business Associate Agreements (BAAs). See Terms, Health data.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your IntakeQ API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your IntakeQ API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the IntakeQ API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in IntakeQ.
Yes, if you approve it. 6 of the 19 IntakeQ tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this IntakeQ server only. Cancel any time: Pro then runs to the end of the paid period. Run intakeq_usage_status to see how many calls you used.
Ask the AI to run intakeq_upgrade: it returns a Stripe Checkout link. To cancel, run intakeq_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with intakeq_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.