Skip to main content
Glama

noaa-cdo-mcp-server

by io.github.cyanheads
OverviewDiscussionsAdmin

Server Details

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

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 42 days
Last Tested
Transport
Streamable HTTP
URL
Repository
cyanheads/noaa-climate-mcp-server
GitHub Stars
4
Server Listing
NOAA Climate MCP Server

TDQS

A4.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct aspect of the NOAA CDO API: data fetching, location searching, station searching, station details, data categories, datasets, and data types. There is no overlap in functionality.

Naming Consistency5/5

All tools follow a consistent pattern: 'noaa_' prefix with a verb_noun structure (fetch_data, find_locations, find_stations, get_station, list_data_categories, list_datasets, list_data_types).

Tool Count5/5

7 tools is well-scoped for a weather data retrieval server, covering discovery (datasets, categories, types, locations, stations) and data fetching without unnecessary bloat.

Completeness5/5

The tool surface covers the full discovery-to-data workflow: discover datasets, categories, types, locations, and stations, then fetch data and get station details. No obvious gaps for the read-only API domain.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changednoaa_find_locations1 field changed
      • changedInput schema / properties / locationCategoryId / description
        Previous value: -"Category filter. Use ST for states (~52 entries), CNTY for counties, CITY for cities (large set — thousands of entries), CNTRY for countries, ZIP for zip codes, CLIM_REG for NOAA climate regions, CLIM_DIV for climate divisions, HYD_ACC/HYD_CAT/HYD_REG/HYD_SUB for hydrological categories. Optional — omit to return all location types."New value: +"Category filter. Use ST for states (51 entries), CNTY for counties, CITY for cities (large set — thousands of entries), CNTRY for countries, ZIP for zip codes, CLIM_REG for NOAA climate regions, CLIM_DIV for climate divisions, HYD_ACC/HYD_CAT/HYD_REG/HYD_SUB for hydrological categories. Optional — omit to return all location types."
  2. 6 tool updates
    • Changednoaa_fetch_data4 fields changed
      • addedOutput schema / properties / effectiveQuery
        Added value: +{
+  "description": "Summary of the effective query: dataset, date range, units, and any station/location/datatype filters applied.",
+  "type": "string"
+}
      • addedOutput schema / properties / notice
        Added value: +{
+  "description": "Guidance when no records were returned — echoes query parameters and suggests how to broaden.",
+  "type": "string"
+}
      • addedOutput schema / properties / totalCount
        Added value: +{
+  "description": "Total number of matching observation records before the page limit.",
+  "type": "number"
+}
      • changedOutput schema / required
        Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "totalCount",
+  "effectiveQuery"
+]
    • Changednoaa_find_locations3 fields changed
      • addedOutput schema / properties / notice
        Added value: +{
+  "description": "Guidance when no locations matched — echoes applied filters and suggests how to broaden.",
+  "type": "string"
+}
      • addedOutput schema / properties / totalCount
        Added value: +{
+  "description": "Total number of matching locations before the page limit.",
+  "type": "number"
+}
      • changedOutput schema / required
        Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "totalCount"
+]
    • Changednoaa_find_stations3 fields changed
      • addedOutput schema / properties / notice
        Added value: +{
+  "description": "Guidance when no stations matched — echoes applied filters and suggests how to broaden.",
+  "type": "string"
+}
      • addedOutput schema / properties / totalCount
        Added value: +{
+  "description": "Total number of matching stations before the page limit.",
+  "type": "number"
+}
      • changedOutput schema / required
        Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "totalCount"
+]
    • Changednoaa_list_data_categories3 fields changed
      • addedOutput schema / properties / notice
        Added value: +{
+  "description": "Guidance when no data categories matched — echoes applied filters and suggests how to broaden.",
+  "type": "string"
+}
      • addedOutput schema / properties / totalCount
        Added value: +{
+  "description": "Total number of matching data categories before the page limit.",
+  "type": "number"
+}
      • changedOutput schema / required
        Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "totalCount"
+]
    • Changednoaa_list_data_types3 fields changed
      • addedOutput schema / properties / notice
        Added value: +{
+  "description": "Guidance when no data types matched — echoes applied filters and suggests how to broaden.",
+  "type": "string"
+}
      • addedOutput schema / properties / totalCount
        Added value: +{
+  "description": "Total number of matching data types before the page limit.",
+  "type": "number"
+}
      • changedOutput schema / required
        Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "totalCount"
+]
    • Changednoaa_list_datasets3 fields changed
      • addedOutput schema / properties / notice
        Added value: +{
+  "description": "Guidance when no datasets matched — echoes applied filters and suggests how to broaden.",
+  "type": "string"
+}
      • addedOutput schema / properties / totalCount
        Added value: +{
+  "description": "Total number of matching datasets before the page limit.",
+  "type": "number"
+}
      • changedOutput schema / required
        Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "totalCount"
+]
  3. 7 tool updates
    • First observednoaa_fetch_data
    • First observednoaa_find_locations
    • First observednoaa_find_stations
    • First observednoaa_get_station
    • First observednoaa_list_data_categories
    • First observednoaa_list_data_types
    • First observednoaa_list_datasets

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources