
Connects Claude to NOAA's Tides & Currents API for real-time coastal water data. You get seven tools: list stations, pull metadata, fetch tide predictions, query observed water levels and currents, grab meteorological observations, and retrieve vertical datums. Useful when you're building anything that needs accurate tidal or coastal condition data, whether that's marine navigation planning, fishing apps, coastal flood analysis, or environmental monitoring. Part of the Pipeworx gateway, so you can either use this standalone or tap into their full catalog of 673+ data sources. Runs over streamable HTTP and includes a plain-English query interface if you'd rather ask questions than call tools directly.
NOAA Tides & Currents MCP — observations, predictions, datums, stations. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
stations(type?, format?) — list of tide/current/water-level stationsstation_metadata(station) — single-station metadatapredictions(station, begin_date, end_date, datum?, interval?, units?, time_zone?) — tide predictionswater_level(station, begin_date, end_date, datum?, units?, time_zone?) — observed water levelcurrents(station, begin_date, end_date, units?, time_zone?, bin?) — observed currentsmet_obs(station, product, begin_date, end_date, units?, time_zone?) — meteorological obs (wind, air_temp, water_temp, …)datums(station) — vertical datumsstation accepts a 7-digit NOAA station id. Dates: yyyyMMdd or yyyyMMdd HH:mm.
https://api.tidesandcurrents.noaa.gov/
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"noaa-tides": {
"url": "https://gateway.pipeworx.io/noaa-tides/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/noaa-tides/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Noaa Tides data" })
The gateway picks the right tool and fills the arguments automatically.
MIT