NOAA Tides & Currents

Live

NOAA water-level observations, tide predictions, currents, and coastal meteorology — every US coast plus the Great Lakes, AK, HI, and Pacific territories.

What is NOAA Tides & Currents?

NOAA Center for Operational Oceanographic Products and Services (CO-OPS) — observed water levels, astronomical tide predictions, currents, and coastal meteorology. Coverage spans every US coast, the Great Lakes, Alaska, Hawaii, Puerto Rico / VI / Bermuda / American Samoa. Discover stations by type (NWLON ~301; tide-prediction 3,449; current-prediction 4,430; historic water-level 2,919; water-temp 240; met 318; harmonic-constituent 1,343), state, bounding box, or radius. Pull observed water levels and astronomical tide predictions (hi/lo extremes or 6-min/hourly series, datums MHHW/MHW/MTL/MSL/MLW/MLLW + NAVD/STND on tidal stations + IGLD on Great Lakes), plus wind, air temperature, water temperature, and barometric pressure. Per-station datum and product availability is fetched on demand.

Available Tools

searchStations
Find stations by catalog (type), state, bbox, near-point, or name substring.
getStation
Single station detail. Pass expand=['datums'|'sensors'|'harcon'|'products'] to learn what the station supports.
getWaterLevels
Observed water levels (real-time + verified historic). Filter by datum/units/timezone. 31-day request cap.
getTidePredictions
Astronomical tide predictions — hi/lo extremes (default) or 6-min/hourly series. 365-day cap on hi/lo and hourly.
getMeteorological
Coastal meteorology: wind, air_temperature, water_temperature, or air_pressure. 31-day request cap.
getServiceInfo
Live station counts by catalog, supported products, datum/unit/time-zone enums, and per-product date caps.

Requirements

Toggle on
Toggle on and use — no setup needed.

Quick Setup Guide

Follow these steps to connect your AI agents to this connector

Open /mcp and turn on NOAA Tides & Currents — no credentials needed.

Call searchStations to find a station near you, then getTidePredictions or getWaterLevels with a stationId. For wind/temperature/pressure use getMeteorological.

Connect to Your AI Assistant

Choose your AI assistant below for specific setup instructions

Follow these steps to connect NOAA Tides & Currents to Claude:

Step 1: Open Claude Settings

Launch Claude → Click the profile button (bottom left) → Navigate to Settings

Step 2: Access Connectors

Scroll down to the Connectors tab → Navigate to the bottom → Click “Add Custom Connector”

Step 3: Name Your Connector

Enter any name you'd like for this connector

Step 4: Get the Connector URL

Step 5: Add the Connector

Paste the URL in the “Remote MCP Server URL” text box → Click Add

Step 6: Start Using

Your connector is now ready to use in Claude

Follow these steps to connect NOAA Tides & Currents to ChatGPT:

Step 1: Enable Developer Mode

Go to Settings → Connectors → Advanced → Enable Developer mode

Step 2: Create New Connector

Go back to Connectors page → Click “Create” (top right)

Step 3: Name Your Connector

Enter any name you'd like for this connector (descriptions are optional)

Step 4: Get the Connector URL

Step 5: Add the URL

Paste the URL in the “MCP Server URL” text box

Step 6: Set Authentication

Click the authentication dropdown → Select “No authentication” (PatchOps handles authentication internally)

Step 7: Create the Connector

Click “I understand and want to continue” checkbox → Press Create

Step 8: Using the Connector

Start a new chat → Click the + button (left of text box) → Open dropdown → Hover over three dots labeled “More” → Select your connector

Instructions for connecting NOAA Tides & Currents to GitHub Copilot:

Coming Soon

Detailed setup instructions for GitHub Copilot will be added here.

For other MCP-compatible platforms:

Step 1: Get the Connector URL

Step 2: Add to Configuration

Add this configuration to your MCP settings file. Replace the URL with your specific connector URL from the /mcp page:

"NOAA Tides & Currents-MCP": {
  "url": "https://patchops.ai/api/mcp/...",
  "type": "http"
}

Example Configuration

Here’s an example using PatchOps MCP:

"PatchOps-MCP": {
  "url": "https://patchops.ai/api/mcp/...",
  "type": "http"
}