intakeq-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (HTTP mode only) | 3000 |
| TRANSPORT | No | Transport mode: stdio or http | stdio |
| MCP_API_KEY | No | Bearer token to gate the HTTP /mcp endpoint. Required in HTTP mode unless MCP_ALLOW_NO_AUTH=true | |
| MCP_BASE_URL | No | Base URL printed in HTTP startup logs | http://127.0.0.1:3000 |
| INTAKEQ_API_KEY | No | Fallback API key for CI / headless use (prefer the set_api_key tool) | |
| INTAKEQ_API_BASE | No | Override the IntakeQ API base URL | https://intakeq.com/api/v1 |
| MCP_ALLOW_NO_AUTH | No | Set to true to explicitly allow HTTP mode without MCP_API_KEY (local dev only) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_api_keyA | Store your IntakeQ API key and verify connectivity |
| auth_statusA | Check whether the connector is authenticated with IntakeQ |
| clear_api_keyA | Clear the stored IntakeQ API key |
| list_clientsA | Search/list clients in the connected IntakeQ account. Returns up to 100 results per page. Response field reference: BillingType: 0=Unknown, 1=SelfPay, 2=Insurance LinkedClientRelationshipType: 0=None, 1=Parent, 2=Child, 3=Spouse, 4=Sibling, 5=Other, 6=Partner |
| get_clientA | Get a single client by ID (includes full profile). Response field reference: BillingType: 0=Unknown, 1=SelfPay, 2=Insurance LinkedClientRelationshipType: 0=None, 1=Parent, 2=Child, 3=Spouse, 4=Sibling, 5=Other, 6=Partner |
| list_practitionersA | List all practitioners in the IntakeQ account. Call this before create_appointment to find a valid PractitionerId. |
| list_servicesA | List services configured in the IntakeQ account. Call this before create_appointment to find a valid ServiceId. |
| list_locationsA | List locations configured in the IntakeQ account. Call this before create_appointment to find a valid LocationId. |
| list_appointmentsA | List appointments. At least one of clientId, startDate, or endDate must be provided. |
| get_appointmentA | Get a single appointment by ID |
| create_appointmentB | Create a new appointment in IntakeQ. All fields are required. |
| update_appointmentA | Update an existing appointment via PUT. Id and UtcDateTime are required. Cannot change client or practitioner. |
| list_intake_formsA | List intake form submissions. PHI — every call is audit-logged. |
| get_formA | Get a single intake form submission by ID. PHI — every call is audit-logged. |
| list_questionnaire_templatesA | List all questionnaire templates available in the IntakeQ account |
| send_intake_formA | Send an intake form to a client. Provide QuestionnaireId plus either ClientId or (ClientName and ClientEmail). |
| list_notesA | List clinical notes. PHI — every call is audit-logged. Notes are read-only in IntakeQ. |
| get_noteA | Get a single clinical note by ID. PHI — every call is audit-logged. |
| list_invoicesB | List invoices from the connected IntakeQ account |
| get_invoiceA | Get a single invoice by ID |
| list_filesA | List file metadata for a client. Returns references only (Id, FileName, DateCreated, Size, ContentType, FolderId). Files are never downloaded — this tool returns metadata references only. clientId is mandatory. |
| audit_exportA | Export the local HIPAA §164.312(b) audit log. Every read and write of PHI is recorded here. Use date_from/date_to to filter by date range, client_id to filter by patient. Supports pagination via limit/offset. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| compliance-notice | Explains what the connector does, what it logs, and the BAA requirement |
| auth-status | Live authentication status — whether an API key is stored and verified |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/oktopeak/IntakeQ'
If you have feedback or need assistance with the MCP directory API, please join our Discord server