FHIR MCP Server
Related Servers
Alternatives to FHIR MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to securely interact with FHIR healthcare servers and HL7 terminology services. Provides comprehensive healthcare data operations with built-in PHI protection, audit logging, and SMART on FHIR authentication.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables seamless integration with FHIR APIs for healthcare applications, allowing users to search, retrieve, create, update, and analyze clinical information through natural language interactions. Supports SMART-on-FHIR authentication and works with various healthcare systems like EPIC and HAPI FHIR servers.Apache 2.0
- FlicenseAqualityDmaintenanceProvides read/write access to any FHIR-compliant healthcare API with built-in validation, supporting resource management, search operations, and granular permissions through natural language.51-
- AlicenseAqualityCmaintenanceProvides seamless integration with FHIR APIs, enabling AI/LLM tools to search, retrieve, and analyze clinical healthcare data with support for SMART-on-FHIR authentication and multiple transport protocols.7116 PyPI135Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely interact with FHIR R4-based EMRs, supporting read, search, create, and update operations on any FHIR resource type across systems like Epic, Cerner, and OpenEMR.285 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables LLMs to interact with clinical patient records using tools for document ingestion, structured conversion, patient profiling, record listing, search, and secure Q&A over patient documentation.-
TDQS
Scored across 13 tools
The request_*_resource tools are clearly separated by FHIR resource type, and request_generic_resource is explicitly a fallback for resources without a dedicated tool. However, the similar structure and the note in request_observation_resource referencing a non-existent 'get_loinc_code' tool could cause slight confusion.
The CRUD tools follow a strong request_<resource>_resource pattern, making the set predictable. The utility tools (get_loinc_codes, add_document_to_pinecone, search_pinecone) diverge in style but are still verb-first and understandable.
13 tools is well within the ideal range for a FHIR server covering multiple resource types. The number is neither bloated nor thin, given the broad scope of FHIR.
The set covers CRUD for the most common FHIR resources plus a generic fallback for all others, and adds LOINC lookup and document search. Minor gaps like a dedicated search/query tool or terminology service exist, but the generic resource tool covers most needs.