Skip to main content
Glama
lingeswaranTW

bahmni-mcp

by lingeswaranTW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to bahmni-mcp

No user-submitted related servers found.

    Related Servers

    • OpenAPI MCP Server

      luciVuc
      A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.
      23 npm
      MIT
    • FHIRfly MCP Server by FHIRfly-io

      FHIRfly MCP Serverofficial

      FHIRfly-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for connecting Claude Desktop to FHIRfly healthcare reference data APIs, enabling lookup of drugs, providers, clinical codes, and more.
      81 npm
      MIT

    • mcp-openapi-schema

      hannesj
      A
      license
      Not graded
      quality
      F
      maintenance
      A MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context
      163 npm
      49
      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

    C2.3/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools target distinct resources (patient, encounter, observation, etc.), but createOrUpdateEncounterTransaction bundles multiple data types including diagnoses and orders, causing potential overlap with individual getters. Overall, tools are mostly distinct.

    Naming Consistency3/5

    All names use camelCase and start with verbs (get, search, createOrUpdate), but verb choice is inconsistent (e.g., findEncounters vs getVisitsForPatient, manageVisits is vague). The pattern is readable but could be more uniform.

    Tool Count4/5

    19 tools is a reasonable scope for a healthcare MCP, covering core entities without being excessive. The count feels appropriate for the domain.

    Completeness2/5

    The tool surface heavily favors read operations; write operations are limited to patient profiles and a single composite encounter transaction. Missing separate create/update for observations, diagnoses, orders, etc., which will cause agent failures in common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources