What is the IntakeQ MCP MCP server?
IntakeQ/PracticeQ MCP connector with HIPAA §164.312(b) audit logging on every PHI read/write
How to install IntakeQ MCP
Copy-paste configuration for popular MCP clients.
INTAKEQ_API_KEYsecretIntakeQ API key (optional — prefer the set_api_key tool)
INTAKEQ_API_BASEOverride the default IntakeQ API base URL (https://intakeq.com/api/v1)
MCP_API_KEYsecretBearer token gate on the HTTP /mcp endpoint. Required in http mode unless MCP_ALLOW_NO_AUTH is true
MCP_ALLOW_NO_AUTHSet to true to allow HTTP mode without MCP_API_KEY (local development only)
TRANSPORTTransport mode: stdio (default) or http
MCP_BASE_URLBase URL for HTTP transport (e.g. http://127.0.0.1:3000)
PORTHTTP listen port (default 3000). HTTP transport only.
Related MCP servers

Connect Claude to Lawmatics: matters, contacts, pipelines, tasks, forms, custom fields, invoices.

Connect Claude to MyCase: cases, contacts, documents, tasks, calendar, calls, time, billing, staff.

36 Clio tools for Claude: read matters, contacts, documents, tasks, billing—audit-logged, encrypted, ABA Opinion 512 compliant.

Open-source MCP server connecting Claude to Filevine practice management. Built by Oktopeak.
Building-permit verdicts by address, with cited records. SF, Seattle, Austin, NYC. Pay per call.
Crypto price-event settlement verdicts and US building-permit data, paid per call in USDC.
