Skip to main content
Glama
pcmedsinge

fhir-mcp-suite

by pcmedsinge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to fhir-mcp-suite

No user-submitted related servers found.

    Related Servers

    • 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

    • MediLinkAI

      MiChaelinzo
      A
      license
      Not graded
      quality
      D
      maintenance
      Clinical decision-support MCP server that lets AI agents reason over live FHIR patient data for medication review, appointment scheduling, and care gap identification.
      5,766 npm
      MIT

    • sharp-on-fhir-mcp

      TerminallyLazy
      A
      license
      Not graded
      quality
      C
      maintenance
      A clean-room SHARP-on-MCP compliant FHIR R4 MCP server that enables AI agents to interact with any FHIR R4 endpoint using SHARP context headers, without server-side OAuth. It provides clinical tools, lab results, imaging, and interactive MCP-UI dashboards.
      MIT

    • HealthClawGuardrails

      aks129
      A
      license
      A
      quality
      A
      maintenance
      Open-source guardrails between AI agents and FHIR clinical data — PHI redaction, immutable audit, step-up auth, tenant isolation. MCP server + OpenAI/Gemini adapters. A healthclaw.io project.
      29
      30
      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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a unique and clearly distinct purpose: capabilities for metadata, read for single resource retrieval, search for querying, search_next for pagination, and validate for conformance checking. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., fhir_read, fhir_search). The 'fhir_' prefix is used uniformly, and each name clearly describes the action and domain.

    Tool Count4/5

    With 5 tools, the set is appropriately scoped for a focused FHIR read/search/validation suite. It is not excessive, and each tool provides essential functionality. A slightly higher count could cover write operations, but the current number is reasonable.

    Completeness3/5

    The tool set covers capabilities, read, search, pagination, and validation, but lacks write operations (create, update, delete), history, and transaction support. For a full FHIR interaction, these missing operations are notable gaps, though the validation focus partially justifies the omission.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources