Is an API Key required for NOAA Tides API?

No. The NOAA CO-OPS API is a free and open service provided by the United States government. This server works out of the box without any static credentials required.

Can the agent show air temperature at stations?

Yes. Use the `get_air_temperature` tool providing a station ID. Your agent will return real-time temperature metadata alongside the timestamp.

What data datum is used for predictions?

This server uses the Mean Lower Low Water (MLLW) datum for all water level and tide prediction requests to maintain consistency with nautical charts.

NOAA Tides & Currents API MCP Server for Claude Desktop 5 tools — connect in under 2 minutes

Name: NOAA Tides & Currents API
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 5 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 Tides & Currents API and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

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 Tides & Currents API MCP Server

Empower your AI agent to orchestrate your entire maritime research and tidal auditing workflow with the NOAA Tides & Currents API, the authoritative source for United States coastal data. By connecting NOAA's Center for Operational Oceanographic Products and Services (CO-OPS) to your agent, you transform complex water level searches into a natural conversation. Your agent can instantly retrieve real-time water levels, audit high and low tide predictions, and query atmospheric metadata without you ever touching a technical portal. Whether you are planning maritime logistics or conducting coastal research, your agent acts as a real-time oceanographic consultant, ensuring your data is always verified and precise.

Claude Desktop is the definitive way to connect NOAA Tides & Currents API to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 5 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 Level Auditing — Retrieve real-time water level data for thousands of NOAA stations and maintain a clear view of coastal changes.
Tide Oversight — Audit high and low tide predictions to understand the temporal distribution of maritime scale instantly.
Atmospheric Discovery — Query real-time air and water temperature metadata to assist in regional environmental planning.
Station Intelligence — Retrieve high-resolution details for specific NOAA station IDs to assist in deep-dive oceanographic classification.
Maritime Monitoring — Check API status to ensure your maritime research workflow is always operational.

The NOAA Tides & Currents API MCP Server exposes 5 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 Tides & Currents API to Claude Desktop via MCP

Follow these steps to integrate the NOAA Tides & Currents API 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 Tides & Currents API

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

Why Use Claude Desktop with the NOAA Tides & Currents API MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with NOAA Tides & Currents API 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 Tides & Currents API + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the NOAA Tides & Currents API 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 Tides & Currents API MCP Tools for Claude Desktop (5)

These 5 tools become available when you connect NOAA Tides & Currents API to Claude Desktop via MCP:

check_api_status

Check if the NOAA Tides & Currents service is operational

get_air_temperature

Get real-time air temperature data for a specific NOAA station

get_tide_predictions

Get high and low tide predictions for a specific NOAA station

get_water_levels

Get real-time water levels for a specific NOAA station

get_water_temperature

Get real-time water temperature data for a specific NOAA station

Example Prompts for NOAA Tides & Currents API in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with NOAA Tides & Currents API immediately.

"Get tide predictions for station '9414290' (San Francisco) for '20240510' using NOAA Tides."

"What is the current water temperature at station '8443970' (Boston)?"

"Show real-time water levels for station '9410660' (Los Angeles)."

Troubleshooting NOAA Tides & Currents API MCP Server with Claude Desktop

Common issues when connecting NOAA Tides & Currents API 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 Tides & Currents API + Claude Desktop FAQ

Common questions about integrating NOAA Tides & Currents API 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.