dhis2-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DHIS2_BASE_URL | No | Base URL of the DHIS2 instance | https://play.im.dhis2.org/stable-2-43-1 |
| DHIS2_PASSWORD | No | Basic auth password | district |
| DHIS2_USERNAME | No | Basic auth username | admin |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_indicatorsA | Search DHIS2 indicators by name. Returns id, name, and description for each match. |
| query_analyticsA | Get aggregated values for one indicator, split by period, for one organisation unit. Run search_indicators first to get the indicator id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
Both tools follow the same verb_noun pattern with snake_case naming (search_indicators, query_analytics), making the naming perfectly consistent and predictable.
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.
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.