Skip to main content
Glama
brianmituka

dhis2-mcp

by brianmituka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to dhis2-mcp

No user-submitted related servers found.

    Related Servers

    • DHIS2 MCP Server

      ahasan722
      A
      license
      A
      quality
      D
      maintenance
      Connects DHIS2 health information systems to AI assistants via the Model Context Protocol, enabling natural language queries for analytics, metadata, and tracker data.
      13
      MIT

    • WHO MCP Server

      openpharma-org
      A
      license
      B
      quality
      D
      maintenance
      Provides access to the World Health Organization's Global Health Observatory data, enabling AI assistants to search, retrieve, and analyze comprehensive health indicators, country statistics, disease burden data, and regional health trends through WHO's OData API.
      1
      MIT

    • DHIS2 MCP Server

      Dradebo
      A
      license
      B
      quality
      F
      maintenance
      Enables comprehensive interaction with DHIS2 health information systems through 40+ tools covering complete Web API functionality. Supports data management, tracker programs, analytics, and bulk operations for DHIS2 development and administration.
      47
      8 npm
      7
      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 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: search_indicators handles metadata discovery while query_analytics retrieves aggregated data. The explicit dependency between them removes any ambiguity.

    Naming Consistency5/5

    Both tools follow the same verb_noun pattern with snake_case naming (search_indicators, query_analytics), making the naming perfectly consistent and predictable.

    Tool Count2/5

    Two tools feels very thin for a DHIS2 server, which typically covers a broad health information system domain. The server only exposes a small analytics niche, so the count does not match the implied scope.

    Completeness3/5

    The core workflow of searching for indicators then querying analytics is present, but there is no way to discover organization units, periods, or other metadata within the server. This forces agents to obtain those identifiers from outside the tool surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources