Connect IntakeQ to Claude Code

Make Claude run the intake paperwork loop in IntakeQ. From the terminal, inside the sessions where you already work.

How do you connect IntakeQ to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect IntakeQ, you add a IntakeQ MCP server: a small hosted service that exposes IntakeQ's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own IntakeQ account. No API keys pasted into config files.

claude mcp add --transport http intakeq https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in IntakeQ once connected?

Full read-write closes the intake loop. Claude can send an intake questionnaire to a new client, check which sent forms are still incomplete, create or reschedule the appointment, update client profile details, and pull unpaid invoices into a follow-up queue, so no client arrives unbooked, unbilled, or with paperwork missing.

Send an intake questionnaire to a new client, after you approve
Check which sent intake forms are still incomplete and draft reminders for your review
Create or reschedule an appointment, after you approve the slot
Update a client's profile details, like contact information and tags, after you approve
Pull a client's submitted intake responses and summarize them for the practitioner
List unpaid invoices and prepare a follow-up summary by client

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same IntakeQ access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the IntakeQ API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when IntakeQ changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build IntakeQ connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same IntakeQ connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own IntakeQ account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on IntakeQ's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to IntakeQ?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the IntakeQ account it signs in with. Revoking access is one click in IntakeQ.

More on the IntakeQ connector

IntakeQ connector for claude.ai SimplePractice + Claude Code Acuity Scheduling + Claude Code Stripe + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us