Development Indicators MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host address to bind the MCP server when using streamable-http transport. Example: '127.0.0.1' or '0.0.0.0'. | |
| MCP_PORT | No | Port to bind the MCP server when using streamable-http transport. Example: '8000'. | |
| FAOSTAT_USER | No | Optional FAOSTAT username for authenticated data access. Required for the FAOSTAT smoke benchmark and certain FAOSTAT operations. | |
| MCP_TRANSPORT | No | Transport mode for the MCP server. Default is 'stdio'. Set to 'streamable-http' for a hosted-style HTTP endpoint. | stdio |
| FAOSTAT_PASSWORD | No | Optional FAOSTAT password for authenticated data access. Required alongside FAOSTAT_USER. | |
| UN_POPULATION_TOKEN | No | Optional bearer token issued by the UN Population portal, required for UN Population observation endpoints. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sourcesB | List supported and planned official data sources and their access characteristics. |
| get_source_setupB | Explain source access requirements without exposing server secrets. |
| find_microdataA | Find relevant public microdata catalogues and state their access conditions. |
| search_indicatorsC | Rank official indicators; returns match evidence, retrieval health and source failures. |
| faostat_list_domainsC | List live FAOSTAT groups and domains available to build source-qualified series. |
| faostat_search_dimensionC | Search a FAOSTAT domain's area, item, element, unit, or other definition table. |
| resolve_geographiesA | Resolve country names or codes to ISO 3166-1 alpha-3 codes such as GHA and KEN. |
| get_indicator_metadataB | Retrieve authoritative metadata for a source-qualified series reference. |
| get_observationsC | Retrieve official observations while retaining metadata, citations and warnings. |
| compare_observationsA | Retrieve series side by side and flag obvious metadata differences without merging them. |
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 10 tools
Each tool has a distinct purpose: listing sources, retrieving setup details, finding microdata, searching indicators, FAOSTAT-specific queries, geography resolution, metadata retrieval, observation retrieval, and comparison. Descriptions clearly differentiate overlapping areas like list_sources vs find_microdata.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_sources, get_observations, compare_observations). Prefixing FAOSTAT-specific tools with 'faostat_' adds a clear namespace without breaking the pattern.
With 10 tools, the server is well-scoped for discovering, searching, and retrieving development indicator data. This count is within the ideal range and each tool earns its place by covering a distinct part of the workflow.
The surface covers the full discovery-to-retrieval pipeline: source enumeration, search, metadata, observations, and comparison. Minor gaps exist (e.g., no bulk download or time-series filtering), but these are not severe dead ends for typical use cases.