PUBLIC OR API KEY
Streamable HTTP
https://perigeetides.com/mcpStart anonymously, or send a Perigee key as an Authorization bearer token when the client supports custom headers.
Model Context Protocol · hosted and open source
Connect an MCP client to NOAA tide predictions, currents, observed water levels, coastal weather, station facts, and local sun and moon context through one Perigee endpoint. The hosted server is ready without a key, and the open-source package can run locally over stdio.
Choose the connection that fits the client
PUBLIC OR API KEY
https://perigeetides.com/mcpStart anonymously, or send a Perigee key as an Authorization bearer token when the client supports custom headers.
OAUTH CONNECTION
https://perigeetides.com/pro/mcpUse this endpoint when the client can open an OAuth sign-in and should apply your Perigee account limits without exposing a key.
Claude · Cursor · VS Code · standard JSON
Pick a client for its exact command, connector URL, one-click deep link, or portable MCP JSON. Installation never asks for a NOAA credential.
claude mcp add --transport http perigee https://perigeetides.com/mcp26 tools plus reference resources
The server also exposes noaa://reference/… resources and prompt templates. For a deterministic HTTP contract, use the REST API reference.
Interpretation contract
Astronomical tide predictions do not include wind, pressure, river flow, waves, or storm surge. Use an observed-water-level tool when the question is about what the gauge measured.
High and low water describe vertical water level. Flood, ebb, maximum current, and slack require a current-station product and can occur at different times.
Keep the returned station ID, vertical datum, units, local time zone, source timestamp, and unavailable fields with every answer.
Registry identity and source trail
io.github.RyanCardin15/noaa-tides-and-currents-mcp@ryancardin/noaa-tides-currents-mcp-serverclaude mcp add noaa -- npx -y @ryancardin/noaa-tides-currents-mcp-serverCanonical registry identity and hosted Streamable HTTP transport.
Published package for local stdio use and self-hosting.
Independent MCP directory record.
Independent MCP directory record and source overview.
Open-source implementation, releases, issues, and package metadata.
Common questions
Yes. The public /mcp endpoint works anonymously within the published request limit. A free Perigee key or OAuth connection raises capacity and ties usage to your account.
Use /mcp for anonymous access or a client that can send an API key. Use /pro/mcp when the client supports OAuth and should open a Perigee sign-in flow.
Yes. The @ryancardin/noaa-tides-currents-mcp-server package exposes a stdio server for local clients and self-hosting.
No. Perigee is an independent interface. NOAA CO-OPS and the National Weather Service remain the upstream authorities for the named data products returned by the tools.