Skip to content
← Directory

mcp · United States

ocean-mcp

MCP servers for coastal oceanography

Claim this listing

Represent ocean-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered docs-verified
NOAA CO-OPS tides, water levels, currents, meteorological data · ERDDAP dataset access across 80+ public servers · NHC storm tracks, advisories, HURDAT2 best track data · Hurricane reconnaissance HDOB, Vortex Data Messages, ATCF fixes · STOFS storm surge forecasts and observation validation · OFS regional ocean model forecasts (water level, temperature, salinity) · RTOFS global ocean forecasts (SST, salinity, currents, SSH) · WW3 GFS-Wave forecasts and NDBC buoy wave observations · NDBC buoy observations (waves, SST, wind, pressure) · NWS ASOS/AWOS surface wind observations · USGS streamflow, NWS/NWPS flood status, peak events · GOES-18/19 satellite imagery (visible, infrared, water vapor) · ADCIRC and SCHISM model setup debugging and config validation (tooling, not data)
Coverage llm-inferred
United States coastal and ocean waters (NOAA sources); RTOFS is global
Formats docs-verified
markdown · JSON · GeoJSON · image
Access docs-verified
Free and open; no API key for the data servers; MIT licence. hpc-system-mcp and ufs-runner-mcp need NOAA RDHPCS cluster access

Useful for

Use cases llm-inferred
US coastal flood-risk screening: CO-OPS water levels and flood statistics at a nearby tide station · Storm surge forecast comparison against tide-gauge observations for coastal flood assessment · Stream flow and NWS flood status checks near a US site via USGS Water Services · Wave and wind climate context from NDBC buoy observations for marine or coastal design
Audience llm-inferred
coastal engineers · hydrologists · oceanographers · GIS analysts · environmental consultants working on US projects

Limitations

Constraints llm-inferred
Coverage is US/NOAA-focused; no UK or European data sources are described · Several servers are not on PyPI and must be installed from source (vdatum-mcp, hpc-system-mcp, ufs-runner-mcp, alert-mcp) · hpc-system-mcp and ufs-runner-mcp require NOAA RDHPCS cluster access; ufs-runner-mcp submits real Slurm jobs · nos-workflow-mcp is experimental and not ready for general use · Data servers depend on upstream public NOAA, USGS and ERDDAP endpoints, so availability is outside the project's control · Monorepo has 13 published servers in the table, so each must be installed and configured separately
Licence
MIT
Authentication
No API key required (repository README, auto-extracted; check upstream requirements)
GitHub stars
10
Last commit
14/10/2026
Last successful page check
14/10/2026
Page health
healthy
Package
pypi:coops-mcp
Verification
Not independently verified

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Provenance & evidence

Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).

Metadata observed 15/10/2026 · research sweep: github-search