Give your agent the whole health record.
Flexpa's hosted MCP server lets an AI agent read a patient's consented claims and clinical records through ready-made tools, using the same patient access token as the FHIR API.
Included from Growth · $5,000/year on lower plans · Read the docs
- FHIR API
- Your own tool definitions
- Your own agent auth
- POST /mcp/consent
- 18 records tools
- 12 prompts
01The short answer
What is the Flexpa MCP server?
The Flexpa MCP server is a hosted Model Context Protocol server for patient health records. After a patient connects their health insurer, their providers or TEFCA through Flexpa Consent, an MCP client such as Claude or ChatGPT can call tools like get_labs, get_claims and find_in_record to read that patient's records.
It authenticates with the patient access token your app already receives from Consent, so there is no second sign-in to build and no agent tools to write and maintain on top of the FHIR API.
02How it works
From connection to result
- 1
The patient connects
The patient finds their insurer, provider or TEFCA in Flexpa Consent and approves sharing.
- 2
Your app gets a token
Consent returns a patient access token, the same one you would use with the FHIR API.
- 3
Point the MCP client at Flexpa
Configure the client with https://api.flexpa.com/mcp/consent and the token. The server uses the streamable HTTP transport.
- 4
The agent reads the record
The agent calls tools for a health summary, labs, medications, claims, spending and documents, and can search the record with find_in_record.
POST https://api.flexpa.com/mcp/consent
Authorization: Bearer <patient_access_token>Records tools
Each tool reads the consented record of one patient.
- get_health_summary
- get_patient
- get_coverage
- get_claims
- get_financial_summary
- get_problems
- get_allergies
- get_labs
- get_vitalsigns
- get_documents
- get_medications
- get_immunizations
- get_procedures
- get_visits
- get_care_team
- find_in_record
- get_document_content
- fhir_read
Good to know
- The MCP server is in beta.
- It needs a patient access token. /mcp/consent returns 401 for application access tokens.
- Records tools leave out records marked entered-in-error or cancelled.
- Documented clients are Claude, ChatGPT on paid plans with developer mode, and Claude Code.
03Who it's for
Where it pays off
AI health assistants
Ground answers about labs, medications and bills in the patient’s own records instead of what they remember to type.
See Flexpa for agentsHealth apps and devices
Add a chat or copilot to your product that already knows the user’s conditions, prescriptions and recent results.
See health apps and devicesCare navigation
Give a navigator’s assistant the history behind a referral before the first conversation.
See care navigationPlans
Included in Growth and above
MCP server is included in the Growth, Scale, Omni and Infrastructure plans. On Startup, it is $5,000 a year.
04A few good questions
MCP server,
answered.
Which AI clients work with it?
Claude, ChatGPT on paid plans with developer mode, and Claude Code are documented. The server speaks MCP over streamable HTTP with a bearer token.
Can the agent see other patients?
No. The patient access token is scoped to one patient’s consent, so the tools only return that patient’s records.
What can the agent read?
Whatever the patient connected: coverage, claims and costs, problems, allergies, labs, vital signs, medications, immunizations, procedures, visits, care team and clinical documents.
How is this different from the public tools at /mcp?
The public endpoint offers health tools for agents, such as endpoint discovery, and does not touch patient records. Patient records tools need a patient access token at /mcp/consent.
Which Flexpa plans include MCP server?
MCP server is included in the Growth, Scale, Omni and Infrastructure plans. On Startup, it is $5,000 a year.
Spotlights
More add-ons
C-CDA to PDF conversion
Every record, one PDF.
SSO (SAML, OIDC, SCIM sync)
Sign in to Flexpa like everything else.
Claims to clinical data normalization
Query claims like a medical record.
C-CDA to FHIR conversion
Turn TEFCA documents into FHIR you can query.
Proprietary network connections
Reach the employer plans your users actually have.
SMART Health Links
Share records with a link or a QR code.
Put your agent on real records.
See a patient connect in the demo, then see what an agent can do with their history.
Get a demo