surfline-mcp
Related Servers
Alternatives to surfline-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMinimal MCP server exposing tools for kitesurfing forecasts (wind and waves via Open-Meteo) and tide predictions (via NOAA CO-OPS).-
- AlicenseNot gradedqualityDmaintenanceMCP server for real-time surf conditions at 5,000+ beaches worldwide. Enables checking surf conditions, finding nearest spots, and listing spots via natural language.22 npm1MIT
- FlicenseNot gradedqualityCmaintenanceProvides surf forecast data including swell height, period, direction, and wind conditions for any location worldwide using the Open-Meteo Marine API. It also includes tools to find the best day to surf and integrates with MCP clients via a Python server.20-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that provides real-time surf intelligence, including wave quality scoring, beach discovery, session planning, and forecast analysis across 12+ global data sources. It turns AI assistants into surf-savvy copilots for finding the perfect wave.1-
- FlicenseBqualityDmaintenanceA minimal MCP server using FastMCP to demonstrate tool creation, including a get_weather example.1-
- AlicenseAqualityBmaintenanceA simple MCP server that exposes a get_weather tool to fetch real-time weather for any GPS coordinates using the Open-Meteo API, no API key required.15 npmISC
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool's purpose is clearly defined and distinct by default.
The single tool name 'get_surf_forecast' follows a clear verb_noun pattern. With only one tool, consistency is inherently perfect as there are no other tools to compare against.
A single tool is too few for a surf forecast server's apparent scope, which typically involves multiple operations like listing spots, getting forecasts for different locations, or accessing different data types. This minimal set limits functionality.
The tool surface is severely incomplete for a surf forecasting domain. It only fetches forecast data for one pre-configured spot, lacking operations to list spots, get forecasts for multiple locations, or access other surf-related data like tides or reports.