
A straightforward wrapper around Open-Meteo's free marine API. No authentication required, which keeps setup simple. Part of the broader Pipeworx gateway that bundles 673+ data sources behind a single MCP endpoint. The documentation doesn't list specific tools, but Open-Meteo typically provides marine forecasts, wave heights, ocean currents, and sea temperatures. You can either connect to this standalone marine endpoint or use the full Pipeworx gateway and ask questions in plain English. The gateway routes your request to the right underlying API. Useful when you need ocean or coastal weather data in your AI workflows without managing API keys.
Marine MCP — wraps marine-api.open-meteo.com (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_wave_forecast | Get multi-day wave forecasts for coastal locations (e.g., "Hawaii", "California Coast"). Returns max wave height, period, and dominant direction per day. Use when planning water activities or monitoring upcoming swell. |
get_current_waves | Check real-time wave conditions at a coastal location. Returns current wave height, period, and direction. Use for immediate surfing, boating, or maritime planning decisions. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"marine": {
"url": "https://gateway.pipeworx.io/marine/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/marine/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 Marine data" })
The gateway picks the right tool and fills the arguments automatically.
MIT