Skip to main content
Glama
GattaniAkshit

medmcp

by GattaniAkshit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to medmcp

No user-submitted related servers found.

    Related Servers

    • M4

      hannesill
      A
      license
      B
      quality
      D
      maintenance
      Query clinical datasets like MIMIC-IV and eICU with natural language, supporting both tabular EHR data and clinical notes through a unified interface.
      11
      43
      MIT

    • data-agent-service

      calvinchengx
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language queries over data warehouses with catalog-grounded semantics and per-query authorization, returning answers with attached reasoning.
      Apache 2.0

    • Claims Data MCP Server

      Rutvikmerai
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language querying of healthcare claims data by exposing a SQLite database with read-only SQL tools, allowing users to ask questions in plain English and get answers backed by real database queries.
      -

    • Datum

      malharinamdar
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language querying of SQLite databases through a governed semantic layer, with citations and typed abstention for PII or uncertified data.
      -

    • OMOP MCP Server

      aandresalvarez
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language exploration of OMOP CDM databases for concept discovery, patient count queries, and cohort SQL generation with support for multiple database backends.
      1
      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.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: patient search, admissions lookup, lab results retrieval, and data aggregation. There is no overlap in their intended actions or target data, making misselection unlikely.

    Naming Consistency4/5

    Three tools follow the verb_noun pattern (find_patients, get_admissions, get_labs), while 'aggregate' is a single verb without a noun. This is a minor deviation but still readable and predictable overall.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped to core MIMIC-IV demo queries. Each tool covers a significant workflow, and the count is well within the ideal range for a focused medical data access server.

    Completeness4/5

    The tools cover patient lookup, admissions, labs, and aggregation, which handles most basic exploratory queries. Missing operations like diagnosis or medication retrieval are notable but not critical given the demo scope, so agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources