Skip to main content
Glama
erikhoward

Azure AHDS FHIR MCP Server

by erikhoward

Related Servers

Alternatives to Azure AHDS FHIR MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that connects AI tools to Electronic Health Records using SMART on FHIR, allowing secure searching, querying, and analysis of patient data from compatible EHRs.
      87
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables querying FHIR healthcare data using natural language, allowing doctors to retrieve patient information, medications, observations, and other healthcare records.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides healthcare tools for interacting with FHIR data and medical resources on EMRs like Cerner and Epic
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server that provides universal access to multiple FHIR servers with AI-powered clinical analysis capabilities for healthcare data integration and patient care planning.
      3
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server that bridges AI applications with FHIR healthcare data systems, enabling patient data access, clinical data retrieval, and data quality assessment.
      4
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A server that implements the Model Context Protocol (MCP) with StreamableHTTP transport, enabling standardized interaction with model services through a RESTful API interface.
      335 npm
      2
      MIT

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search_fhir' has a clearly defined purpose focused on FHIR search operations.

    Naming Consistency5/5

    The naming follows a consistent snake_case pattern with a clear verb_noun structure ('search_fhir'). With only one tool, there is no inconsistency to evaluate.

    Tool Count2/5

    A single tool for an FHIR server is insufficient for comprehensive coverage of FHIR operations. FHIR domains typically require CRUD operations (create, read, update, delete) and other interactions beyond just search, making this server feel thin and incomplete for its purpose.

    Completeness2/5

    The tool surface is severely incomplete for an FHIR server. While the search functionality is detailed, there are significant gaps in basic FHIR operations like creating, reading, updating, or deleting resources, which are essential for full FHIR lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues