IntakeQ MCP Server

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

Packages and local setup

The published npm package is @oktopeak/intakeq-mcp, version 1.0.1. Its declared MCP transport is stdio.

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

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.0.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.