The dhis2w FastMCP server and the MCP tools of every built-in dhis2w-core plugin.
Until 2026-09-24 this record combined several servers published from one repository. The others now have records of their own: dhis2w-mcp-bridge, dhis2w-mcp-router. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"dhis2w-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# dhis2w-mcp FastMCP server that exposes every `dhis2w-core` plugin as MCP tools. Same service functions as the CLI; different I/O shape. A connected agent (Claude Desktop, Claude Code, Cursor, …) sees roughly 304 typed tools grouped by plugin: `metadata_*`, `data_aggregate_*`, `data_tracker_*`, `analytics_*`, `route_*`, `user_*`, `apps_*`, `system_*`, `messaging_*`, `files_*`, `maintenance_*`, `customize_*`, `profile_*`, `doctor_*`. Counts age with each release; the generated `docs/tool-reference.md` is the source of truth. ## Install ### From PyPI (recommended) ```bash # As a global tool — drops `dhis2w-mcp` on $PATH (one-time fetch, instant launches) uv tool install dhis2w-mcp # Update to the latest release uv tool upgrade dhis2w-mcp # Force re-install (after PyPI publish issues / cache weirdness) uv tool install --reinstall dhis2w-mcp # Remove uv tool uninstall dhis2w-mcp # Or run on demand without installing — fetches into the uv cache on first run uvx dhis2w-mcp # Force a refresh (pulls latest published version, bypasses cache) uvx --refresh dhis2w-mcp ``` The PyPI distribution name and the binary name match (`dhis2w-mcp` for both), so unlike `dhis2w-cli` (whose binary is `d2w`), no `--from` dance is needed. ### From a workspace checkout (for active development) ```bash git clone [email protected]:winterop-com/dhis2w-mcp.git cd dhis2w-mcp uv sync --all-packages ``` This puts `dhis2w-mcp` on the workspace venv's path. `uv run dhis2w-mcp` from anywhere inside the repo speaks MCP over stdio. ## Configure your MCP client The server speaks MCP over stdio and reads its DHIS2 connection from either a profile (the workspace's `.dhis2/profiles.toml` / `~/.config/dhis2/profiles.toml`) or environment variables (`DHIS2_URL` + auth — `DHIS2_PASSWORD`, `DHIS2_PAT`, or OAuth2). Pick whichever fits your client. ### Claude Desktop Edit your config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\Claude\claude_desktop_confi…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.