Back to MCP Servers
๐Ÿงฉ

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

To add IntakeQ MCP to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 7 environment variables, listed below.

DevTools

Install

npx -y @oktopeak/intakeq-mcp@1.0.1

Environment variables

INTAKEQ_API_KEYSet in your MCP config
INTAKEQ_API_BASESet in your MCP config
MCP_API_KEYSet in your MCP config
MCP_ALLOW_NO_AUTHSet in your MCP config
TRANSPORTSet in your MCP config
MCP_BASE_URLSet in your MCP config
PORTSet in your MCP config

Install with your client

Terminal
claude mcp add intakeq --env INTAKEQ_API_KEY=<YOUR_INTAKEQ_API_KEY> --env INTAKEQ_API_BASE=<YOUR_INTAKEQ_API_BASE> --env MCP_API_KEY=<YOUR_MCP_API_KEY> --env MCP_ALLOW_NO_AUTH=<YOUR_MCP_ALLOW_NO_AUTH> --env TRANSPORT=<YOUR_TRANSPORT> --env MCP_BASE_URL=<YOUR_MCP_BASE_URL> --env PORT=<YOUR_PORT> -- npx -y @oktopeak/intakeq-mcp@1.0.1

Run this in a terminal to add the server to Claude Code.

What this does

IntakeQ MCP exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

INTAKEQ_API_KEY
INTAKEQ_API_BASE
MCP_API_KEY
MCP_ALLOW_NO_AUTH
TRANSPORT
MCP_BASE_URL
PORT

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install IntakeQ MCP?

Run the Claude Code command in the install section to add IntakeQ MCP to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with IntakeQ MCP?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to IntakeQ MCP as well.

Does IntakeQ MCP need an API key?

Yes. Before it can run, set these environment variables: INTAKEQ_API_KEY, INTAKEQ_API_BASE, MCP_API_KEY, MCP_ALLOW_NO_AUTH, TRANSPORT, MCP_BASE_URL, PORT. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-oktopeak-intakeq-mcp)](https://clauderules.net/mcp/io-github-oktopeak-intakeq-mcp)
HTML
<a href="https://clauderules.net/mcp/io-github-oktopeak-intakeq-mcp" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-oktopeak-intakeq-mcp" alt="Listed on clauderules.net" /></a>