Skip to main content
Glama
surfline-mcp

surfline-mcp

by ivoytov

surfline-mcp

Минималистичный Python MCP-сервер с одним инструментом: get_surf_forecast.

Он получает данные из обоих эндпоинтов прогноза Surfline:

  • conditions

  • rating

Спот фиксируется через переменную окружения (SURFLINE_SPOT_ID), поэтому этот сервер фактически предназначен для одного спота.

Настройка

cd surfline-mcp
uv sync

Related MCP server: Kitesurf Forecast MCP

Запуск (stdio MCP-сервер)

cd surfline-mcp
export SURFLINE_SPOT_ID=5842041f4e65fad6a7708852
uv run surfline-mcp

Запуск через uvx (из GitHub)

export SURFLINE_SPOT_ID=5842041f4e65fad6a7708852
uvx --from git+https://github.com/ivoytov/surfline-mcp surfline-mcp

Конфигурация Nanobot MCP (uvx)

{
  "tools": {
    "mcpServers": {
      "surfline": {
        "command": "uvx",
        "args": ["--from", "git+https://github.com/ivoytov/surfline-mcp", "surfline-mcp"],
        "env": {
          "SURFLINE_SPOT_ID": "5842041f4e65fad6a7708852"
        }
      }
    }
  }
}

Инструмент

get_surf_forecast(days=3)

Возвращает:

  • spot_id

  • days

  • daily_forecast[] с полями:

    • forecastDay

    • dayToWatch

    • headline

    • observation

    • rating_summary.dominant_key

    • rating_summary.min_value

    • rating_summary.max_value

    • rating_summary.avg_value

    • rating_windows[] в виде компактных 3-часовых снимков:

      • local_hour

      • key

      • value

Available Tools

1 tool
get_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

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers