Skip to main content
Glama
ysnr-dev

fhir-mcp-server

by ysnr-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to fhir-mcp-server

No user-submitted related servers found.

    Related Servers

    • medplum-mcp

      ncodeuy
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Medplum FHIR healthcare data, enabling Claude and other MCP clients to read, search, and query FHIR resources from one or more Medplum environments.
      5 npm
      -

    • FHIR MCP Server

      sumithasb
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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
    • FHIRfly MCP Server by FHIRfly-io

      FHIRfly MCP Serverofficial

      FHIRfly-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for connecting Claude Desktop to FHIRfly healthcare reference data APIs, enabling lookup of drugs, providers, clinical codes, and more.
      81 npm
      MIT

    • smart-mcp-server

      DigitalSQR
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely interact with FHIR R4 servers for clinical decision support workflows, including PlanDefinition execution, FHIR resource management, terminology services, and Questionnaire/StructureMap transformation via Matchbox.
      1
      -

    • FHIR MCP Server

      maheshbalan
      A
      license
      A
      quality
      C
      maintenance
      MCP server for FHIR interoperability, enabling natural language querying and manipulation of clinical data with full CRUD operations, semantic search, and RAG capabilities.
      13
      MIT
    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

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct FHIR operation: server metadata, searching, reading, patient compartment, history, and validation. No overlaps are apparent.

    Naming Consistency4/5

    Most tool names follow a verb_noun pattern (e.g., get_capabilities, search_fhir), except patient_everything which uses a noun_verb form. The inconsistency is minor and does not hinder understanding.

    Tool Count5/5

    Six tools is appropriate for a FHIR MCP server covering essential interactions: discovery, search, read, patient compartment, history, and validation. The scope is well-balanced.

    Completeness2/5

    The toolset lacks create, update, and delete operations, which are core to resource lifecycle management. The validate_fhir tool even references create_fhir/update_fhir as prerequisites, but they are missing.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources