NOAA tides and currents: water levels, tide predictions, currents, met data, flooding, sun and moon
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like NOAA Tides and Currents.
https://perigeetides.com/mcpnpx -y @ryancardin/noaa-tides-currents-mcp-serverAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-ryancardin15-noaa-tides-and-currents-mcp": {
"command": "npx",
"args": [
"-y",
"@ryancardin/noaa-tides-currents-mcp-server"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
NOAA Tides and Currents is an MCP server for NOAA tides and currents: water levels, tide predictions, currents, met data, flooding, sun and moon. It supports STDIO, HTTP transport.
Use the generated config in Install. This server runs with npx -y @ryancardin/noaa-tides-currents-mcp-server; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://perigeetides.com/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://perigeetides.com/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://perigeetides.com/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://perigeetides.com/mcp.
NOAA Tides and Currents uses STDIO, HTTP transport. Endpoint: https://perigeetides.com/mcp.
NOAA Tides and Currents inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
NOAA Tides and Currents does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
@ryancardin/noaa-tides-currents-mcp-serverstdio | npm | 2.0.1 | None advertised |