Marine logo

Marine

Fetches current and forecast coastal wave conditions from Open-Meteo through MCP, with hosted HTTP and local npm connection options.

Install Marine

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "marine": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-marine"
      ],
      "env": {
        "PIPEWORX_API_KEY": "YOUR_VALUE_HERE",
        "PIPEWORX_META_TOOLS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

marine MCP server connects AI clients to the Open-Meteo marine API through the Pipeworx gateway. It provides current wave observations and multi-day forecasts, including wave height, period, and direction for coastal coordinates. Use it for surfing, boating, maritime planning, or monitoring expected swell. Clients can connect over hosted MCP, run the npm stdio bridge, or call the tools directly over HTTP.

Use cases

  • Check current wave conditions before surfing
  • Compare forecast swell for upcoming boating trips
  • Monitor coastal wave height and direction
  • Retrieve forecast data for maritime planning

Key features

  • Current wave height, period, and direction
  • Multi-day coastal wave forecasts
  • Hosted MCP endpoint
  • Local npm stdio bridge
  • Direct HTTP tool calls
  • Optional shared Pipeworx meta-tools

Tools2

What Marine lets your agent do. Expand a tool for its parameters.

Verified live~233 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

10/10 checks healthy over the last 58d

What it can do

From the 2 tools this server returned when we ran it.

Read-only tools · 2
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age194 days
Maintainers1

Observed 2026-10-26 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @pipeworx/mcp-marine (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads437Package downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Tools exposed2Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Marine works

What marine does

marine exposes coastal wave data from marine-api.open-meteo.com through the Model Context Protocol. Its two domain-specific tools cover immediate conditions and upcoming forecasts:

  • get_current_waves returns the present wave height, period, and direction for a coastal location.
  • get_wave_forecast returns daily forecast values over multiple days, including maximum wave height, period, and dominant direction.

The tools are intended for questions such as whether current conditions suit surfing or boating, or how swell may develop over the next several days. Locations can be described in geographic terms such as Hawaii or the California Coast, while the direct HTTP example supplies latitude and longitude.

How it works

The hosted MCP endpoint is available at https://gateway.pipeworx.io/marine/mcp. An MCP client connects to that URL and discovers the marine tools. The endpoint also exposes shared Pipeworx gateway tools, including ask_pipeworx, discover_tools, search_within, and memory-related tools. These shared tools can route questions beyond marine data; they are included even when connecting to the pack-specific endpoint.

A separate full-gateway URL, https://gateway.pipeworx.io/mcp, lists the broader catalog directly. Both endpoints use the same gateway and data sources, while the marine URL lists the marine pack tools directly.

For clients without MCP support, the gateway provides HTTP tool access under /v1/tools/. For example, get_wave_forecast can be called with a JSON body containing latitude, longitude, and a number of days.

Setup and configuration

Add the hosted endpoint to an MCP client with a server entry named marine:

config.json
{
  "mcpServers": {
    "marine": {
      "url": "https://gateway.pipeworx.io/marine/mcp"
    }
  }
}

The local npm option runs @pipeworx/mcp-marine through npx and forwards requests to the same gateway:

config.json
{
  "mcpServers": {
    "marine": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-marine"]
    }
  }
}

The local bridge requires network access. Anonymous use is available with a daily limit of 50 calls. A free Pipeworx account raises the limit to 200 calls; provide the account key as PIPEWORX_API_KEY in the client environment. Set PIPEWORX_META_TOOLS=1 if the local bridge should also list the shared gateway tools.

Tools and capabilities

  • Retrieve current coastal wave height, period, and direction.
  • Request multi-day wave forecasts for coastal locations.
  • Call tools through MCP over hosted HTTP.
  • Run a local stdio bridge with npx.
  • Invoke get_wave_forecast directly through the gateway HTTP API.
  • Ask broader natural-language questions through the shared ask_pipeworx tool.

Limitations and notes

The local npm bridge has no offline mode and must reach the Pipeworx gateway. Anonymous calls are limited to 50 per day, while an account-key connection allows 200 per day. The hosted pack endpoint includes shared Pipeworx meta-tools in addition to the marine tools, so clients may display more tools than the two marine-specific functions. The integration is independent and unofficial rather than published or endorsed by the upstream marine API provider. Pipeworx handles the gateway connection, and its API key is sent as a Bearer token when configured.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Marine

marine is an MCP server that connects AI clients to the Open-Meteo marine API through the Pipeworx gateway. Its main tools, get_current_waves and get_wave_forecast, return current or multi-day coastal wave height, period, and direction for surfing, boating, and maritime planning.

Add the hosted URL `https://gateway.pipeworx.io/marine/mcp` to your MCP client, or run the local bridge with `npx -y @pipeworx/mcp-marine`. The local option needs network access and can use `PIPEWORX_API_KEY` for a higher daily call limit.

Yes, marine works with Cursor through the hosted MCP URL. Add `https://gateway.pipeworx.io/marine/mcp` as an MCP server in Cursor, or configure the local npm stdio bridge instead.

Yes, call the gateway HTTP API directly at `/v1/tools/`. Send a JSON request to the `get_wave_forecast` endpoint with latitude, longitude, and the forecast day count.

No, anonymous calls work without a key and are limited to 50 per day. Add a free Pipeworx account key as `PIPEWORX_API_KEY` to raise the limit to 200 calls per day.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMarine AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/marine?style=directory)](https://allmcps.com/mcp/marine)
HTML Embed
<a href="https://allmcps.com/mcp/marine"><img src="https://allmcps.com/api/badge/marine?style=directory" alt="Marine on AllMCPs" /></a>