mcpbeat

Noaa Climate MCP Server

io.github.cyanheads/noaa-climate-mcp-server
answering

Noaa Climate MCP Server is answering right now. Last checked 6 min ago. 41 installs a week from npm. It exposes 7 tools. Last commit 30 Jul 2026.

Search NOAA climate stations and datasets, fetch historical weather observations.

Installs per day peak 28 · avg 6 · +21% w/w
a month agotoday
Uptime history 40 hours of history · worst hour 75%
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
361 ms
Response time
average over 24h
41
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add noaa-climate-mcp-server --transport http https://noaa-climate.caseyjhand.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "noaa-climate-mcp-server": {
      "url": "https://noaa-climate.caseyjhand.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.noaa-climate-mcp-server]
url = "https://noaa-climate.caseyjhand.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "noaa-climate-mcp-server": {
      "url": "https://noaa-climate.caseyjhand.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "noaa-climate-mcp-server": {
      "url": "https://noaa-climate.caseyjhand.com/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

noaa
noaa_climate_fetch_data
Fetch historical observation records from a NOAA CDO dataset for a given date range. Requires datasetId (e.g., GHCND for daily, GSOM for monthly), startDate, and endDate. Optionally scope to specific stations, locations, and data types. Date range limits per request: sub-daily and daily datasets (GHCND, PRECIP_15, PRECIP_HLY, NORMAL_DLY, NORMAL_HLY) are limited to 1 year; monthly and annual datasets (GSOM, GSOY, NORMAL_MLY, NORMAL_ANN) are limited to 10 years. For climate normals (NORMAL_*), use startDate=2010-01-01 and endDate=2010-12-31 — that is the API proxy year regardless of which 30-year period is being described. Returns flat tuples of { date, datatype, station, value, attributes }. Strongly recommended: pass units=metric or units=standard — without it, GHCND values are raw tenths-of-unit integers (TMAX=256 = 25.6°C, PRCP=12 = 1.2mm). GSOM/GSOY are already scaled.
noaa_climate_find_locations
Search for geographic locations by category (CITY, ST, CNTY, CNTRY, ZIP, CLIM_REG, etc.). Returns location IDs used in station search and data queries. Without locationCategoryId, returns all location types. Use locationCategoryId=ST to list US states (51 entries — small enough to retrieve completely). Use locationCategoryId=CITY for cities (thousands of entries — use pagination and sortField=name to navigate alphabetically). The CDO API has no name-search parameter; to find a specific city, sort alphabetically with sortField=name and page through results. Location IDs: states as FIPS:37 (NC), cities as CITY:US530031, zip codes as ZIP:98101, countries as CNTRY:US. Obtain location IDs here, then pass them to noaa_climate_find_stations or noaa_climate_fetch_data.
noaa_climate_find_stations
Search for weather observation stations by location, bounding box, dataset, and data type. Returns station IDs, names, coordinates, elevation, and data coverage dates. Filter by locationId (e.g., "FIPS:37" for all NC stations), extent (lat/lon bounding box), datasetId, datatypeId, and date range. Station IDs returned here are used as stationId in noaa_climate_fetch_data. A station must have data for the dataset and date range you want — filter by datasetId and startDate/endDate to ensure compatibility. Common station ID formats: GHCND:USC00450974, COOP:010008.
noaa_climate_get_station
Fetch full metadata for a single weather station by its ID (e.g., "GHCND:USC00450974", "COOP:010008"). Returns name, coordinates, elevation, and the full date range for which data is available. Use when you have a station ID from noaa_climate_find_stations and want its complete details, or to verify a station before querying data.
noaa_climate_list_data_categories
List data categories that group related data types — Temperature, Precipitation, Wind, Pressure, Sunshine, Sky cover, Weather Type, and more. Use to discover what types of measurements are available before calling noaa_climate_list_data_types. Optionally filter by dataset, location, station, or date range. There are 42 categories in total.
noaa_climate_list_data_types
List available data types (measurement labels like TMAX, TMIN, PRCP, SNOW) for a given dataset or category. Pass a datasetId to see what is measured in that dataset, or a datacategoryId (e.g., "TEMP") to see all temperature-related types. Hundreds of types exist across all datasets. Use this before calling noaa_climate_fetch_data when the data type IDs are unknown. Common GHCND types: TMAX (max temperature), TMIN (min temperature), PRCP (precipitation), SNOW (snowfall), SNWD (snow depth), AWND (average wind speed).
noaa_climate_list_datasets
List available NOAA CDO datasets with their IDs, names, and temporal coverage. Returns all ~11 datasets by default (no required parameters). Optionally filter to datasets that contain a specific data type, cover a location or station, or overlap a date range. Common datasets: GHCND (daily observations, 1763–present), GSOM (monthly summaries), GSOY (annual summaries), NORMAL_DLY/MLY/ANN/HLY (1981–2010 climate normals). Use this first to discover available datasets before calling noaa_climate_fetch_data.

Endpoints

URLTransportStateLatencyChecked
https://noaa-climate.caseyjhand.com/mcp streamable-http answering 422 ms 6 min ago

Noaa Climate MCP Server — questions

Answers built from our own checks of this server.

What can Noaa Climate MCP Server do?
It exposes 7 tools, read directly from the server on our last check. Among them: noaa_climate_fetch_data, noaa_climate_find_locations, noaa_climate_find_stations, noaa_climate_get_station, noaa_climate_list_data_categories, noaa_climate_list_datasets and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Noaa Climate MCP Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 361 ms. The bar chart above shows every period we have measured.
How do I connect Noaa Climate MCP Server?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Noaa Climate MCP Server need an API key?
No. Noaa Climate MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Noaa Climate MCP Server?
It answers our handshake in 361 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Noaa Climate MCP Server?
The npm package @cyanheads/noaa-climate-mcp-server was installed 41 times in the last week. Week over week that is +21%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Noaa Climate MCP Server open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript, 2 stars on GitHub and 3 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.