Search NOAA CDO stations and datasets, fetch historical weather observations.
Most cloud and infrastructure work still happens through a UI a human drives. Noaa MCP server moves it into the conversation instead. Search NOAA CDO stations and datasets, fetch historical weather observations.
The server publishes 9 tools. What each one is for:
noaa_climate_list_datasets — List available CDO datasets with IDs, names, and temporal coveragenoaa_climate_list_data_categories — List data category groups (Temperature, Precipitation, Wind, etc.)noaa_climate_list_data_types — List specific measurement labels (TMAX, TMIN, PRCP, SNOW, etc.) by dataset or categorynoaa_climate_find_locations — Search geographic locations by category (states, cities, counties, zip codes, climate regions)noaa_climate_find_stations — Search weather stations by location, bounding box, dataset, and data typenoaa_climate_get_station — Fetch full metadata for a single station by IDnoaa_climate_fetch_data — Fetch historical observation records for a dataset and date rangePrerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration is passed through the environment: MCP_TRANSPORT_TYPE, MCP_LOG_LEVEL, NOAA_CDO_TOKEN, MCP_HTTP_ENDPOINT_PATH, MCP_PUBLIC_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Noaa's toolset — noaa_climate_list_datasets, noaa_climate_list_data_categories, noaa_climate_list_data_types and 6 more — is a fair guide to whether it matches your workflow. It is maintained by cyanheads; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| noaa_climate_list_datasets | List available CDO datasets with IDs, names, and temporal coverage |
| noaa_climate_list_data_categories | List data category groups (Temperature, Precipitation, Wind, etc.) |
| noaa_climate_list_data_types | List specific measurement labels (TMAX, TMIN, PRCP, SNOW, etc.) by dataset or category |
| noaa_climate_find_locations | Search geographic locations by category (states, cities, counties, zip codes, climate regions) |
| noaa_climate_find_stations | Search weather stations by location, bounding box, dataset, and data type |
| noaa_climate_get_station | Fetch full metadata for a single station by ID |
| noaa_climate_fetch_data | Fetch historical observation records for a dataset and date range |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
{
"mcpServers": {
"noaa-climate-mcp-server": {
"type": "stdio",
"command": "bunx",
"args": ["@cyanheads/noaa-climate-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info",
"NOAA_CDO_TOKEN": "your-token-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_TRANSPORT_TYPE | Configuration value read at startup. | Optional |
| MCP_LOG_LEVEL | Configuration value read at startup. | Optional |
| NOAA_CDO_TOKEN | Credential the server authenticates with. | Yes |
| MCP_HTTP_ENDPOINT_PATH | Filesystem location the server is allowed to use. | Optional |
| MCP_PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.