
NOAA NDBC MCP Server
io.github.mansurjisanPublished by GitHub account mansurjisanv0.1.2Updated Oct 24, 2026
NOAA National Data Buoy Center observations: waves, SST, wind, pressure from 1,300+ stations
Overview
Read-only MCP server that gives an assistant NOAA NDBC buoy observations — waves, sea surface temperature, wind and pressure — from 1,300+ stations.
- What you can do
- Retrieve NDBC buoy observations such as wave height, sea surface temperature, wind and pressure from 1,300+ stations
- Find buoys near a location and pull the latest observations from a specific station
- Return results as markdown, json, geojson or image depending on the tool
- Combine with sibling ocean servers in the same repo for forecasts and comparisons
- When to use it
- Useful when you want an assistant to answer questions about current ocean conditions at US coastal and offshore buoys, or to compare buoy observations with model forecasts from related servers.
- Requirements
- Runs locally over stdio, typically launched with uvx (or pip/pipx) from the PyPI package ndbc-mcp, so a Python environment with uv is needed. No API keys, environment variables or headers are required; the server fetches free public NOAA data over the network.
Installation
In SourceWeft
- Open NOAA NDBC MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
OceanMCP
A monorepo of independently installable MCP servers for ocean and coastal data workflows.
[PyPI] [CI] [MCP Registry] [License: MIT]
Servers
No API keys required for the data servers — all servers above use free, publicly available datasets. The exceptions are hpc-system-mcp and ufs-runner-mcp (below), which require actual NOAA RDHPCS cluster access and, in ufs-runner-mcp's case, submit real Slurm jobs.
Additional servers live in this repo but are not yet published to PyPI (install from source): vdatum-mcp (vertical datum conversion), hpc-system-mcp and ufs-runner-mcp (NOAA RDHPCS / UFS-Coastal HPC workflows — require cluster access), and alert-mcp (CO-OPS threshold alerting).
There is also a 19th server in this repo, nos-workflow-mcp, which is experimental and still a work in progress (its full implementation lives on an unmerged branch — main carries only a minimal subset). It's intentionally left out of the table above and not yet ready for general use.
Quick Start
Install from PyPI
Replace coops-mcp with any published server: erddap-mcp, nhc-mcp, recon-mcp, stofs-mcp, ofs-mcp, rtofs-mcp, ww3-mcp, ndbc-mcp, winds-mcp, usgs-mcp, goes-mcp, adcirc-mcp, schism-mcp.
Install from source
Configure your MCP client
Add to your MCP settings (e.g., project .mcp.json):
Using PyPI packages (recommended):
Using local source checkout
Example Queries
With servers configured, you can ask your AI assistant naturally:
CO-OPS queries:
- "Get current water levels at The Battery, NY"
- "Find tide stations near Miami Beach"
- "What are the flood statistics for Charleston, SC?"
- "Show me the sea level trend at San Francisco"
ERDDAP queries:
- "Search for sea surface temperature datasets on CoastWatch"
- "Get chlorophyll data off the California coast for January 2024"
- "What ERDDAP servers cover the US East Coast?"
- "List all glider datasets on IOOS Gliders ERDDAP"
NHC queries:
- "Are there any active tropical cyclones right now?"
- "Show me Hurricane Katrina's track"
- "Search for Category 5 hurricanes in the Atlantic"
- "What is the forecast track for the active storm?"
Recon queries:
- "List HDOB reconnaissance flights for the 2024 Atlantic season"
- "Get HDOB flight-level observations from October 7, 2024"
- "Show me the Vortex Data Messages for Hurricane Milton"
- "Get ATCF aircraft fix data for storm AL14 2024"
STOFS queries:
- "Get the STOFS water level forecast for The Battery, NY"
- "Compare STOFS forecast vs observations at Boston for the past 24 hours"
- "What are the top stations with highest predicted water levels?"
- "Find STOFS stations within 50 km of New Orleans"
OFS queries:
- "What OFS models cover the Chesapeake Bay?"
- "Get the water level forecast at lat 38.98, lon -76.48 from CBOFS"
- "Compare CBOFS water level with CO-OPS observations at station 8571892"
- "List available NGOFS2 forecast cycles for today"
RTOFS queries:
- "Get the RTOFS sea surface temperature forecast at 40°N, 74°W"
- "Show me a temperature depth profile in the Gulf Stream"
- "What RTOFS datasets are currently available on HYCOM THREDDS?"
- "Get a vertical transect of salinity from Miami to Bermuda"
- "Show the SST area forecast for the Gulf of Mexico"
WW3 queries:
- "What GFS-Wave model grids are available?"
- "Find NDBC buoys near Cape Hatteras"
- "Get the latest wave observations from buoy 41025"
- "Show me the GFS-Wave forecast at 35°N, 75°W for the next 48 hours"
- "Compare the wave forecast against buoy 41025 observations"
Cross-server queries:
- "Find CO-OPS stations near this ERDDAP buoy location"
- "Compare tide station data with nearby ERDDAP satellite SST"
- "Is there an active hurricane threatening the Gulf Coast? If so, show me the STOFS surge forecast for New Orleans"
- "Get the CBOFS water level forecast at Chesapeake Bay and compare it with the CO-OPS tide prediction for the same station"
- "Show me sea surface temperature from ERDDAP near The Battery and the current water level from CO-OPS"
- "Which NHC storms have hit the Gulf Coast historically? Show the CO-OPS flood statistics for impacted stations"
- "Get the STOFS gridded forecast and the OFS water level forecast at the same location and compare them"
Architecture
Each server is fully self-contained with its own pyproject.toml, dependencies, and tests. See docs/architecture.md for details on shared conventions.
Shared patterns across servers:
- FastMCP for MCP server framework
- httpx for async HTTP clients
- Pydantic models, with
Literal[...]types for constrained parameters - Read-only tools by default — the data-fetching servers only fetch, never
modify, anything.
ufs-runner-mcp(submits/cancels Slurm jobs) andalert-mcp(creates/pauses/deletes in-memory alert state) are the two exceptions, each with a small number of tools markedreadOnlyHint=False response_formatoutput as markdown (default), json, geojson, or image, depending on the tool- Actionable error messages with suggestions
See CONVENTIONS.md for the full response/behavior contract (output caps, retrieved_at, error format, HTTP retries, dependency bounds).
Citation
If you use this project in your research or work, please cite:
License
Licensed under the MIT License. You may use, modify, and distribute this software under the MIT terms. See LICENSE for details.
Source: README.md at commit f8d88a2
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts