Skip to main content
Glama
wso2

FHIR MCP Server

by wso2

Related Servers

Alternatives to FHIR MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to securely interact with FHIR healthcare servers and HL7 terminology services. Provides comprehensive healthcare data operations with built-in PHI protection, audit logging, and SMART on FHIR authentication.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Provides read/write access to any FHIR-compliant healthcare API with built-in validation, supporting resource management, search operations, and granular permissions through natural language.
      5
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables LLM-based agents to interact with FHIR healthcare data through natural language prompts, providing full CRUD operations on FHIR resources, document processing, and semantic search capabilities.
      13
      100
      MIT
    • 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.
      9 npm
      48 PyPI
      MIT

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose aligned with FHIR operations: create, delete, get_capabilities, get_user, read, search, and update. There is no overlap in functionality; for example, read retrieves a single resource by ID, while search queries multiple resources, and get_capabilities fetches metadata rather than resources. The descriptions reinforce these boundaries, making misselection unlikely.

    Naming Consistency4/5

    The naming is mostly consistent with a verb-based pattern (create, delete, read, search, update) and underscores for multi-word names (get_capabilities, get_user). However, get_capabilities and get_user deviate slightly from the simpler verb style of other tools, though they remain readable and follow a similar structure. This minor inconsistency prevents a perfect score.

    Tool Count5/5

    With 7 tools, this server is well-scoped for FHIR operations, covering core interactions like CRUD (create, read, update, delete), search, metadata discovery (get_capabilities), and user context (get_user). Each tool earns its place without redundancy, and the count is typical for a domain-specific server, avoiding bloat or thin coverage.

    Completeness5/5

    The tool set provides complete coverage for FHIR interactions, including all essential CRUD operations (create, read, update, delete), search for queries, get_capabilities for metadata discovery, and get_user for authentication context. There are no obvious gaps; agents can perform full lifecycle management and queries without dead ends in this domain.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive