Civic Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_TIMEOUT | No | Request timeout in seconds | 30 |
| NASA_API_KEY | No | Optional API key for NASA APIs to get higher rate limits (1000/hr vs 30/hr) | |
| OPENWEATHER_API_KEY | No | API key for OpenWeather to enable global weather conditions. Get a free key at https://openweathermap.org/api |
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 |
|---|---|
| get_weather_forecastA | Get weather forecast for a US location by coordinates. |
| get_weather_alertsA | Get active weather alerts for a US state. |
| get_global_weatherA | Get current weather for any city worldwide (requires OPENWEATHER_API_KEY). |
| query_noaaB | Make a raw query to the NOAA Weather API. |
| query_openweatherA | Make a raw query to the OpenWeather API (requires OPENWEATHER_API_KEY). |
| get_populationA | Get population data for a US state or county. |
| get_demographicsA | Get demographic breakdown for a US state or county. |
| get_housing_statsB | Get housing statistics for a US state or county. |
| query_censusA | Make a raw query to the Census API. |
| get_astronomy_photoA | Get NASA's Astronomy Picture of the Day (APOD). |
| get_mars_rover_photosA | Get photos from Mars rovers (Curiosity, Opportunity, Spirit, Perseverance). |
| search_nasa_imagesB | Search NASA's image and video library. |
| query_nasaC | Make a raw query to the NASA API. |
| get_country_indicatorsB | Get economic indicators for a country from the World Bank. |
| compare_countriesB | Compare an economic indicator across multiple countries. |
| query_worldbankB | Make a raw query to the World Bank API. |
| search_datasetsA | Search for datasets on Data.gov. |
| get_dataset_infoB | Get detailed information about a specific Data.gov dataset. |
| query_datagovC | Make a raw query to the Data.gov CKAN API. |
| search_eu_datasetsB | Search for datasets on the European Union Open Data Portal. |
| get_eu_dataset_infoC | Get detailed information about a specific EU Open Data dataset. |
| query_eu_dataC | Make a raw query to the EU Open Data Portal API. |
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 22 tools
Tools are grouped by data source and purpose, but there is significant overlap. For example, get_country_indicators and compare_countries both use World Bank data, and get_weather_forecast and get_global_weather both provide weather information. Descriptions help clarify, but an agent might struggle to choose between overlapping tools like query_nasa and get_astronomy_photo.
Most tools follow a consistent verb_noun pattern (e.g., get_country_indicators, search_datasets, query_census). However, there are minor deviations, such as compare_countries (verb_noun but not 'get' or 'query') and get_astronomy_photo (abbreviated 'photo' instead of 'picture'). Overall, the naming is readable and predictable.
With 22 tools, the count feels heavy for a 'Civic Data' server, as it spans multiple unrelated domains like astronomy, Mars photos, and global weather. This suggests a lack of focus; a more cohesive set might have 10-15 tools centered on government or economic data. The broad scope makes the toolset overwhelming and less coherent.
For each data source (e.g., World Bank, NASA, NOAA), there is basic coverage with get/search/query tools, but gaps exist. For instance, there are no update or delete operations, which is reasonable for read-only data, but some domains lack comprehensive endpoints (e.g., limited NASA tools beyond APOD and images). The surface is functional but not fully rounded for all implied use cases.