athenahealth MCP Server & Agent Skill
Last updated
ibl.ai publishes a free athenahealth agent skill: a SKILL.md that teaches an AI agent to read and write athenahealth data and expose it as an MCP tool. Download it, connect your own athenahealth credentials, and run the agent on ibl.ai Agentic OS, where you own all the code and the data.
athenaOne is athenahealth's cloud EHR, practice management and billing service. It holds practices, departments, providers, patients, appointments, clinical charts and documents, and claims and financial data.
What is the athenahealth API, and what can an agent read from it?
Proprietary athenaOne REST APIs with read and write across administrative, clinical and financial workflows, keyed by practice ID; FHIR R4 APIs for USCDI data; changed-data subscription feeds and event notifications.
- API: athenaOne APIs (proprietary) and athenahealth FHIR APIs (R4, DSTU2) (Mixed)
- Access: Partner or license program
- Base URL: https://api.platform.athenahealth.com/v1/{practiceid}/ (Production) and https://api.preview.platform.athenahealth.com/v1/{practiceid}/ (Preview); FHIR R4 global base: https://api.platform.athenahealth.com/fhir/r4
- Authentication: OAuth 2.0 client credentials; OAuth 2.0 authorization code
Anyone can register on the Developer Portal; Preview credentials reach a public sandbox. Certified FHIR APIs are free. athenaOne and non-certified APIs need Platform Services or the Marketplace Partner Program, and each practice must enable the app.
Token endpoint: {base}/oauth2/v1/token. 2-legged (service) apps send client ID and secret by Basic auth or a JWT signed with a registered JWKS. 3-legged apps, limited to Certified APIs, get user consent and may use PKCE.
What can an agent read from athenahealth?
- Departments β GET /v1/{practiceid}/departments lists a practice's departments.
- Changed data feeds β GET /v1/{practiceid}/documents/patientcase/changed returns queued changes for subscribed events.
- Subscription events β GET /v1/{practiceid}/documents/patientcase/changed/subscription/events lists events you can subscribe to.
- Clinical data (FHIR R4) β USCDI resources on the FHIR R4 global or site-specific base URL.
What can an agent write to athenahealth?
- Changed-data subscriptions β POST /v1/{practiceid}/documents/patientcase/changed/subscription subscribes to all or one event.
- Remove subscriptions β DELETE /v1/{practiceid}/documents/patientcase/changed/subscription removes a subscription or events. Confirm with the user first.
- athenaOne records β athenaOne APIs include write calls across administrative, clinical and financial functions; each needs its endpoint's scope. Confirm with the user first.
Limits: Response headers report a per-minute OAuth request limit and a per-day API call limit that resets at midnight GMT. Lists page with limit and offset. Bulk data pulls over the API are not accepted. Retry only 502-504 with backoff.
Records are HIPAA protected health information (PHI). OAuth credentials are tied to one environment, and production data is reachable only for practices that enable the app.
How do I connect athenahealth to an AI agent over MCP?
As of October 2026 we found no MCP server published by athenahealth itself.
The practical path is to host a small MCP server that wraps the athenaOne APIs (proprietary) and athenahealth FHIR APIs (R4, DSTU2), or to give the agent the calls directly with the SKILL.md below.
On ibl.ai an MCP connection is three records, and a working integration always needs all three:
- Register the server β
POST β¦/mcp-servers/with its URL, a transport (sse,websocketorstreamable_http) and anauth_typeofnone,tokenoroauth2. - Create a connection that holds the credential, scoped to the whole organization (
platform), to a single agent, or to each user (user). - Enable it on the agent β
mcp-toolintool_slugsand the server id inmcp_servers. Both lists are replaced, not merged, so read the settings first.
athenahealth supports per-user OAuth, so the server can use auth_type=oauth2 with auth_scope=user: each person connects their own athenahealth account in the chat the first time the agent needs it.
The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.
What does the athenahealth agent skill do?
The athenahealth skill is one SKILL.md file named iblai-connect-athenahealth. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.
Download the athenahealth SKILL.md
Save it as .claude/skills/iblai-connect-athenahealth/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:
$ npx skills add iblai/vibe --allThis connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.
It was checked against athenahealth's documentation on October 20, 2026. Test it against your own athenahealth setup before you rely on it.
What can I ask an athenahealth agent to do?
- βList the departments for practice 195900 in the Preview sandbox.β
- βShow patient cases that changed since my last sync.β
- βPull this patient's allergies and problem list through the FHIR R4 API.β
- βSubscribe to patient case change events for the cardiology department.β
How do I run an athenahealth agent on ibl.ai?
Agentic OS is where the agent runs on ibl.ai: it holds the athenahealth MCP connection, the model the agent uses, its instructions and its conversation history.
On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing β so you can deploy anywhere, from your own cloud to a fully air-gapped network.
- AI agents for Healthcare β what ibl.ai deploys in this sector
Which ibl.ai agents work with athenahealth data?
- Clinical Support β Healthcare
- Medical Coding β Healthcare
Which ibl.ai platform skills does an athenahealth agent use?
- /iblai-api-agent-mcp β MCP connectors for ibl.ai agents, end to end
- /iblai-vibe-agent-mcp β Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,β¦
- /iblai-api-agent-tool β Enable or disable an ibl.ai agent's tools via the platform API
What else should I know before connecting athenahealth to an AI agent?
Is there an official athenahealth MCP server?
Not that we found as of October 20, 2026: athenahealth documents the athenaOne APIs (proprietary) and athenahealth FHIR APIs (R4, DSTU2), not an MCP server of its own.
The SKILL.md on this page gives an agent the integration directly, and any MCP server you host can be registered on ibl.ai.
Who can get athenahealth API credentials?
Anyone can register on the Developer Portal; Preview credentials reach a public sandbox. Certified FHIR APIs are free. athenaOne and non-certified APIs need Platform Services or the Marketplace Partner Program, and each practice must enable the app.
Does athenahealth data leave my infrastructure when an ibl.ai agent uses it?
On ibl.ai, you own all the code and the data. Self-hosted in your cloud or data center, the agent, its MCP connections and its conversation logs stay inside your perimeter.
Because the platform is model-agnostic, you can point the agent at a model you host, so athenahealth records need not reach a third-party model provider.
Is the athenahealth agent skill free to use?
Yes. The SKILL.md is a free download with no sign-up. It assumes you already have athenahealth credentials, and your agreement with athenahealth still governs how you use its API.
Which other data sources can an AI agent connect to alongside athenahealth?
Which other Healthcare systems have a connector?
- Availity β Payer-provider health information network
- Epic β Electronic health record (EHR)
- HL7 FHIR β Healthcare data exchange standard
- MEDITECH Expanse β Electronic health record (EHR)
- Oracle Health (Cerner) β Electronic health record (EHR)
- Veradigm β Electronic health record (EHR)
Every connector, grouped by sector, is on the connectors hub.