← Back to all docs
change healthcare

Change Healthcare MCP Server

The Change Healthcare MCP server lets AI agents run eligibility, claims, status, remittance, and prior-authorization workflows through Change Healthcare. Connect Change Healthcare to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since Change Healthcare doesn't ship an MCP server.

By Alex KlarfeldMay 12, 2026

What is the Change Healthcare MCP server?

The Change Healthcare MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) run eligibility, claims, status, remittance, and prior-authorization workflows through Change Healthcare using a standard protocol.

In short: Change Healthcare provides healthcare transaction processing and revenue-cycle solutions: a clearinghouse and EDI hub (837/835/270/271/276/277, attachments), eligibility verification, claims submission and edits, claim status and denial management, ERA/EFT, prior authorization, and provider/payer enrollment.

Change Healthcare doesn't ship an official MCP server, and Change Healthcare mixes portals, SFTP batches, and limited APIs, with payer-specific edits and trading-partner routing rules that must be respected. Supergood builds and maintains the connector by reverse-engineering Change Healthcare's authenticated web and EDI flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.

What you can do with Change Healthcare via MCP

Once connected, an agent can:

  • Check eligibility and benefits against a payer (270/271).
  • Submit professional and institutional claims and watch the edits and acknowledgments.
  • Track claim status events (277/277CA) and denials.
  • Pull remittances (835 ERA): payments, adjustments, CARC/RARC codes.
  • Submit prior-authorization inquiries and track status where the payer supports it.
  • Manage provider and payer enrollment for ERA/EFT and claim routing.
  • Look up payers, payer plans, and trading-partner routing.

How to connect Change Healthcare to Claude, ChatGPT & Cursor

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

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

Supergood doesn't wait for Change Healthcare to ship an API. We reverse-engineer the authenticated web and EDI flows behind Change Healthcare, 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 Change Healthcare 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 Change Healthcare's front-end happens to return.
  • Monitored and adapted. When Change Healthcare changes its web and EDI UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
  • EDI plus portal. Change Healthcare's data is split across portals, SFTP batches, and limited APIs; Supergood handles all of it and returns one normalized surface.

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Builds and Validates Your MCP Server

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

Use Cases

Clean-claim workflow

- Submit claims and watch the edits and 277 acknowledgments - Surface rejections with the payer-specific reason - Re-submit corrections

Eligibility before service

- Batch-check eligibility for the schedule against the right payers - Flag inactive coverage and benefit limits - Hand the front desk a clean list

Remittance posting

- Pull 835 ERAs and parsed payment detail - Reconcile against submitted claims - Flag short-pays for follow-up

Enrollment management

- Track ERA/EFT enrollment status by payer - Surface payers blocking submission until enrolled - Keep routing consistent across the practice

Technical Specifications

MCP transport

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

Authentication

Supergood provisions a dedicated Change Healthcare 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 portal flows; X12 EDI batches follow trading-partner schedules that Supergood orchestrates, with parsed JSON alongside the raw X12.

Rate limits

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

Frequently asked questions

No. Change Healthcare doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering Change Healthcare'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 Change Healthcare 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 Change Healthcare's live system, not a nightly export. Change Healthcare mixes portals, SFTP batches, and limited APIs, with payer-specific edits and trading-partner routing rules that must be respected.

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

Ready to get a real API?