surfline-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SURFLINE_SPOT_ID | Yes | The Surfline spot ID to fetch forecasts for |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_surf_forecastC | Fetch Surfline forecast data for one configured spot. Uses |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.