← Back to all docs
waystar

Waystar MCP Server

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

By Alex KlarfeldInvalid Date

What is the Waystar MCP server?

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

In short: Waystar is a unified revenue cycle and clearinghouse platform for healthcare providers: eligibility and coverage discovery, claim scrubbing and submission to thousands of payers, claim status, electronic remittance, denial and underpayment analytics, prior authorization, and patient payment tools.

Waystar doesn't ship an official MCP server, and each payer has unique edit logic living in Waystar's scrubber. Portal-first processes (denial workqueues, attachments, resubmissions) sit behind web UIs. Supergood builds and maintains the connector by reverse-engineering Waystar'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 Waystar via MCP

Once connected, an agent can:

  • Check eligibility and run coverage discovery (270/271).
  • Submit professional and institutional claims (837P/I) through the scrubber.
  • Track claim status and notifications (276/277).
  • Pull remittances (835 ERA): payments, adjustments, refunds.
  • Surface denials, underpayments, and workqueues with CARC/RARC reasons.
  • Generate patient estimates and statements.
  • Look up payers, plans, and provider records (NPIs, TINs).

How to connect Waystar to Claude, ChatGPT & Cursor

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

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

Supergood doesn't wait for Waystar to ship an API. We reverse-engineer the authenticated web and EDI flows behind Waystar, 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 Waystar 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 Waystar's front-end happens to return.
  • Monitored and adapted. When Waystar changes its web and EDI UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
  • EDI plus the portal. Waystar mixes real-time portal flows with X12 EDI batches and portal-only denial workqueues; Supergood handles all of it and returns parsed JSON alongside the raw X12.

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Builds and Validates Your MCP Server

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

Use Cases

Clean-claim workflow

- Submit claims and watch the scrubber edits - Track 277 acknowledgments - Surface rejections with the payer-specific reason

Denial management

- Pull denial and underpayment workqueues - Group by CARC/RARC reason - Draft the resubmission with the right attachments

Remittance posting

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

Patient financials

- Generate an estimate before service - Produce statements for outstanding balances - Reconcile patient payments against claims

Technical Specifications

MCP transport

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

Authentication

Supergood provisions a dedicated Waystar 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 (837/835/270/271/276/277) follow batching windows that Supergood orchestrates.

Rate limits

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

Frequently asked questions

No. Waystar doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering Waystar'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 Waystar 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 Waystar's live system, not a nightly export. Each payer has unique edit logic living in Waystar's scrubber, and portal-first processes (denial workqueues, attachments, resubmissions) sit behind web UIs.

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

Ready to get a real API?