Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect athenahealth to Claude Code

Make Claude draft notes and update billing tasks inside athenahealth. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect athenahealth to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect athenahealth, you add a athenahealth MCP server: a small hosted service that exposes athenahealth's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own athenahealth account. No API keys pasted into config files.

claude mcp add --transport http athenahealth https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in athenahealth once connected?

Full read-write athenahealth access lets Claude draft an encounter note for clinician review, queue a follow-up task, propose a claim or charge update, and flag a denied claim for rework, all where the record already lives. The lookup-then-retype loop that used to mean switching tabs happens in one place.

  • Draft an encounter or clinical note for a clinician to review and sign
  • Create or update a task in a provider's or biller's worklist
  • Propose a charge or claim edit for a billing reviewer to approve
  • Flag a denied or held claim and draft the corrected resubmission
  • Add an internal note or update a patient case after you confirm

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same athenahealth access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the athenahealth API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when athenahealth changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build athenahealth connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same athenahealth connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own athenahealth account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on athenahealth's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to athenahealth?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the athenahealth account it signs in with. Revoking access is one click in athenahealth.

More on the athenahealth connector

athenahealth connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us