Skip to main content
Glama
maheshbalan

FHIR MCP Server

by maheshbalan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to FHIR MCP Server

No user-submitted related servers found.

    Related Servers

    • FHIR MCP Server

      ncastro5146
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients to query and manipulate FHIR-compliant clinical data using natural-language prompts, offering full CRUD operations on FHIR resources, semantic document search, RAG pipelines, and LOINC terminology lookup.
      -

    • FHIR MCP Server

      richardandersson65189
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients to interact with FHIR-compliant backends through full CRUD operations, document ingestion, semantic search, and LOINC terminology lookup. It supports natural-language querying and manipulation of clinical data.
      -

    • FHIR MCP Server

      AlessiaDemir57
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients and LLM agents to perform full CRUD operations on FHIR resources, query and manipulate clinical data through natural-language prompts, and use document ingestion, semantic search, and terminology lookup against a FHIR backend.
      -

    • FHIR MCP Server

      aranyajenkins7342
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources