← Back to all docs

CareLogic MCP Server

The CareLogic MCP server lets AI agents read and write client, episode, scheduling, documentation, authorization, and billing data in CareLogic by Qualifacts. Connect CareLogic to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since CareLogic doesn’t ship an MCP server.

By Alex KlarfeldMay 12, 2026
CareLogic API

What is the CareLogic MCP server?

The CareLogic MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) read and write client, episode, scheduling, documentation, authorization, and billing data in CareLogic through a standard protocol.

In short: CareLogic, the cloud behavioral-health EHR from Qualifacts, supports mental health, SUD, IDD, autism, and child & family service providers: intake and referrals, episodes of care and program enrollments, scheduling, clinical documentation, authorization tracking, billing and reimbursement, outcomes measurement, and HL7/FHIR connectors.

CareLogic doesn't ship an official MCP server, and CareLogic delivers documentation, authorization checks, and billing actions through web apps and batch exports, with 42 CFR Part 2 consent protections and behavioral-health workflows that need nuanced handling rather than a unified public API. Supergood builds and maintains the connector by reverse-engineering CareLogic's authenticated web and portal flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.

What you can do with CareLogic via MCP

Once connected, an agent can:

  • Look up clients: demographics, consents, referrals.
  • Pull episodes of care and program enrollments.
  • Pull and create appointments and encounters (individual, group, telehealth).
  • Retrieve clinical notes and treatment plans, with signatures and lock state.
  • Manage authorizations (service code, units, date ranges) and check eligibility and utilization.
  • Submit claims (837P) and reconcile remittances (835).
  • Pull outcomes measures and reporting data.

How to connect CareLogic to Claude, ChatGPT & Cursor

Connecting works like any other MCP server. The short version:

  • Claude (Desktop or claude.ai): add the CareLogic MCP server under Settings → Connectors (or your MCP config), authorize the CareLogic 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 CareLogic 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 CareLogic MCP server

Supergood doesn't wait for CareLogic to ship an API. We reverse-engineer the authenticated web and portal flows behind CareLogic, 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 CareLogic 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 CareLogic's front-end happens to return.
  • Monitored and adapted. When CareLogic changes its web and portal UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
  • Consent-aware access. Behavioral-health records carry 42 CFR Part 2 protections; Supergood respects consent gates and note-locking so the agent only sees what it’s entitled to.

Getting Started

  • Schedule Integration Assessment

Book a 30-minute call to confirm which CareLogic modules and workflows you need and how authentication should work.

  • Supergood Builds and Validates Your MCP Server

We deliver a hardened CareLogic 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 CareLogic changes.

carelogic

Use Cases

Intake and enrollment

- Pull the referral and create the client with consents - Enroll the client in the right episode and program - Surface missing consents before scheduling

Documentation

- Pull the open encounter and treatment plan - Surface notes that still need a signature or are unlocked - Keep records consistent with another tool

Authorization tracking

- Check remaining units before scheduling - Run eligibility and utilization checks - Flag authorizations running low

Billing and RCM

- Submit 837P claims once documentation is signed - Reconcile 835 remittances - Surface denials with payer-specific reasons

Technical Specifications

MCP transport

Remote MCP server over HTTPS; works with hosted MCP clients and with local MCP configs.

Authentication

Supergood provisions a dedicated CareLogic 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 scheduling and clinical reads; EDI/SFTP feeds and clearinghouse submissions follow batching windows that Supergood orchestrates.

Rate limits

Tuned to CareLogic'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 CareLogic 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 CareLogic web and portal surfaces changes, with rapid connector updates.

Frequently asked questions

No. CareLogic doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering CareLogic'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 CareLogic 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 CareLogic's live system, not a nightly export. CareLogic delivers documentation, authorization checks, and billing actions through web apps and batch exports, with 42 CFR Part 2 consent protections and behavioral-health workflows that need nuanced handling rather than a unified public API.

Both. The MCP tools are a layer on top of a normalized REST API for CareLogic; you can call either, from an agent or from your own code.

Ready to get a real API?