Noaa Marine Mcp Server
Wire tide predictions, currents, and buoy conditions from NOAA into coastal, boating, or marine logistics apps without hand-rolling CO-OPS and NDBC APIs.
Overview
NOAA Marine MCP Server is a MCP server for the Build phase that finds NOAA tide stations and buoys and returns tide predictions, currents, and live marine conditions to your agent.
What is this MCP server?
- Discover NOAA CO-OPS tide stations and NDBC buoys near a place or coordinates
- Fetch tide predictions, tidal currents, and live marine observations from official feeds
- stdio and streamable-http transports plus hosted remote at noaa-marine.caseyjhand.com
- Optional NOAA_APPLICATION_ID courtesy string for CO-OPS requests (defaults to noaa-marine-mcp-server)
- npm package @cyanheads/noaa-marine-mcp-server v0.1.3 with Bun runtime hint
- Server version 0.1.3
- Supports stdio and streamable-http transports
What problem does it solve?
Coastal and marine products need correct station IDs and CO-OPS/NDBC endpoints, which is tedious to script inside every agent session.
Who is it for?
Indie builders adding tide charts, current windows, or buoy alerts to a niche marine or coastal SaaS or mobile companion app.
Skip if: Teams that only need generic land weather forecasts without tides, currents, or offshore buoy telemetry.
What do I get? / Deliverables
Your agent can resolve marine stations and return tide and buoy datasets in one MCP workflow while you build harbor, boating, or logistics features.
- Resolved tide station and buoy identifiers for a region or coordinate
- Tide prediction and current series pulled from NOAA products
- Live marine observation snapshots from selected NDBC buoys
Recommended MCP Servers
Journey fit
Marine NOAA data is fetched when you are implementing location-aware features and external data sources, which is the Build phase. Station lookup, tide tables, and live buoy reads are classic third-party API integrations exposed to your coding agent via MCP.
How it compares
MCP integration focused on NOAA marine CO-OPS and NDBC data, not a full multi-source weather agent skill.
Common Questions / FAQ
Who is NOAA Marine MCP Server for?
Solo and small-team developers building coastal, boating, or logistics software who want NOAA tide and buoy data inside Claude Code, Cursor, or Codex via MCP.
When should I use NOAA Marine MCP Server?
Use it during Build when you are wiring tide predictions, tidal currents, or live buoy readings into your product and want the agent to query NOAA without custom API glue.
How do I add NOAA Marine MCP Server to my agent?
Install @cyanheads/noaa-marine-mcp-server from npm, run the stdio start script with Bun, or register the streamable-http remote URL in your MCP client; set NOAA_APPLICATION_ID if you want a custom CO-OPS application label.