Provides access to NOAA CO-OPS tides, water levels, currents, and meteorological data for ocean and coastal workflows.
Also known as oceanmodeling/ocean-mcp, coops-mcp
- Stars
- 10
- Tools
- 12
- Downloads, 30 days
- 135
- Latest version
- 0.1.1
- Last commit
- Nov 16, 2026
- License
- MIT
What is NOAA CO-OPS MCP?
NOAA CO-OPS provides access to NOAA CO-OPS tides, water levels, currents, and meteorological data for ocean and coastal workflows. It exposes 12 tools, such as coops_get_currents, coops_get_extreme_water_levels, coops_get_flood_stats.
Summary generated from the project's README
About NOAA CO-OPS MCP server
Accessing NOAA CO-OPS tides, water levels, currents, and meteorological data is what this server enables for ocean and coastal researchers. It provides a direct way to retrieve environmental information from official sources to support marine workflows. Users can interact with the server through an AI client by asking natural language questions about specific locations or historical trends.
This server is installed locally using tools like uvx, pip, or pipx. It functions as a read-only data provider, meaning it fetches information without modifying any external datasets. No API keys or accounts are required because the server utilizes free, publicly available datasets. It is part of a larger monorepo of ocean-focused tools, allowing for specialized data retrieval through a standardized interface.
What you can do with it
- 1Retrieve local water levelsAsk the assistant to get the current water level at a specific coastal location like The Battery, NY.
- 2Locate nearby tide stationsFind the locations of tide stations in a specific area such as Miami Beach.
- 3Analyze flood statisticsRequest historical flood statistics for a specific city like Charleston, SC.
- 4Monitor sea level trendsCheck the long-term sea level trends for a coastal city like San Francisco.
Written from the project's README. Every use case is checked against a quote from it.
How to install NOAA CO-OPS MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall NOAA CO-OPS MCP in Claude Code
$ claude mcp add coops-mcp -- uvx coops-mcpInstall NOAA CO-OPS MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"coops-mcp": {
"command": "uvx",
"args": [
"coops-mcp"
]
}
}
}Install NOAA CO-OPS MCP in VS Code
.vscode/mcp.json
{
"servers": {
"coops-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"coops-mcp"
]
}
}
}Install NOAA CO-OPS MCP in VS Code CLI
$ code --add-mcp '{"name":"coops-mcp","type":"stdio","command":"uvx","args":["coops-mcp"]}'Install NOAA CO-OPS MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"coops-mcp": {
"command": "uvx",
"args": [
"coops-mcp"
]
}
}
}Install NOAA CO-OPS MCP in Codex
$ codex mcp add coops-mcp -- uvx coops-mcpInstall NOAA CO-OPS MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.coops-mcp] command = "uvx" args = ["coops-mcp"]
Install NOAA CO-OPS MCP in Gemini CLI
$ gemini mcp add -s user coops-mcp uvx -- coops-mcpInstall NOAA CO-OPS MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"coops-mcp": {
"command": "uvx",
"args": [
"coops-mcp"
]
}
}
}NOAA CO-OPS MCP tools 12
Read from the server with tools/listcoops_get_currentsRead-onlyRetrieve current (water flow) observations or predictions from a CO-OPS currents station. Note: Currents stations use alphanumeric IDs (e.g., 'cb1401'), not the 7-digit numeric IDs used for water level stations. Args: station_id: CO-OPS currents station ID (e.g., 'cb1401'). product: Data type — 'currents' for observations, 'currents_predictions' for predictions. begin_date: Start date (YYYY-MM-DD or YYYYMMDD). end_date: End date (YYYY-MM-DD or YYYYMMDD). date: Date shorthand — 'today', 'latest', or 'recent' (alternative to begin/end). units: Unit system — 'metric' or 'english' (default: metric). time_zone: Time zone — 'gmt', 'lst', or 'lst_ldt' (default: gmt). bin_num: Depth bin number for multi-bin stations (optional). response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on records returned (default 2000). Only the most recent max_records are kept, and the output flags any truncation.
coops_get_extreme_water_levelsRead-onlyGet extreme (record) water levels ever recorded at a CO-OPS station. Returns the highest and lowest water levels on record with dates and values. Args: station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY). datum: Vertical datum reference (default: MHHW). units: Unit system — 'metric' or 'english' (default: metric).
coops_get_flood_statsRead-onlyGet annual flood day counts and high tide flooding outlook for a CO-OPS station. Combines data from the annual flood count and high tide flooding outlook endpoints. Args: station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY). year: Optional specific year to query. datum: Vertical datum reference (default: MHHW). units: Unit system — 'metric' or 'english' (default: metric).
coops_get_sea_level_trendsRead-onlyGet sea level trend data for a CO-OPS station. Returns the long-term linear sea level trend with confidence intervals. Args: station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY).
coops_get_peak_storm_eventsRead-onlyGet peak water level events (storm surges) recorded at a CO-OPS station. Args: station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY). datum: Vertical datum reference (default: MHHW). units: Unit system — 'metric' or 'english' (default: metric). year: Optional specific year to query.
coops_get_datumsRead-onlyGet tidal datum values for a CO-OPS station. Returns datum elevations (MLLW, MHHW, MSL, MHW, MLW, etc.) relative to station datum. Args: station_id: CO-OPS station ID (e.g., '9414290' for San Francisco, CA). units: Unit system — 'metric' or 'english' (default: metric).
coops_get_meteorologicalRead-onlyRetrieve meteorological observations from a CO-OPS station. Args: station_id: CO-OPS station ID (e.g., '8724580' for Key West, FL). product: Met data type — 'wind', 'air_temperature', 'water_temperature', 'air_pressure', 'humidity', 'conductivity', 'salinity', 'visibility', or 'air_gap'. begin_date: Start date (YYYY-MM-DD or YYYYMMDD). end_date: End date (YYYY-MM-DD or YYYYMMDD). date: Date shorthand — 'today', 'latest', or 'recent' (alternative to begin/end). units: Unit system — 'metric' or 'english' (default: metric). interval: Data interval — '6' (6-min) or 'h' (hourly). time_zone: Time zone — 'gmt', 'lst', or 'lst_ldt' (default: gmt). response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on records returned (default 2000). Only the most recent max_records are kept, and the output flags any truncation.
coops_list_stationsRead-onlyList CO-OPS stations, optionally filtered by type and/or state. Args: station_type: Filter by station type (e.g., 'waterlevels', 'currentpredictions', 'waterlevelsandmet'). state: Filter by US state (2-letter code, e.g., 'NY', 'FL'). limit: Maximum number of stations to return (default 50). offset: Number of stations to skip for pagination (default 0).
coops_get_stationRead-onlyGet detailed information for a specific CO-OPS station. Args: station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY). expand: Optional list of resources to include: 'details', 'sensors', 'datums', 'floodlevels', 'harcon', 'benchmarks'. units: Unit system — 'metric' or 'english' (default: metric).
coops_find_nearest_stationsRead-onlyFind CO-OPS stations nearest to a geographic coordinate. Args: latitude: Latitude in decimal degrees (e.g., 40.7). longitude: Longitude in decimal degrees (e.g., -74.0). radius_km: Search radius in kilometers (default 50). station_type: Optional filter by station type (e.g., 'waterlevels'). limit: Maximum number of stations to return (default 5). response_format: Output format — 'markdown' (default) or 'geojson' (a FeatureCollection of Point features, coordinates [lon, lat]).
coops_get_water_levelsRead-onlyRetrieve observed water level data from a CO-OPS station. Use begin_date/end_date for a date range, or date='today'/'latest'/'recent' for shortcuts. Max range is 365 days per request. Args: station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY). begin_date: Start date (YYYY-MM-DD or YYYYMMDD format). end_date: End date (YYYY-MM-DD or YYYYMMDD format). date: Date shorthand — 'today', 'latest', or 'recent' (alternative to begin/end). datum: Vertical datum reference (default: MLLW). Options: MLLW, MHHW, MSL, NAVD, STND, MHW, MLW, MTL. units: Unit system — 'metric' or 'english' (default: metric). interval: Data interval — '6' (6-min), 'h' (hourly), 'hilo' (high/low only). Default is 6-min. time_zone: Time zone — 'gmt', 'lst', or 'lst_ldt' (default: gmt). response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on records returned (default 2000). A long 6-min range is tens of thousands of points; only the most recent max_records are kept, and the output flags any truncation.
coops_get_tide_predictionsRead-onlyRetrieve tide predictions for a CO-OPS station. Predictions are based on harmonic constituents — available for most water level stations. Max range: 365 days (or 3650 days for high/low interval). Args: station_id: CO-OPS station ID (e.g., '8518750' for The Battery, NY). begin_date: Start date (YYYY-MM-DD or YYYYMMDD format). end_date: End date (YYYY-MM-DD or YYYYMMDD format). datum: Vertical datum reference (default: MLLW). units: Unit system — 'metric' or 'english' (default: metric). interval: Prediction interval — '6' (6-min), 'h' (hourly), 'hilo' (high/low only). Default is 6-min. time_zone: Time zone — 'gmt', 'lst', or 'lst_ldt' (default: gmt). response_format: Output format — 'markdown' (default) or 'json'. max_records: Cap on predictions returned (default 2000). A long 6-min range is tens of thousands of points; only the most recent max_records are kept, and the output flags any truncation.
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableoceanmodeling/ocean-mcp is public and reachablegithub.com/oceanmodeling/ocean-mcp ↗Pass
- Package names this repository as its sourcecoops-mcp names oceanmodeling/ocean-mcp as sourcepypi.org/project/coops-mcp/ ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for coops-mcppypi.org/project/coops-mcp/ ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-16github.com/oceanmodeling/ocean-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from coops-mcpPass
- No critical advisory in the package or its dependencies37 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model12 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubOceanMCP
A monorepo of independently installable MCP servers for ocean and coastal data workflows.
Servers
| Server | PyPI | Description |
|---|---|---|
| coops-mcp | NOAA CO-OPS tides, water levels, currents, meteorological data | |
| erddap-mcp | Universal ERDDAP data access across 80+ public servers | |
| nhc-mcp | NHC storm tracks, advisories, HURDAT2 best track data | |
| recon-mcp | Hurricane reconnaissance data (HDOB, Vortex Data Messages, ATCF fixes) | |
| stofs-mcp | NOAA STOFS storm surge forecasts and observation validation | |
| ofs-mcp | NOAA OFS regional ocean model forecasts (water level, temperature, salinity) | |
| rtofs-mcp | NOAA RTOFS global ocean forecasts (SST, salinity, currents, SSH) via HYCOM THREDDS | |
| ww3-mcp | GFS-Wave (WAVEWATCH III) forecasts and NDBC buoy wave observations | |
| ndbc-mcp | NOAA NDBC buoy observations — waves, SST, wind, pressure (1,300+ stations) | |
| winds-mcp | NWS surface wind observations from ASOS / AWOS stations | |
| usgs-mcp | USGS Water Services — streamflow, NWS/NWPS flood status, peak events | |
| goes-mcp | NOAA GOES-18/19 satellite imagery — visible, infrared, water vapor | |
| adcirc-mcp | ADCIRC model setup debugging, parameter lookup, config validation | |
| schism-mcp | SCHISM model setup debugging, parameter lookup, config validation |
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
# uvx (recommended) — runs without permanent install, like npx for Python
uvx coops-mcp
# pip — install into current environment
pip install coops-mcp
# pipx — install in isolated environment with CLI entry point
pipx install coops-mcp
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
git clone https://github.com/oceanmodeling/ocean-mcp.git
cd ocean-mcp/servers/coops-mcp # or any other server directory under servers/
uv sync
Configure your MCP client
Add to your MCP settings (e.g., project .mcp.json):
Using PyPI packages (recommended):
{
"mcpServers": {
"coops": {
"command": "uvx",
"args": ["coops-mcp"]
},
"erddap": {
"command": "uvx",
"args": ["erddap-mcp"]
},
"nhc": {
"command": "uvx",
"args": ["nhc-mcp"]
},
"recon": {
"command": "uvx",
"args": ["recon-mcp"]
},
"stofs": {
"command": "uvx",
"args": ["stofs-mcp"]
},
"ofs": {
"command": "uvx",
"args": ["ofs-mcp"]
},
"rtofs": {
"command": "uvx",
"args": ["rtofs-mcp"]
},
"ww3": {
"command": "uvx",
"args": ["ww3-mcp"]
}
}
}
{
"mcpServers": {
"coops": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ocean-mcp/servers/coops-mcp", "python", "-m", "coops_mcp"]
},
"erddap": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ocean-mcp/servers/erddap-mcp", "python", "-m", "erddap_mcp"]
},
"nhc": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ocean-mcp/servers/nhc-mcp", "python", "-m", "nhc_mcp"]
},
"recon": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ocean-mcp/servers/recon-mcp", "python", "-m", "recon_mcp"]
},
"stofs": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ocean-mcp/servers/stofs-mcp", "python", "-m", "stofs_mcp"]
},
"ofs": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ocean-mcp/servers/ofs-mcp", "python", "-m", "ofs_mcp"]
},
"rtofs": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ocean-mcp/servers/rtofs-mcp", "python", "-m", "rtofs_mcp"]
},
"ww3": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ocean-mcp/servers/ww3-mcp", "python", "-m", "ww3_mcp"]
}
}
}
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:
@software{jisan2025oceanmcp,
author = {Jisan, Mansur Ali},
title = {Ocean MCP: Real-Time Marine Data, MCP-Native},
year = {2025},
url = {https://github.com/oceanmodeling/ocean-mcp},
note = {MCP servers for NOAA CO-OPS, ERDDAP, NHC, Recon, STOFS, OFS, RTOFS, WW3, NDBC, USGS, winds, GOES, ADCIRC, and SCHISM data}
}
License
Licensed under the MIT License. You may use, modify, and distribute this software under the MIT terms. See LICENSE for details.
NOAA CO-OPS MCP questions
How do I add NOAA CO-OPS MCP to Claude Code?
Run claude mcp add coops-mcp -- uvx coops-mcp in your terminal. Add --scope user to make it available in every project.
How do I add NOAA CO-OPS MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does NOAA CO-OPS MCP provide?
It exposes 12 tools, including coops_get_currents, coops_get_extreme_water_levels, coops_get_flood_stats, coops_get_sea_level_trends, coops_get_peak_storm_events.
Do I need an API key to use the data servers?
No, all data servers use free, publicly available datasets and do not require API keys.