Noaa Tides logo

Noaa Tides

Access NOAA tide, current, water-level, weather, datum, and station data through MCP tools.

Install Noaa Tides

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": {
    "noaa-tides": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-noaa-tides"
      ],
      "env": {
        "PIPEWORX_API_KEY": "YOUR_VALUE_HERE",
        "PIPEWORX_META_TOOLS": "YOUR_VALUE_HERE",
        "NODE_USE_ENV_PROXY": "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— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Noaa Tides connects MCP clients to NOAA Tides & Currents for station metadata, tide predictions, observed water levels, currents, meteorological observations, and vertical datums. It uses the Pipeworx gateway over HTTPS, with a hosted MCP endpoint or an npm-based local stdio bridge. The NOAA API is keyless, while Pipeworx access can be authenticated for higher daily call limits. Use it for coastal, marine, and environmental data workflows that need NOAA station-based queries.

Use cases

  • Find NOAA stations by type or location identifier
  • Retrieve predicted tides for a date range
  • Compare observed water levels with station data
  • Query current and meteorological observations
  • Look up station datums and metadata

Key features

  • NOAA tide predictions
  • Observed water-level and current data
  • Meteorological observations
  • Station metadata and discovery
  • Vertical datum lookup
  • Hosted MCP and local stdio access

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

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-noaa-tides (npm)

Adoption & maintenance

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

npm downloads421Package downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Noaa Tides works

What Noaa Tides does

Noaa Tides exposes NOAA Tides & Currents data through MCP. Its tools cover station discovery and metadata, predicted tides, observed water levels, observed currents, meteorological observations, and vertical datums. The upstream data source is the NOAA API at https://api.tidesandcurrents.noaa.gov/.

Queries use NOAA’s seven-digit station identifiers. Date ranges accept either yyyyMMdd or yyyyMMdd HH:mm formats. Depending on the tool, requests can select datums, intervals, units, time zones, current bins, station types, or meteorological products.

The integration is independent and unofficial; it is not affiliated with or endorsed by NOAA.

How it works

The hosted MCP endpoint is:

https://gateway.pipeworx.io/noaa-tides/mcp

An MCP client can connect to that URL directly. The endpoint lists the Noaa Tides tools and also includes shared Pipeworx gateway tools such as ask_pipeworx, discover_tools, search_within, and remember/recall. These shared tools can route questions across the wider Pipeworx catalog. A full gateway connection at https://gateway.pipeworx.io/mcp exposes the broader catalog directly instead.

HTTP clients can invoke tools without MCP by sending requests to the gateway’s /v1/tools/ endpoints. For example, station searches can be made with POST https://gateway.pipeworx.io/v1/tools/stations and a JSON request body.

Setup and configuration

For a hosted connection, add the MCP URL to the client configuration:

config.json
{
  "mcpServers": {
    "noaa-tides": {
      "url": "https://gateway.pipeworx.io/noaa-tides/mcp"
    }
  }
}

The npm package @pipeworx/mcp-noaa-tides provides a local stdio bridge. It forwards requests to the same hosted endpoint and therefore requires network access:

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

Anonymous use is available with a limit of 50 calls per day. Setting PIPEWORX_API_KEY adds an account key and raises the limit to 200 calls per day. The key is sent as a Bearer token. Set PIPEWORX_META_TOOLS=1 with the local bridge to list the shared gateway tools in addition to the pack-specific tools. When using an HTTPS proxy, newer Node versions can use it when NODE_USE_ENV_PROXY=1 is set.

Tools and capabilities

  • stations lists tide, current, or water-level stations.
  • station_metadata retrieves metadata for one station.
  • predictions returns tide predictions for a date range.
  • water_level retrieves observed water levels.
  • currents retrieves observed currents, with optional bin selection.
  • met_obs retrieves meteorological observations such as wind, air temperature, and water temperature.
  • datums returns the vertical datums for a station.

Limitations and notes

The service depends on network access and has no offline mode. NOAA station IDs must be seven digits, and each request must use the date formats supported by the tools. The hosted endpoint does not require an account for initial calls, but anonymous and authenticated usage have different daily limits.

Reviews

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

Frequently Asked Questions about Noaa Tides

Noaa Tides is an MCP server that connects AI clients to NOAA Tides & Currents through Pipeworx. Its main tools list stations, retrieve station metadata, query tide predictions, fetch observed water levels and currents, obtain meteorological observations, and look up vertical datums using NOAA station IDs.

Add the hosted MCP URL to your client, or run the npm stdio bridge with `npx -y @pipeworx/mcp-noaa-tides`. The hosted endpoint is `https://gateway.pipeworx.io/noaa-tides/mcp`; the local bridge forwards calls there and needs network access.

Yes. Cursor is named as a supported MCP client. Configure it with the hosted `https://gateway.pipeworx.io/noaa-tides/mcp` endpoint, or use the npm stdio configuration.

No. Anonymous calls work without a key and are capped at 50 calls per day. Adding `PIPEWORX_API_KEY` authenticates the connection and raises the daily limit to 200 calls.

Use `yyyyMMdd` or `yyyyMMdd HH:mm` for tool date parameters. Requests also require a seven-digit NOAA station ID, with optional settings such as datum, units, time zone, interval, or current bin depending on the tool.

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 PreviewNoaa Tides AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/noaa-tides?style=directory)](https://allmcps.com/mcp/noaa-tides)
HTML Embed
<a href="https://allmcps.com/mcp/noaa-tides"><img src="https://allmcps.com/api/badge/noaa-tides?style=directory" alt="Noaa Tides on AllMCPs" /></a>