How do I find my nearest CO-OPS station?

Visit tidesandcurrents.noaa.gov/map to find your nearest station and its ID number. Major stations include 8518750 (NYC), 9414290 (San Francisco), 8723214 (Virginia Key, Miami).

CO-OPS stands for Center for Operational Oceanographic Products and Services, a branch of NOAA that manages a national network of coastal stations providing marine environmental data.

Can I get long-term sea level trends?

Yes, the API provides sea level rise trends calculated over decades of data, offering precise measurements of relative sea level changes in millimeters per year at specific coastal stations.

NOAA Marine — Tides, Currents & Coastal Data MCP Server for Claude Desktop 6 tools — connect in under 2 minutes

Name: NOAA Marine — Tides, Currents & Coastal Data
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 6 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install NOAA Marine — Tides, Currents & Coastal Data and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "noaa-marine-tides-currents-coastal-data": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

NOAA Marine — Tides, Currents & Coastal Data

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About NOAA Marine — Tides, Currents & Coastal Data MCP Server

Complete US coastal data from NOAA's Center for Operational Oceanographic Products and Services.

Claude Desktop is the definitive way to connect NOAA Marine — Tides, Currents & Coastal Data to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Water Levels — Real-time tides from 200+ stations
Tide Predictions — Hi/lo tide forecasts
Currents — Speed and direction
Water Temperature — Coastal water temps
Met Data — Air temp, wind, pressure at coastal stations
Sea Level Trends — Decades of sea level rise data

The NOAA Marine — Tides, Currents & Coastal Data MCP Server exposes 6 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect NOAA Marine — Tides, Currents & Coastal Data to Claude Desktop via MCP

Follow these steps to integrate the NOAA Marine — Tides, Currents & Coastal Data MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using NOAA Marine — Tides, Currents & Coastal Data

Look for the 🔌 icon in the chat. your 6 tools are now available

Why Use Claude Desktop with the NOAA Marine — Tides, Currents & Coastal Data MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with NOAA Marine — Tides, Currents & Coastal Data through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

NOAA Marine — Tides, Currents & Coastal Data + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the NOAA Marine — Tides, Currents & Coastal Data MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

NOAA Marine — Tides, Currents & Coastal Data MCP Tools for Claude Desktop (6)

These 6 tools become available when you connect NOAA Marine — Tides, Currents & Coastal Data to Claude Desktop via MCP:

get_currents

Available at select CO-OPS stations with current meters. Get observed ocean current speed and direction at a US coastal station

get_meteorological

Complements water-level data for a complete coastal picture. Get coastal meteorological data: air temp, wind, pressure at a station

get_sea_level_trends

Shows long-term relative sea level trends calculated from decades of tide gauge data. Critical for climate research. Get long-term sea level rise trends for a US coastal station

get_tide_predictions

Provides predicted high and low tide times and heights. Useful for fishing, boating, coastal activities. Default is next 48 hours. Get tide predictions (hi/lo) for a US coastal station

get_water_levels

Data in meters relative to station datum. Provide a CO-OPS station ID (e.g., 8518750 for The Battery, NYC; 9414290 for San Francisco). Get observed water levels (tides) at a US coastal station

get_water_temperature

Useful for marine biology, fishing, surfing, and coastal research. Get water temperature at a US coastal station

Example Prompts for NOAA Marine — Tides, Currents & Coastal Data in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with NOAA Marine — Tides, Currents & Coastal Data immediately.

"What are the tide predictions for today at The Battery, NYC?"

"What is the current water temperature in San Francisco Bay?"

"Show me the sea level rise trend for Miami over the last 50 years."

Troubleshooting NOAA Marine — Tides, Currents & Coastal Data MCP Server with Claude Desktop

Common issues when connecting NOAA Marine — Tides, Currents & Coastal Data to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

NOAA Marine — Tides, Currents & Coastal Data + Claude Desktop FAQ

Common questions about integrating NOAA Marine — Tides, Currents & Coastal Data MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.