Developer · Local MCP server
IntakeQ MCP
IntakeQ/PracticeQ MCP connector with HIPAA §164.312(b) audit logging on every PHI read/write.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.oktopeak/intakeq-mcp- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-02
- Updated
- 2026-07-02
- Publisher
- oktopeak (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/oktopeak) · how
- Website
- github.com/oktopeak/IntakeQ
- Repository
- github.com/oktopeak/IntakeQ
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @oktopeak/intakeq-mcp | 1.0.1 | stdio |
How to connect IntakeQ MCP
IntakeQ MCP runs locally from a Node.js package published to the npm registry: @oktopeak/intakeq-mcp version 1.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @oktopeak/intakeq-mcp@1.0.1. It reads these environment variables: INTAKEQ_API_KEY (secret), INTAKEQ_API_BASE, MCP_API_KEY (secret), MCP_ALLOW_NO_AUTH, TRANSPORT, MCP_BASE_URL and PORT; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"intakeq-mcp": {
"command": "npx",
"args": [
"-y",
"@oktopeak/intakeq-mcp@1.0.1"
],
"env": {
"INTAKEQ_API_KEY": "<secret>",
"INTAKEQ_API_BASE": "<value>",
"MCP_API_KEY": "<secret>",
"MCP_ALLOW_NO_AUTH": "<value>",
"TRANSPORT": "<value>",
"MCP_BASE_URL": "<value>",
"PORT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from oktopeak (GitHub)
| Server | Runs |
|---|---|
| Clio MCPConnect Claude to Clio: 34 tools for matters, custom fields, notes, documents, folders, billing. | Local · stdio |
| Filevine MCPOpen-source MCP server connecting Claude to Filevine practice management. Built by Oktopeak. | Local · stdio |
| Lawmatics MCPConnect Claude to Lawmatics: matters, contacts, pipelines, tasks, forms, custom fields, invoices. | Local · stdio |
| Mycase MCPConnect Claude to MyCase: cases, contacts, documents, tasks, calendar, calls, time, billing, staff. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| InstaNode-dev MCPProvision Postgres databases + webhooks from AI coding agents in one HTTP call. | Local · stdio |
| InstaPodsDeploy and manage web apps on InstaPods: create pods, push files, run commands, read logs. | Remote · HTTPLive check: sign-in required |
| InstinctSelf-learning memory for AI coding agents with pattern detection and confidence scoring. | Local · stdio |
| IntactIntAct (EBI) molecular-interaction database MCP. Keyless. | Remote · HTTPLive check: ✓ handshake |
| IntegrityPulse FinOpsVerified cloud cost forecasting for AI agents. AWS, GCP, Azure pricing matrix. | Remote · HTTPLive check: ✓ handshake |
| Intelligence GatewayUnified MCP gateway to Algeria TKAWEN ecosystem: commerce, certification and AI tools. | Remote · HTTPLive check: ✓ handshake |
| intencion.ioDebug a bad AI-agent run from your editor: which intent fails, at which step, and why. | Local · stdio |
| Interactive TerminalMCP server for real interactive terminal sessions - REPLs, SSH, databases, Docker. | Local · stdio |