Log inSubmit server
Noaa Cdo MCP Server logo

Noaa Cdo MCP Server

Query NOAA climate datasets, stations, historical observations, storm events, and billion-dollar disaster records through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Noaa Cdo MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "noaa-cdo-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/noaa-climate-mcp-server"
      ],
      "env": {
        "NOAA_CDO_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @cyanheads/noaa-climate-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.

Overview

noaa-cdo-mcp-server MCP server exposes NOAA Climate Data Online, NCEI Storm Events, and Billion-Dollar Weather and Climate Disasters through MCP tools. It helps agents discover datasets, locations, stations, and measurement types before retrieving historical observations or disaster records. Reach for it when an agent needs structured NOAA climate data, station metadata, storm details, or disaster cost and casualty figures.

Use cases

  • Find stations with temperature observations in a geographic area
  • Retrieve historical precipitation or snowfall records for a date range
  • Search storm events for damage, casualties, and narratives
  • Compare billion-dollar disaster costs by year or disaster class

Key features

  • NOAA CDO dataset and measurement discovery
  • Location and weather-station search
  • Historical observation retrieval
  • NCEI storm event search
  • Billion-dollar disaster queries
  • STDIO and Streamable HTTP support

Tools10

What Noaa Cdo MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~288 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

6/6 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @cyanheads/noaa-climate-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed10Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Noaa Cdo MCP Server works

What noaa-cdo-mcp-server does

The noaa-cdo-mcp-server MCP server gives an MCP client access to NOAA climate and weather records. Its main data source is Climate Data Online (CDO), which provides dataset catalogs, measurement categories, geographic locations, weather stations, station metadata, and historical observations. It also exposes searches for the NCEI Storm Events Database and queries for NOAA's Billion-Dollar Weather and Climate Disasters.

The server provides 10 tools and two resources. The noaa://datasets resource supplies CDO dataset information, while noaa://stations/{stationId} provides metadata for a specified station. Together, the discovery tools and resources support a workflow that starts with identifying the appropriate dataset, location, station, and measurement type before requesting records.

How it works

Use the catalog tools to inspect available datasets, data categories, data types, and location categories. Location searches can cover states, cities, counties, ZIP codes, and climate regions. Station searches accept location IDs, geographic bounding boxes, datasets, data types, and date ranges, and return station IDs along with coordinates, elevation, and coverage dates.

Historical observations come from noaa_climate_fetch_data. The request requires a dataset and date range, and can be narrowed by station, location, or data type. Results use flat records containing the date, datatype, station, value, and attributes. Metric or standard units should be requested explicitly; otherwise, GHCND values are returned as raw tenths-of-unit integers.

Storm searches require a year and can filter by state, event type, month, episode, or minimum damage. Results include event details, narratives, casualties, and damage fields when reported. Disaster queries can return individual CPI-adjusted costs and deaths or yearly totals grouped by disaster class.

Setup and configuration

The noaa-cdo-mcp-server MCP server can run through STDIO or Streamable HTTP. The repository provides an npm package, a Docker package, install links for Claude Desktop, Cursor, and VS Code, and a public hosted endpoint at https://noaa-climate.caseyjhand.com/mcp.

Local use requires the NOAA_CDO_TOKEN environment variable for CDO access. The Storm Events search does not require a token. The repository's client installation configuration runs the package with npx and passes the token through the environment.

Tools and capabilities

  • Enumerate CDO datasets, categories, measurement types, and location categories.
  • Find locations using category-specific searches and optional name filters.
  • Find stations by location, bounding box, dataset, data type, and date range.
  • Retrieve complete station metadata and historical observations.
  • Search one year's NCEI storm events, including damage and narratives.
  • Query billion-dollar disasters by event or annual disaster-class totals.
  • Use pagination, sorting, date filters, and result limits on supported catalog and search operations.

Limitations and notes

Observation requests have dataset-specific date-span limits. Several daily datasets allow a maximum one-year span, while monthly, annual, and monthly or annual normal datasets allow up to 10 years. Normal datasets require the date range from January 1 through December 31, 2010. Storm event searches support years from 1950 through the current partial year, and a year may fail when NCEI has not published a file.

The location name filter requires a location category and is capped for categories with more than 4,000 locations; ZIP-code searches do not support that name-filter path. Station and data queries depend on valid IDs returned by the discovery tools. Damage values may be absent when NCEI reported no damage, rather than represented as zero. The repository identifies the project under the Environment & Nature category and licenses it under Apache-2.0.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Noaa Cdo MCP Server

noaa-cdo-mcp-server is an MCP server that connects AI clients to NOAA Climate Data Online, the NCEI Storm Events Database, and NOAA’s Billion-Dollar Weather and Climate Disasters. Its tools discover datasets, locations, stations, and data types, fetch historical observations, search storm events, and query disaster costs and deaths.

Install it with the repository’s client configuration or run its npm package with `npx`; local CDO access requires `NOAA_CDO_TOKEN`. The project also provides a Docker package, STDIO and Streamable HTTP modes, and a public hosted MCP endpoint.

Yes, noaa-cdo-mcp-server includes a Cursor installation link. The provided configuration runs the npm package with `npx` and passes `NOAA_CDO_TOKEN` as an environment variable.

Call `noaa_climate_fetch_data` with a dataset ID, start date, and end date, then optionally add station IDs, location IDs, or data type IDs. Discover valid values with the dataset, location, station, and data-type tools first, and request metric or standard units for readable values.

Yes, the Storm Events search does not require a token. Use `noaa_climate_search_storm_events` with a required year and optional filters such as state, event type, month, episode ID, or minimum damage.

Related MCP servers

All in Environment & Nature All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNoaa Cdo MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/noaa-cdo-mcp-server?style=directory)](https://allmcps.com/mcp/noaa-cdo-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/noaa-cdo-mcp-server"><img src="https://allmcps.com/api/badge/noaa-cdo-mcp-server?style=directory" alt="Noaa Cdo MCP Server on AllMCPs" /></a>