FHIR MCP Server
Related Servers
Alternatives to FHIR MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables LLM-based agents to connect to a FHIR-compliant healthcare backend and query or manipulate clinical data with natural-language prompts. Provides full CRUD operations on FHIR resources, AI-powered document ingestion and semantic search, RAG-ready retrieval, and LOINC terminology lookup.-
- FlicenseNot gradedqualityAmaintenanceEnables LLM-based agents to interact with FHIR-compliant backends through natural-language prompts, supporting CRUD operations on clinical resources, document ingestion, semantic search, and LOINC terminology lookup.-
- FlicenseNot gradedqualityAmaintenanceEnables LLM-based agents and MCP-compatible clients to query and manipulate FHIR clinical data through natural-language prompts, with full CRUD operations, document ingestion, semantic search, and LOINC terminology lookup.-
- FlicenseNot gradedqualityAmaintenanceEnables LLM-based agents and MCP-compatible clients to query and manipulate clinical data on a FHIR-compliant backend using natural-language prompts, with full CRUD operations, document ingestion, semantic search, and LOINC terminology support.-
- FlicenseNot gradedqualityAmaintenanceEnables LLM-based agents and MCP-compatible clients to perform full CRUD operations on FHIR resources and query or manipulate clinical data using natural-language prompts. It also supports document ingestion, semantic search, LOINC terminology lookup, and secure FHIR API authentication.-
- FlicenseNot gradedqualityAmaintenanceEnables LLM-based agents and MCP-compatible clients to perform full CRUD operations on FHIR resources and query or manipulate clinical data using natural-language prompts. It also supports document ingestion, semantic search, LOINC terminology lookup, and OAuth2 authentication for FHIR APIs.-
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.