IntakeQ MCP

Name: IntakeQ MCP
Author: oktopeak

by oktopeakversion 1.0.1i★ –iRuns on your computer

Registry nameio.github.oktopeak/intakeq-mcp

Install

Overview

Description from the maker (original English)

IntakeQ/PracticeQ MCP connector with HIPAA §164.312(b) audit logging on every PHI read/write

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 48/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools
You need to fill in: INTAKEQ_API_KEY, MCP_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: INTAKEQ_API_KEY, INTAKEQ_API_BASE, MCP_API_KEY, MCP_ALLOW_NO_AUTH, TRANSPORT, MCP_BASE_URL, PORT

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "intakeq": {
      "command": "npx",
      "args": [
        "-y",
        "@oktopeak/intakeq-mcp"
      ],
      "env": {
        "INTAKEQ_API_KEY": "your-value",
        "INTAKEQ_API_BASE": "your-value",
        "MCP_API_KEY": "your-value",
        "MCP_ALLOW_NO_AUTH": "your-value",
        "TRANSPORT": "your-value",
        "MCP_BASE_URL": "your-value",
        "PORT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add intakeq --env INTAKEQ_API_KEY=your-value --env INTAKEQ_API_BASE=your-value --env MCP_API_KEY=your-value --env MCP_ALLOW_NO_AUTH=your-value --env TRANSPORT=your-value --env MCP_BASE_URL=your-value --env PORT=your-value -- npx -y @oktopeak/intakeq-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "intakeq": {
      "command": "npx",
      "args": [
        "-y",
        "@oktopeak/intakeq-mcp"
      ],
      "env": {
        "INTAKEQ_API_KEY": "your-value",
        "INTAKEQ_API_BASE": "your-value",
        "MCP_API_KEY": "your-value",
        "MCP_ALLOW_NO_AUTH": "your-value",
        "TRANSPORT": "your-value",
        "MCP_BASE_URL": "your-value",
        "PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "intakeq": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@oktopeak/intakeq-mcp"
      ],
      "env": {
        "INTAKEQ_API_KEY": "your-value",
        "INTAKEQ_API_BASE": "your-value",
        "MCP_API_KEY": "your-value",
        "MCP_ALLOW_NO_AUTH": "your-value",
        "TRANSPORT": "your-value",
        "MCP_BASE_URL": "your-value",
        "PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

INTAKEQ_API_KEY secret env
IntakeQ API key (optional — prefer the set_api_key tool)
INTAKEQ_API_BASE env
Override the default IntakeQ API base URL (https://intakeq.com/api/v1)
MCP_API_KEY secret env
Bearer token gate on the HTTP /mcp endpoint. Required in http mode unless MCP_ALLOW_NO_AUTH is true
MCP_ALLOW_NO_AUTH env
Set to true to allow HTTP mode without MCP_API_KEY (local development only)
TRANSPORT env
Transport mode: stdio (default) or http
MCP_BASE_URL env
Base URL for HTTP transport (e.g. http://127.0.0.1:3000)
PORT env
HTTP listen port (default 3000). HTTP transport only.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account oktopeak, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 5606 servers in this category
Published to the registry more recently than 20% of the other 5606 servers in this category
Basic checks equal to or better than 100% of the other 5606 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is IntakeQ MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: INTAKEQ_API_KEY, MCP_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 6 days ago

Computer or cloud

Install

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 18 days ago

Runs on your computer

Install

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@oktopeak/intakeq-mcp

### Built by Oktopeak — AI transformation & automation for healthcare practices

Digital transformation for healthcare and legal businesses. We build AI integrations, workflow automation, and custom software your practice owns outright — including this connector. → Book a 30-min call

IntakeQ/PracticeQ MCP connector for Claude. Gives Claude access to your IntakeQ scheduling, intake forms, treatment notes, invoices, and client records through the Model Context Protocol.

Every PHI read and write is logged locally in compliance with HIPAA §164.312(b).

⚠️ Before you connect this to real patient data

Two things must be in place before PHI flows through this connector:

IntakeQ BAA — IntakeQ/PracticeQ includes a Business Associate Agreement. Sign it in your IntakeQ account (Settings → HIPAA) before going live. This is one of IntakeQ's strengths: the BAA is self-serve and included in all plans.

Anthropic enterprise tier with ZDR — With hosted Claude + MCP, PHI goes to Anthropic for inference. The defensible claim is training-disabled + Zero Data Retention under enterprise + BAA — not data locality. "Access" (the model processed it) is the exposure, not just retention. Sign up for Anthropic enterprise and request a BAA before using this with real patients.

What this connector does:

Brokers authenticated calls to the IntakeQ REST API
Logs every PHI read and write to ~/.intakeq-mcp/audit.log (HIPAA §164.312(b))
Stores your API key encrypted (AES-256-GCM) locally — no PHI content stored (audit entries contain only access-trail identifiers)

Installation

npm install -g @oktopeak/intakeq-mcp

Claude Desktop configuration

"mcpServers": { "intakeq": { "command": "intakeq-mcp" } } }

Authentication

Generate your API key in IntakeQ: Settings → Integrations → Developer API

Then tell Claude:

"Set my IntakeQ API key to [your-key]"

Or use the MCP tool directly: set_api_key

Tools

Tool	Description	R/W
`set_api_key`	Store IntakeQ API key	W
`auth_status`	Verify API connection	R
`clear_api_key`	Remove stored key	W
`list_clients`	Search/list clients	R
`get_client`	Single client profile	R
`list_practitioners`	All practitioners in the account	R
`list_services`	Services configured in the account	R
`list_locations`	Locations configured in the account	R
`list_appointments`	Appointments by client/date	R
`get_appointment`	Single appointment	R
`create_appointment`	Book appointment	W
`update_appointment`	Reschedule/update	W
`list_intake_forms`	Submitted intake forms	R
`get_form`	Full form with answers	R
`list_questionnaire_templates`	Available form templates	R
`send_intake_form`	Send form to client	W
`list_notes`	Treatment notes (read-only in IntakeQ API)	R
`get_note`	Full note	R
`list_invoices`	Client invoices	R
`get_invoice`	Single invoice	R
`list_files`	Client file metadata	R
`audit_export`	Export HIPAA audit trail	R

Tip: call list_practitioners, list_services, and list_locations before create_appointment to obtain valid IDs required by that tool.

MCP Resources

Resource URI	Description
`intakeq://compliance-notice`	HIPAA compliance notice — BAA requirements and what the connector logs
`intakeq://auth-status`	Live authentication status (JSON)

HIPAA Audit Log

Every PHI read and write is appended to ~/.intakeq-mcp/audit.log (JSONL format). Each entry records: timestamp, session ID, machine IP, tool name, arguments (sanitized), outcome, practitioner ID, client ID, and result count.

Export the audit log at any time: ask Claude to run audit_export.

Audit logging is fail-open. If the log file can't be written (disk full, permissions), the tool call still completes rather than blocking clinical work — the failure is written to stderr with an [audit-log-failure] prefix so it can be monitored/alerted on. If you need a hard guarantee that PHI access is never left unlogged, monitor process stderr for that prefix in your deployment.

HTTP transport

The server runs in stdio mode by default. To run as an HTTP server (e.g. for multi-user or remote deployments):

MCP_API_KEY=your-secret TRANSPORT=http PORT=3000 intakeq-mcp

The MCP endpoint is at /mcp, gated by a required Bearer token (MCP_API_KEY). The server refuses to start in HTTP mode without `MCP_API_KEY` set, since an unauthenticated endpoint would expose every PHI tool to anyone who can reach the port. To explicitly opt into an unauthenticated endpoint for local development only, set MCP_ALLOW_NO_AUTH=true — never do this with real patient data.

HTTP transport does not terminate TLS itself. Run it behind a reverse proxy (nginx, Caddy, your cloud provider's load balancer, etc.) that terminates HTTPS — otherwise the Bearer token and all PHI in transit are sent in plaintext on the network.

Each HTTP session maintains its own API key in memory — the set_api_key tool scopes the key to the session and never writes it to the shared disk file. Sessions are garbage-collected after 24 hours.

Health check: GET /health → { "ok": true, "sessions": }

Environment variables

Variable	Default	Description
`INTAKEQ_API_KEY`	—	Fallback API key for CI / headless use (prefer the `set_api_key` tool)
`INTAKEQ_API_BASE`	`https://intakeq.com/api/v1`	Override the IntakeQ API base URL
`TRANSPORT`	`stdio`	Transport mode: `stdio` or `http`
`PORT`	`3000`	HTTP server port (HTTP mode only)
`MCP_BASE_URL`	`http://127.0.0.1:3000`	Base URL printed in HTTP startup logs
`MCP_API_KEY`	—	Bearer token to gate the HTTP `/mcp` endpoint. Required in HTTP mode unless `MCP_ALLOW_NO_AUTH=true`
`MCP_ALLOW_NO_AUTH`	—	Set to `true` to explicitly allow HTTP mode without `MCP_API_KEY` (local dev only)

Rate limiting

IntakeQ enforces ~10 requests/minute. The connector retries automatically on HTTP 429 (up to 3 attempts, with back-off delays of 10 s / 20 s / 30 s). After 3 failures the error is surfaced rather than hanging indefinitely.

Not yet covered

Insurance claims / CMS-1500 write
Webhooks
Bulk operations
Creating treatment notes (not available in IntakeQ API)

Other open-source connectors by Oktopeak

Same architecture (encrypted key storage, audit logging, rate limiting), different platforms:

[Clio MCP](https://github.com/oktopeak/clio-mcp) — Claude + Clio practice management (@oktopeak/clio-mcp)
[MyCase MCP](https://github.com/oktopeak/mycase-mcp) — Claude + MyCase legal practice management (@oktopeak/mycase-mcp)
[Filevine MCP](https://github.com/oktopeak/filevine-mcp) — Claude + Filevine practice management (@oktopeak/filevine-mcp)

Supporting this project

This connector is free, MIT licensed, and maintained by Oktopeak. It always will be — we don't take donations. If it saved you time, the things that actually help:

Star this repo. It is genuinely how other firms find it.
Tell another firm running IntakeQ.
[Leave a review](https://clutch.co/profile/oktopeak) if we helped you directly.
Need it deployed, extended, or maintained for your firm? [Commercial support](https://oktopeak.com/services/healthcare-ai-integration/) — that is what funds the free work.
Practice-wide deployment: rolling Claude + this connector out to a whole practice (Claude Cowork, multi-user, security review)? See Firm Deployment.

Who we are

[Oktopeak](https://oktopeak.com/?utm_source=github&utm_medium=readme&utm_campaign=intakeq-mcp&utm_content=who-we-are) — digital transformation for healthcare and law firms.

We're a 7-person in-house product team building AI solutions for regulated industries: AI integrations, workflow automation, and custom software our clients own outright. We maintain four open-source MCP connectors — Clio, MyCase, Filevine, and IntakeQ — and deploy them inside real practices with scoped credentials, audit logs, and workflows built around how your team actually works.

🌐 oktopeak.com
📅 Book a 30-min call
✉️ office@oktopeak.com — security reports welcome
💼 LinkedIn

IntakeQ MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

@oktopeak/intakeq-mcp

⚠️ Before you connect this to real patient data

Installation

Claude Desktop configuration

Authentication

Tools

MCP Resources

HIPAA Audit Log

HTTP transport

Environment variables

Rate limiting

Not yet covered

Other open-source connectors by Oktopeak

Supporting this project

Who we are