← Back to all docs
centralreach

CentralReach MCP Server

The CentralReach MCP server lets AI agents read and write client, scheduling, ABA clinical-data, authorization, and billing data in CentralReach. Connect CentralReach to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since CentralReach doesn't ship an MCP server.

By Alex Klarfeld•May 12, 2026
CentralReach MCP Server

What is the CentralReach MCP server?

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

In short: CentralReach is a practice-management and clinical-data platform built for autism and IDD care, with a strong focus on Applied Behavior Analysis: client records and intake, scheduling and session workflows, ABA data collection (programs, goals, targets, trial data), clinical documentation, authorization management, billing and RCM, EVV, telehealth, and staff management.

CentralReach doesn't ship an official MCP server, and CentralReach delivers rosters, schedules, and clinical artifacts through web UIs and batch exports, with payer- and plan-specific rules and an API surface that varies by module. Supergood builds and maintains the connector by reverse-engineering CentralReach'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 CentralReach via MCP

Once connected, an agent can:

  • Look up clients and guardians/contacts; manage intake.
  • Pull and create schedules, appointments, and sessions.
  • Retrieve ABA programs, goals, targets, and data points.
  • Get authorizations (payer, service code, units, date range) and check remaining units.
  • Pull session notes and signatures; surface what still needs signing before billing.
  • Submit claims and post remittances (835); retrieve invoices and payments.
  • Get staff timesheets and mileage for payroll exports.

How to connect CentralReach to Claude, ChatGPT & Cursor

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

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

Supergood doesn't wait for CentralReach to ship an API. We reverse-engineer the authenticated web and portal flows behind CentralReach, 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 CentralReach 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 CentralReach's front-end happens to return.
  • Monitored and adapted. When CentralReach changes its web and portal UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
  • Sequencing, enforced. Auth checks precede scheduling, documentation precedes claim prep. Supergood encodes that sequencing so the agent doesn't skip a step that breaks billing.

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Builds and Validates Your MCP Server

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

Use Cases

Authorization-aware scheduling

- Check remaining units before booking a session - Block scheduling that would exceed the auth - Flag authorizations expiring soon

Clinical data and documentation

- Pull program data points for a client - Surface session notes missing a signature - Keep clinical records consistent with another tool

Billing and RCM

- Submit claims once documentation is signed - Post ERAs and reconcile - Surface denials with payer-specific reasons

Staff operations

- Pull timesheets and mileage for payroll - Surface schedule conflicts and unstaffed sessions - Track credentials and supervision hours

Technical Specifications

MCP transport

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

Authentication

Supergood provisions a dedicated CentralReach 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; export-driven artifacts are orchestrated by Supergood with retry.

Rate limits

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

Frequently asked questions

No. CentralReach doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering CentralReach'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 CentralReach 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 CentralReach's live system, not a nightly export. CentralReach delivers rosters, schedules, and clinical artifacts through web UIs and batch exports, with payer- and plan-specific rules and an API surface that varies by module.

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

Related APIs in Behavioral Health / ABA

Behavioral Health / ABA

ABA Billing Services API

ABA Billing Services is a billing and revenue cycle management service focused on Applied Behavior Analysis (ABA) providers. In plain English: they help ABA clinics get paid—handling authorizations, eligibility checks, claims submission, posting remittances, and denial follow-up. An unofficial API would let you programmatically read and update authorizations, validate and submit sessions, build 837 claims, track payer statuses, and reconcile ERA/EOBs without living in spreadsheets and portals. If you’re another healthcare tech company—say an EHR, scheduling platform, or RCM analytics tool—integrating with ABA Billing Services means you can pull patient insurance details, authorizations, session validation results, claim statuses and remittances; push patient/provider rosters, billable session logs, and corrections with audit trails; and build features like authorization-aware scheduling, automatic claims assembly, real-time denial worklists, and utilization dashboards.

Behavioral Health / ABA

AuthentiCare from Fiserv/First Data API

AuthentiCare from Fiserv/First Data is software used to capture and verify in-home and community-based care visits so providers can get paid by Medicaid and Managed Care Organizations (MCOs). It tracks who delivered care, to whom, where, and for how long, then routes verified visits to billing. With an unofficial API, you could create and edit visits, synchronize patient and caregiver rosters from your EHR, validate authorizations before visits occur, assemble claims from verified visits, and reconcile payments end-to-end.

Behavioral Health / ABA

BHM Healthcare Solutions API

BHM Healthcare Solutions is a healthcare services organization focused on medical necessity review, external peer review (IRO), utilization management, and appeals. An unofficial API lets you submit prior auth and review cases, attach clinical documentation, track determinations, retrieve decision letters, and surface authorization numbers for downstream billing—directly from your own systems.

Behavioral Health / ABA

BehaviorLive API

BehaviorLive is a virtual events and continuing education platform built for behavior analysts and behavioral health teams. It hosts live and on‑demand CEU courses, manages registrations, verifies attendance, delivers certificates, and tracks CEUs in learner transcripts. With an unofficial API, you could sync staff rosters, bulk‑enroll employees in required CEUs, pull real‑time attendance and engagement data, auto‑issue certificates after quizzes, and export transcripts for compliance.

Behavioral Health / ABA

CareLogic by Qualifacts API

Programmatically access client demographics, program enrollments, scheduling, clinical documentation, payer authorizations, and claims in CareLogic with a stable REST API. Supergood builds and operates production-grade, unofficial CareLogic integrations so your team can automate behavioral health EHR and revenue cycle workflows without heavy custom engineering. CareLogic by Qualifacts is an EHR used by behavioral health and human services organizations to manage intake, treatment planning, progress notes, outcomes, scheduling, and reimbursement across Medicaid, commercial, and grant-funded programs. With an unofficial API, you could synchronize your client roster, manage episodes and program participation, create and complete appointments and notes, validate authorizations before service delivery, and assemble 837P claims with remittance tracking—end to end.

Behavioral Health / ABA

Careify API

Programmatically access Careify’s Electronic Visit Verification (EVV), authorizations, scheduling, and Medicaid reimbursement workflows with a stable REST API. In plain English: Careify is software that helps home and community-based service providers, clinics, and provider groups document care visits, verify time and location, track payer authorizations, and get paid. An unofficial API lets you create and verify EVV visits, sync patients and caregivers from your EHR, validate authorizations before scheduling, and automatically assemble claims from verified visits—all without manual portal work.

Ready to get a real API?