Skip to main content
Glama
brianbastian01

FHIR MCP Server

by brianbastian01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to FHIR MCP Server

No user-submitted related servers found.

    Related Servers

    • Healthcare FHIR MCP Server

      CSOAI-ORG
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI applications to securely search and manage healthcare data from FHIR R4-compliant servers with built-in safety validation for AI-generated clinical observations, preventing recording of physiologically impossible values.
      8 npm
      MIT

    • fhir-mcp-server

      krlz-dev
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to search FHIR R4 patients and observations, access patient data as resources, and generate clinical summaries through prompts, using a public HAPI FHIR sandbox.
      2
      MIT

    • FHIR MCP Server

      baala-saravanan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI applications to query and retrieve healthcare data (patients, conditions, observations, medications) from a public FHIR R4 server via MCP tools.
      MIT
    • LangCare MCP FHIR Server by mosaic-care

      LangCare MCP FHIR Serverofficial

      mosaic-care
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      283 npm
      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 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: searching for patients, retrieving demographics, retrieving observations, and summarizing conditions. There is no overlap in purpose, and the descriptions reinforce clear boundaries.

    Naming Consistency5/5

    All tool names follow a clean verb_noun pattern in snake_case: search_patients, get_patient, get_observations, summarize_conditions. The verbs and nouns are consistent and predictable.

    Tool Count5/5

    Four tools is well-scoped for a read-only FHIR sandbox focused on patient data retrieval. Each tool earns its place, covering the core actions a user would need without unnecessary bloat.

    Completeness4/5

    The tool surface covers the main patient-centric workflows: find patient, view demographics, view observations, and summarize conditions. Minor gaps exist (e.g., no raw conditions list or medication history), but the core read-only purpose is well-served.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources