A
licenseNot graded
qualityD
maintenanceAn MCP server that brings AI-powered search and conversation to your FHIR clinical documents.
1
MIT
FHIR MCP Server
by maheshbalan
Related Servers
Alternatives to FHIR MCP Server
No user-submitted related servers found.
Related Servers
LangCare MCP FHIR Serverofficial
AlicenseNot gradedqualityDmaintenanceEnterprise-grade MCP Server for FHIR-based EMRs. Enables AI agents to read, search, create, and update any FHIR R4 resource across major EHR systems like EPIC, Cerner, and OpenEMR.297 npm55MIT- FlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that bridges AI applications with FHIR healthcare data systems, enabling patient data access, clinical data retrieval, and data quality assessment.4-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables querying FHIR healthcare data using natural language, allowing doctors to retrieve patient information, medications, observations, and other healthcare records.1-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables LLMs to securely query synthetic clinical data through validated, scoped tools (patient summaries, conditions, medications, lab trends, encounters) while maintaining audit logs and access controls.-
- FlicenseNot gradedqualityCmaintenanceA healthcare MCP demo server exposing clinical resources, tools, and prompts over SSE with authentication, integrated with Pydantic AI and Gemini for natural language patient record updates.-
TDQS
A3.9/5.0
Scored across 13 tools
Disambiguation4/5
Each request_<resource>_resource tool targets a distinct FHIR resource type, and the Pinecone/LOINC tools have clear separate purposes. However, the many similar request_resource wrappers could lead to accidental selection of the wrong resource, and request_generic_resource may be confused with the specific ones.
Naming Consistency3/5
The dominant request_<resource>_resource pattern is consistent, but get_loinc_codes, add_document_to_pinecone, and search_pinecone deviate with different verb styles, creating a mixed naming convention. This is readable but not fully predictable.
Tool Count5/5
13 tools is well-scoped for a FHIR MCP server, covering common clinical resources plus LOINC lookup and document search. Each tool has a clear purpose and the count is neither too thin nor overwhelming.
Completeness4/5
The server covers a broad set of FHIR resources (Patient, Observation, Medication, Condition, AllergyIntolerance, Encounter, Immunization, DocumentReference, FamilyMemberHistory) and provides a generic fallback for any other resource. Minor gaps exist (no dedicated cross-resource search or batch operations) but agents can work around them.
Maintenance
ActivitySlowing
ResponsivenessNo issues