← Back to all docs

InstaMed MCP Server

The InstaMed MCP server lets AI agents run patient billing, payment, and remittance workflows through InstaMed. Connect InstaMed to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since InstaMed doesn't ship an MCP server.

By Alex Klarfeld•May 12, 2026
InstaMed API

What is the InstaMed MCP server?

The InstaMed MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) run patient billing, payment, and remittance workflows through InstaMed using a standard protocol.

In short: InstaMed (a J.P. Morgan company) runs a secure healthcare payment network: patient billing and statements, card and ACH payment acceptance, stored payment methods and payment plans, a claims clearinghouse with ERA retrieval, and deposit and settlement reporting.

InstaMed doesn't ship an official MCP server, and InstaMed delivers statements, transactions, and ERA artifacts through web apps and batch exports rather than unified public APIs, with PCI and HIPAA controls around card data and PHI. Supergood builds and maintains the connector by reverse-engineering InstaMed'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 InstaMed via MCP

Once connected, an agent can:

  • Look up patients and guarantors, statements, and balances.
  • Process card and ACH payments (authorization, capture, settlement) and manage vaulted payment methods.
  • Set up and manage payment plans: terms, installments, next due date.
  • Pull remittances (ERA/835) for reconciliation: payer, check, claim lines, adjustments.
  • Retrieve deposit and settlement batches.
  • Handle refunds, adjustments, and chargebacks.
  • Look up providers, merchants, locations, and terminals.

How to connect InstaMed to Claude, ChatGPT & Cursor

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

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

Supergood doesn't wait for InstaMed to ship an API. We reverse-engineer the authenticated web and batch flows behind InstaMed, 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 InstaMed 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 InstaMed's front-end happens to return.
  • Monitored and adapted. When InstaMed changes its web and batch UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
  • PCI-aware handling. Card data, ACH credentials, and PHI sit behind strict controls; Supergood works the authenticated flows without exposing sensitive payloads to the agent.

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Builds and Validates Your MCP Server

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

instamed

Use Cases

Patient collections

- Pull outstanding statements and balances - Process a card or ACH payment and confirm settlement - Set up a payment plan when the patient asks

Reconciliation

- Pull ERA/835 remittances and parsed payment detail - Match against deposits and posted payments - Flag short-pays and adjustments for review

Deposit reporting

- Pull settlement batches for a date range - Reconcile against the bank deposit - Surface mismatches and pending settlements

Exceptions

- Process refunds and adjustments when authorized - Track chargeback status and respond - Reconcile reversals against the original transaction

Technical Specifications

MCP transport

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

Authentication

Supergood provisions a dedicated InstaMed 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 payment processing and balance lookups; ERA and deposit reports follow settlement and file-cutoff windows that Supergood orchestrates.

Rate limits

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

Frequently asked questions

No. InstaMed doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering InstaMed'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 InstaMed 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 InstaMed's live system, not a nightly export. InstaMed delivers statements, transactions, and ERA artifacts through web apps and batch exports rather than unified public APIs, with PCI and HIPAA controls around card data and PHI.

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

Related APIs in Healthcare RCM / Billing

Healthcare RCM / Billing

Office Ally API

Office Ally is software that helps medical practices submit insurance claims, verify patient eligibility, manage appointments and charges, and run a cloud EHR. With an unofficial API, you could programmatically sync patients and insurance data, create and submit 837 claims, run real-time 270 eligibility checks, and pull 835 remittances for automated posting—without manual portal work. If you’re a healthcare tech startup building billing, practice management, or provider tooling, integrating with Office Ally means you can pull patient demographics, insurance policies, appointments, eligibility responses, claim statuses, and ERAs; push new patients, updated insurance, charges/superbills, and claims; and build features like eligibility-aware scheduling, automatic claim assembly, real-time rejection handling, and remittance reconciliation. Programmatically access clearinghouse, eligibility, claims, and practice management workflows in Office Ally with a stable REST API. Supergood builds and operates production-grade, unofficial Office Ally integrations so your team can automate critical billing and RCM pipelines without heavy custom engineering.

Healthcare RCM / Billing

Office Ally MCP Server

The Office Ally MCP server lets AI agents run eligibility, claims, status, remittance, and practice-management workflows across Office Ally. Connect Office Ally to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since Office Ally doesn't ship an MCP server.

Healthcare RCM / Billing

Optum API

Optum is healthcare technology used by payers and programs to manage authorizations, eligibility, EVV (in certain programs), and reimbursement. With an unofficial API from Supergood, you could create and verify EVV visits, synchronize member and provider rosters from your EHR, validate authorizations, assemble and submit claims, and reconcile payments end to end. If you’re a clinic, provider group, or a business running revenue cycle operations, integrating your tech stack with Optum can let you pull real-time authorizations and visit statuses, push EHR schedules into EVV, and tie verified visits directly to Medicaid reimbursement—especially helpful for Massachusetts (MassHealth) workflows where EVV and payer rules drive submission compliance. A different tech company integrating with Optum might pull member demographics, authorizations, provider enrollment data, claim statuses, and remittance summaries, while pushing visit check-in/out events, compliance reason codes, and claims files. That unlocks features like authorization-aware scheduling, automated exception resolution, and reconciliation dashboards.

Healthcare RCM / Billing

Optum MCP Server

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

Healthcare RCM / Billing

R1 RCM API

R1 RCM is software that hospitals and provider groups use to register patients, verify eligibility, capture charges, submit claims, manage denials, and collect patient balances. With an unofficial API, you could sync patients and insurance, run real-time eligibility checks, generate and route 837 claims, and reconcile ERA/835 remittances to close the loop.

Healthcare RCM / Billing

Rivet API

Programmatically access payer contract models, prior authorization tracking, estimates, and reimbursement analytics in Rivet with a stable REST API. Supergood builds and operates production-grade, unofficial Rivet integrations so your team can automate critical billing and revenue cycle workflows without heavy custom engineering. Rivet is software used by healthcare provider groups, clinics, and revenue cycle teams to model payer contracts, track prior authorizations, generate compliant patient estimates, identify underpayments, and manage denials and reimbursement. With an unofficial API, you could calculate allowed amounts by payer and CPT code, synchronize authorizations from your scheduling/EHR, generate patient estimates tied to coverage and benefits, pull claims and remittance variance, and route underpayment/denial worklists—end to end.

Ready to get a real API?