@cyanheads/who-gho-mcp-server
Query WHO Global Health Observatory data — 3,102 indicators across 194 member states with country, region, year, and sex filters via MCP. STDIO or Streamable HTTP.
6 Tools • 4 Data Resources • 1 Skill
Overview
Global health statistics from the WHO Global Health Observatory: 3,102 indicators across 194 member states. Search indicators and query data by country, region, income group, sex, and year.
Tools
Resources
Each mirrors data also reachable via who_get_indicator_metadata and who_list_dimension_values — useful for clients that inject resources as context but don't call tools.
Agent skill
who-gho-guide covers dimension-position discovery, complete country comparisons, and countries versus regional aggregates. It ships with plugin installs, npm, Docker, and the MCPB bundle. MCP clients can discover its SKILL.md through resources/list or the io.modelcontextprotocol/skills extension (skills/list, skills/get, and resources/directory/read); the server also exposes the skill://{+path} resource template.
Capability reference
who_search_indicators tool
- Each whitespace-separated word must match a substring in the indicator name, in any order; no stemming or fuzzy expansion. If names have no matches, an exact indicator-code lookup is attempted.
- Returns indicator codes and display names for use with
who_query_indicator_data
- Offset-based pagination (
offset, default 0) with limit default 20, max 100; reports totalCount, hasMore, pageInfo, nextOffset
- An offset at or beyond
totalCount returns an empty page; a no_results error is raised only when nothing matches at all
who_list_indicators tool
- No keyword required — browse the 3,102-indicator catalog
- Offset-based pagination via
limit (default 50, max 500) and offset
- Returns
totalCount and hasMore for iteration
who_get_indicator_metadata tool
- Accepts up to 1,000 indicator codes and processes the first 10 in parallel; submit returned
unprocessedCodes next. With GHO_CLAMP_LIMITS=false, batches over 10 are rejected.
- Returns the full indicator name and supported dimension types (e.g.
COUNTRY, SEX, REGION, AGEGROUP) for each resolved code
- Indicators with no dimension listing upstream return
dimensions: [] plus a dimensionsNote pointing at a sample data row's dimension type/value pairs. Metadata does not identify dimension positions.
- Codes resolving to neither a catalog entry nor dimension rows land in
notFound; the call fails when no processed code resolves and no unprocessed codes remain
who_list_dimensions tool
- No inputs — returns every dimension type code and human-readable title in the GHO catalog
- Common types:
COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, AGEGROUP
- Use to discover codes before calling
who_list_dimension_values
who_list_dimension_values tool
- Returns codes and labels for the dimension's values (e.g. the 234 country entries, the 43 WHO region codes), plus optional parent-hierarchy fields (
parentCode, parentLabel, parentDimension)
parent_code narrows hierarchical dimensions — dimension: "COUNTRY" with parent_code: "EUR" returns the 58 countries in the WHO European Region
- Deterministic ordering by
Code; offset-based pagination (offset) with limit default 100, max 500 — GHO (3,103 values) and DHSMICSGEOREGION (4,932) need paging
- A
parent_code that matches nothing returns an empty page for a known dimension; unknown dimensions fail even with a parent filter
- An unpaired UTF-16 surrogate in
dimension fails as a typed malformed_identifier validation error
who_query_indicator_data tool
- Spatial filters are mutually exclusive per call:
country_codes (WHO country codes, including historical entries), region_codes (WHO aggregate rows), or income_group_codes (World Bank aggregate rows) — supplying more than one is a validation error
year_from / year_to time range; sex (SEX_BTSX, SEX_FMLE, SEX_MLE) applies only when the indicator's first cross-cutting dimension is SEX. dim1_value, dim2_value, and dim3_value select observed positional values; discover positions from returned type/value pairs, not metadata. sex overrides dim1_value with a notice.
include_uncertainty (default true) adds low/high bounds; sort (year_desc default or year_asc) with a total row ordering so paging never repeats or drops rows
- Offset-based pagination with
limit default 200, max 1000; reports totalRows, hasMore, pageInfo, nextOffset
- Typed failure reasons:
indicator_not_found, no_data, ambiguous_spatial_filter, invalid_year_range, invalid_query, malformed_identifier
who://indicator/{indicatorCode}/metadata resource
- Indicator name and supported filter dimensions as
application/json
indicatorCode comes from who_search_indicators or who_list_indicators
- Empty
dimensions carries a dimensionsNote when the upstream dimension table lists none for the code, rather than reporting a missing indicator
- Returns a 404 error only when the code resolves to neither a catalog name nor any dimension rows
who://dimension/{dimensionCode}/values resource
- Bare URI returns the first 100 values for the dimension (
dimensionCode from who_list_dimensions), as application/json
- Registered separately from the two paged variants below because the MCP SDK's RFC 6570 matcher treats every URI query variable as required — one template cannot serve both a bare and a paged form
- An unfiltered empty result means the dimension code does not exist
who://dimension/{dimensionCode}/values{?limit,offset} resource
limit (1–500) and offset must both be present in the URI — the query variables are required, not optional
- Same page fields as the bare URI:
totalCount, hasMore, nextOffset, and an optional notice
- An offset at or beyond
totalCount returns an empty page, not an error
who://dimension/{dimensionCode}/values{?limit,offset,parentCode} resource
- Adds
parentCode to narrow to one parent value, e.g. parentCode="EUR" for countries in the WHO European Region; limit, offset, and parentCode must all be present in the URI
- A
parentCode that matches nothing returns an empty page for a known dimension; unknown dimensions fail even with a parent filter
- Same output shape as the bare and paged resources:
dimension, values, totalCount, hasMore, nextOffset, notice
Features
Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.
WHO GHO-specific:
- Full coverage of the WHO GHO OData API v2 — indicators, dimensions, dimension values, and data queries
- Configurable base URL and service-operation deadline (
GHO_BASE_URL, GHO_REQUEST_TIMEOUT_MS) for custom or mirrored deployments
- Parallel metadata fan-out for multi-code indicator lookups
- Deterministic, total row/value ordering — pagination never repeats or drops rows across pages
Agent-friendly output:
- Tool descriptions encode the cross-tool workflow — agents discover the right call order (search → metadata → query) from descriptions alone
- Structured pagination signaling (
hasMore, nextOffset, pageInfo, and truncated on the data-query tool) so agents can decide whether to page further
- Discriminated, typed error reasons with a
recovery hint on every failure path
- Distinct empty-page vs. not-found semantics — paging past the end, an unmatched filter, and a genuinely missing code each report differently instead of colliding into one generic empty result
Getting started
Public Hosted Instance
A public instance is available at https://who-gho.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP:
Self-Hosted / Local
Add the following to your MCP client configuration file.
Or with npx (no Bun required):
Or with Docker:
For Streamable HTTP, set the transport and start the server:
Prerequisites
- Bun v1.4.0 or higher (or Node.js ≥24).
- No API key required — the WHO GHO API is public.
Installation
- Clone the repository:
- Navigate into the directory:
- Install dependencies:
- Configure environment:
Configuration
See .env.example for the full list of optional overrides.
Running the server
Local development
Docker
The Dockerfile defaults to HTTP transport, stateless session mode, and logs to /var/log/who-gho-mcp-server. OpenTelemetry peer dependencies are installed by default — build with --build-arg OTEL_ENABLED=false to omit them.
Project structure
Development guide
See CLAUDE.md for development guidelines and architectural rules. The short version:
- Handlers throw, framework catches — no
try/catch in tool logic
- Use
ctx.log for logging, ctx.state for storage
- Register new tools and resources in the
createApp() arrays
- Wrap external API calls: validate raw → normalize to domain type → return output schema; never fabricate missing fields
Contributing
Issues are welcome. Run checks and tests before submitting:
License
Apache-2.0 — see LICENSE for details.