tides-mcp

Purpose: Accessing public tide data through a reusable MCP server instead of building a custom data integration.

Inferred · not functionally tested

Audience: developers building MCP clients and AI-powered applications

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: CLI, WEB · deployment: browser, cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

tides-mcp sits in PulseGate's Frameworks & SDKs category. Inferred · not functionally tested: It focuses on accessing public tide data through a reusable MCP server instead of building a custom data integration. Inferred · not functionally tested: It is built as an open-source project for developers building MCP clients and AI-powered applications. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: tides-mcp is available on the web, the command line, and API, and it can be self-hosted.

mrfentmen builds and maintains tides-mcp. Inferred · not functionally tested: Among its 5 catalogued features are MCP server, tide data access, and public data retrieval. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.