Retrieve water level observations and tide predictions from the NOAA CO-OPS API
domain: tidesandcurrents.noaa.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
No API key is required; call the public Data Retrieval API directly, e.g., GET https://api.tidesandcurrents.noaa.gov/api/prod/datagetter.
Specify a 7-digit CO-OPS station ID via the station parameter; look up unknown station IDs via the companion Metadata API.
Specify the product (e.g., water_level, predictions, currents), a date range (begin_date/end_date or range), and units.
Specify the mandatory datum parameter (e.g., MLLW) for water-level/prediction products.
Choose an output format (json, csv, xml) and parse the returned time series.
Known gotchas
The datum parameter is mandatory for water-level/prediction products - requests will error or behave unexpectedly without it.
High/low-only tide predictions are capped at a 10-year lookahead; six-minute/hourly predictions have different constraints - check limits for your requested interval.
Not every station supports every product (e.g., not all stations have currents or harmonic constituents) - verify station capabilities via the Metadata API first.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?