Kipu Health MCP Server
The Kipu Health MCP server lets AI agents read and write admissions, census, documentation, authorization, and billing data in Kipu Health. Connect Kipu Health to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since Kipu Health doesn’t ship an MCP server.
What is the Kipu Health MCP server?
The Kipu Health MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) read and write admissions, census, documentation, authorization, and billing data in Kipu Health through a standard protocol.
In short: Kipu Health is an EHR purpose-built for behavioral health and substance use disorder treatment (detox, residential, PHP, IOP, and outpatient), covering admissions and intake, census and bed management, clinical documentation, scheduling and attendance, eMAR and medication management, utilization review and authorizations, and billing exports.
Kipu Health doesn't ship an official MCP server, and Kipu's admissions, census, and documentation workflows live in web apps and report exports rather than broad public APIs, with multi-episode complexity and e-signature/audit requirements on clinical edits. Supergood builds and maintains the connector by reverse-engineering Kipu Health's authenticated web and batch flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.
What you can do with Kipu Health via MCP
Once connected, an agent can:
- Look up patients and clients: demographics, identifiers, consents.
- Pull episodes and admissions: level of care, program, admit/discharge, bed assignments.
- Pull and create individual and group sessions; track attendance.
- Retrieve clinical documents (assessments, treatment plans, progress and group notes) with e-signatures and lock state.
- Manage payer coverages and authorizations (units/days, service types, validity dates) and run utilization review.
- Pull orders and lab results: toxicology, screening outcomes.
- Pull billing exports and claims/remittance artifacts (837/835).
How to connect Kipu Health to Claude, ChatGPT & Cursor
Connecting works like any other MCP server. The short version:
- Claude (Desktop or claude.ai): add the Kipu Health MCP server under Settings → Connectors (or your MCP config), authorize the Kipu Health account Supergood provisions, and the tools show up in any chat, including agent runs.
- ChatGPT: add it as a connector under Settings → Connectors, authorize, and ChatGPT can call the Kipu Health tools in conversations and in agent mode.
- Cursor: add the server to your MCP config (mcp.json or Settings → MCP), reload, and the tools are available to the agent.
Supergood owns the auth piece (credentials, MFA, session refresh), so the connection doesn't drop. New to MCP? Our explainer covers what an MCP server is and how clients connect to one.
How Supergood builds the Kipu Health MCP server
Supergood doesn't wait for Kipu Health to ship an API. We reverse-engineer the authenticated web and batch flows behind Kipu Health, normalize the responses, and wrap them as MCP tools, plus the underlying REST API if you'd rather call it from code.
- Auth and MFA, handled. Supergood provisions a dedicated Kipu Health account (email and phone managed by us) and keeps the session alive through MFA, token expiry, and re-auth.
- Normalized data. Responses come back in consistent JSON shapes across modules, not the raw shape Kipu Health's front-end happens to return.
- Monitored and adapted. When Kipu Health changes its web and batch UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
- Multi-episode, linked. A patient can have several episodes and level-of-care changes; Supergood keeps documents, authorizations, and billing linked to the right episode so nothing gets crossed.
Getting Started
- Schedule Integration Assessment
Book a 30-minute call to confirm which Kipu Health modules and workflows you need and how authentication should work.
- Supergood Builds and Validates Your MCP Server
We deliver a hardened Kipu Health connector (MCP tools plus the underlying API) scoped to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Kipu Health changes.
Use Cases
Admissions and census
- Take the referral and start the admission - Assign a bed and the level of care - Keep census and occupancy current
Documentation
- Pull the open assessment and treatment plan - Surface notes that need an e-signature - Track group notes against the session roster
Utilization review
- Pull authorizations and remaining days by payer and level of care - Flag authorizations running low - Prep the UR submission
Billing support
- Pull billing exports for claim generation - Reconcile authorizations against billed units - Pull 835 artifacts for posting
Technical Specifications
MCP transport
Remote MCP server over HTTPS; works with hosted MCP clients and with local MCP configs.
Authentication
Supergood provisions a dedicated Kipu Health account (managed email and phone) and handles MFA; you can also bring your own credentials. Session refresh is automatic.
Supported clients
Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, Cursor, and other MCP-compatible clients.
Tools exposed
8 tools covering the workflows listed above; the set is scoped to the modules you license.
Data freshness
Near real-time for census and clinical reads; CSV/HL7/X12 report exports follow timing windows that Supergood orchestrates with retry.
Rate limits
Tuned to Kipu Health's tolerances; Supergood paces requests to avoid tripping security throttles.
Latency
Sub-second for most reads under normal load; writes reflect the underlying platform timing.
Session management
Automatic re-auth plus cookie/token rotation, with health checks.
Security
Encrypted transport, scoped access, and audit logging; respects Kipu Health role-based permissions.
Webhooks
Optional asynchronous delivery for long-running operations; polling otherwise.
Reliability
Retry logic, backoff, and idempotency keys to avoid duplicates.
Adaptation
Continuous monitoring for Kipu Health web and batch surfaces changes, with rapid connector updates.
Frequently asked questions
No. Kipu Health doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering Kipu Health's authenticated flows and exposing them as MCP tools, plus the underlying REST API.
All of them, plus any MCP-compatible client. The same connector shows up in Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, and Cursor.
Supergood provisions a dedicated Kipu Health account with managed MFA, or uses credentials you supply. We keep the session alive through MFA prompts, token expiry, and re-auth, so the connection stays live.
Yes. Reads and writes hit Kipu Health's live system, not a nightly export. Kipu's admissions, census, and documentation workflows live in web apps and report exports rather than broad public APIs, with multi-episode complexity and e-signature/audit requirements on clinical edits.
Both. The MCP tools are a layer on top of a normalized REST API for Kipu Health; you can call either, from an agent or from your own code.