Noaa Cdo Mcp Server
Connect NOAA Climate Data Online stations, datasets, and historical observations to your agent for weather analytics, agritech, or climate-aware product features.
Overview
io.github.cyanheads/noaa-cdo-mcp-server is a MCP server for the Build phase that searches NOAA CDO stations and datasets and fetches historical weather observations through your agent.
What is this MCP server?
- Search NOAA CDO stations and datasets with agent-callable tools
- Fetch historical weather observations for time-series and reporting features
- Requires free NOAA_CDO_TOKEN from ncdc.noaa.gov CDO token page
- v0.1.9 package with stdio, localhost HTTP, and remote noaa-cdo.caseyjhand.com/mcp
- MCP_LOG_LEVEL env for operational visibility
- NOAA_CDO_TOKEN marked isRequired in server environment schema
- Package version 0.1.9 as @cyanheads/noaa-cdo-mcp-server
- Remote MCP endpoint documented at noaa-cdo.caseyjhand.com/mcp
Community signal: 2 GitHub stars.
What problem does it solve?
Climate and weather features bog down on NOAA CDO auth, station IDs, and dataset discovery when you only want the agent to pull series in-context.
Who is it for?
Builders integrating authoritative US climate observations into SaaS, research, or IoT-adjacent products via MCP-enabled agents.
Skip if: Real-time hyperlocal forecasting stacks that need proprietary radar models without NOAA CDO’s historical focus and token limits.
What do I get? / Deliverables
Once configured with a CDO token, your agent can query stations and observations so charts, alerts, and analytics prototypes land faster.
- Station and dataset discovery via agent tools
- Historical observation payloads for charts and exports
- Repeatable CDO queries without custom REST boilerplate
Recommended MCP Servers
Journey fit
Historical weather and station metadata are integration-heavy datasets; builders pull them during product construction rather than abstract ideation alone. Integrations subphase fits CDO token-backed API access exposed as MCP tools for charts, alerts, and research features in your app.
How it compares
NOAA CDO data MCP bridge, not a commercial weather widget or full data warehouse.
Common Questions / FAQ
Who is io.github.cyanheads/noaa-cdo-mcp-server for?
It is for indie developers and data-minded solo builders who use AI agents and need NOAA historical climate and weather series during product integration.
When should I use io.github.cyanheads/noaa-cdo-mcp-server?
Use it while building features that depend on station search, dataset selection, or historical observations from NOAA Climate Data Online.
How do I add io.github.cyanheads/noaa-cdo-mcp-server to my agent?
Obtain NOAA_CDO_TOKEN from the NOAA CDO web token page, install @cyanheads/noaa-cdo-mcp-server, add stdio or HTTP MCP config, and set MCP_LOG_LEVEL if needed.