Mcp Server
Query FHIRfly healthcare datasets—drugs, providers, diagnoses, labs, vaccines, claims, and Medicaid—from your agent while building health apps.
Overview
io.fhirfly/mcp-server is an MCP server for the Build phase that integrates FHIRfly healthcare data APIs for drugs, providers, diagnoses, labs, vaccines, claims, and Medicaid.
What is this MCP server?
- Coverage: drugs, providers, diagnoses, labs, vaccines, claims, Medicaid endpoints
- npm package @fhirfly-io/mcp-server v0.4.0 with stdio transport
- Requires FHIRFLY_API_KEY from fhirfly.io
- GitHub: FHIRfly-io/fhirfly-mcp-server for local MCP wiring
- npm package @fhirfly-io/mcp-server version 0.4.0
- stdio transport; required env FHIRFLY_API_KEY
- Repository: github.com/FHIRfly-io/fhirfly-mcp-server
What problem does it solve?
You are building a health app but waste hours wiring disparate clinical and payer APIs instead of letting your agent query them through one MCP surface.
Who is it for?
Indie health-tech builders prototyping FHIR-adjacent features who want stdio MCP access to FHIRfly datasets.
Skip if: Teams needing a certified EHR, on-prem PHI storage without a FHIRfly contract, or non-health products.
What do I get? / Deliverables
Your agent calls FHIRfly-backed tools so integrations for diagnoses, labs, claims, and related endpoints ship faster behind a single API key.
- Agent-callable healthcare entity lookups and related endpoint access
- Faster health-data integration without custom client boilerplate per resource
Recommended MCP Servers
Journey fit
Build is canonical because the server supplies external clinical and payer data you integrate into prototypes and backends, not distribution or ops monitoring. Integrations matches an npm stdio MCP that wraps third-party healthcare APIs behind uniform tools.
How it compares
Healthcare data MCP over FHIRfly APIs, not a general-purpose SQL or Postgres MCP server.
Common Questions / FAQ
Who is io.fhirfly/mcp-server for?
Developers building healthcare or Medicaid-related products who want agent-driven access to FHIRfly clinical and claims endpoints.
When should I use io.fhirfly/mcp-server?
Use it while integrating backend or agent features that need drugs, providers, diagnoses, labs, vaccines, claims, or Medicaid data.
How do I add io.fhirfly/mcp-server to my agent?
Install @fhirfly-io/mcp-server via npm, set FHIRFLY_API_KEY, and add the stdio MCP server entry in Claude Code or Cursor per FHIRfly docs.