IntakeQ MCP

Name: IntakeQ MCP
Author: oktopeak

作者：oktopeak版本 1.0.1i★ –i在你的电脑上运行

注册名称io.github.oktopeak/intakeq-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 48/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具
你需要填写：INTAKEQ_API_KEY, MCP_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： INTAKEQ_API_KEY, INTAKEQ_API_BASE, MCP_API_KEY, MCP_ALLOW_NO_AUTH, TRANSPORT, MCP_BASE_URL, PORT

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

INTAKEQ_API_KEY 机密 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 机密 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.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 oktopeak 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 5715 个服务器的 0%
发布到注册中心的时间比此分类中其他 5715 个服务器的 20% 更新
基础检查结果等于或优于此分类中其他 5715 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

IntakeQ MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：INTAKEQ_API_KEY, MCP_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.1）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

作者：github广泛使用★ 3.4万7天前更新

电脑或云端

安装

Desktop Commander

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

作者：wonderwhy-er广泛使用↓ 71万/周★ 1万19天前更新

在你的电脑上运行

安装

Cloudflare MCP

Cloudflare MCP servers

作者：cloudflare广泛使用★ 444614个月前更新

在云端运行✓ mcp.cloudflare.com

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@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