surfline-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@surfline-mcp get surf forecast for the next 2 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
surfline-mcp
Minimal Python MCP server with one tool: get_surf_forecast.
It fetches both Surfline forecast endpoints:
conditionsrating
The spot is fixed by environment variable (SURFLINE_SPOT_ID) so this server is effectively single-spot.
Setup
cd surfline-mcp
uv syncRelated MCP server: Kitesurf Forecast MCP
Run (stdio MCP server)
cd surfline-mcp
export SURFLINE_SPOT_ID=5842041f4e65fad6a7708852
uv run surfline-mcpRun via uvx (from GitHub)
export SURFLINE_SPOT_ID=5842041f4e65fad6a7708852
uvx --from git+https://github.com/ivoytov/surfline-mcp surfline-mcpNanobot MCP config (uvx)
{
"tools": {
"mcpServers": {
"surfline": {
"command": "uvx",
"args": ["--from", "git+https://github.com/ivoytov/surfline-mcp", "surfline-mcp"],
"env": {
"SURFLINE_SPOT_ID": "5842041f4e65fad6a7708852"
}
}
}
}
}Tool
get_surf_forecast(days=3)
Returns:
spot_iddaysdaily_forecast[]with:forecastDaydayToWatchheadlineobservationrating_summary.dominant_keyrating_summary.min_valuerating_summary.max_valuerating_summary.avg_valuerating_windows[]as compact 3-hour snapshots:local_hourkeyvalue
Available Tools
1 toolget_surf_forecastC
Fetch Surfline forecast data for one configured spot.
Uses SURFLINE_SPOT_ID from environment and returns both
conditions and rating endpoint payloads.
Inputs: days. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Hosted MCP server for Xweather weather data: conditions, forecasts, alerts, and more.
MCP server for querying Forkast documentation
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides 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.21-
- FlicenseNot gradedqualityDmaintenanceMinimal MCP server exposing tools for kitesurfing forecasts (wind and waves via Open-Meteo) and tide predictions (via NOAA CO-OPS).-
- FlicenseBqualityDmaintenanceA minimal MCP server using FastMCP to demonstrate tool creation, including a get_weather example.1-
- 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.55 npm1MIT