Surf MCP Server
Servidor MCP de Surf
Servidor MCP para personas que navegan por Waves y la web.
Diagrama
Related MCP server: BC Water Tides MCP Server
Demostración en vídeo
https://github.com/user-attachments/assets/0a4453e2-66df-4bf5-8366-8538cda366ed
Características
Obtenga información sobre mareas para cualquier ubicación utilizando latitud y longitud
Soporte para consultas de mareas específicas de la fecha
Datos detallados de mareas, incluidas mareas altas y bajas e información de la estación
Manejo automático de zona horaria (UTC)
Prerrequisitos
Python 3.x
Clave API de Storm Glass
Cómo obtener su clave API de Storm Glass
Visita Storm Glass
Haga clic en "Probar gratis" o "Iniciar sesión" para crear una cuenta.
Una vez registrado, recibirás tu clave API
Nota sobre los límites de uso de la API:
Nivel gratuito: 10 solicitudes por día
Planes de pago disponibles:
Pequeño: 500 solicitudes/día (19€/mes)
Mediano: 5000 solicitudes/día (49€/mes)
Grande: 25.000 solicitudes/día (129 €/mes)
Empresa: Planes personalizados disponibles
Elige un plan según tus necesidades de uso. El plan gratuito es ideal para pruebas y uso personal.
Instalación
Clonar el repositorio:
git clone https://github.com/ravinahp/surf-mcp.git
cd surf-mcpInstalar dependencias usando uv:
uv syncNota: Usamos uv en lugar de pip ya que el proyecto usa pyproject.toml para la gestión de dependencias.
Configurar como servidor MCP
Para agregar esta herramienta como servidor MCP, deberá modificar el archivo de configuración de su escritorio Claude. Esta configuración incluye su clave API de Storm Glass, por lo que no necesitará configurarla por separado.
La ubicación del archivo de configuración depende de su sistema operativo:
MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.jsonVentanas:
%APPDATA%/Claude/claude_desktop_config.json
Agregue la siguiente configuración a su archivo JSON:
{
"surf-mcp": {
"command": "uv",
"args": [
"--directory",
"/Users/YOUR_USERNAME/Code/surf-mcp",
"run",
"surf-mcp"
],
"env": {
"STORMGLASS_API_KEY": "your_api_key_here"
}
}
}⚠️ IMPORTANTE:
Reemplace
YOUR_USERNAMEcon su nombre de usuario actual del sistemaReemplace
your_api_key_herecon su clave API de Storm Glass realAsegúrese de que la ruta del directorio coincida con su instalación local
Despliegue
Edificio
Para preparar el paquete:
Sincronizar dependencias y actualizar el archivo de bloqueo:
uv syncPaquete de compilación:
uv buildEsto creará distribuciones en el directorio dist/ .
Depuración
Dado que los servidores MCP se ejecutan en stdio, la depuración puede ser complicada. Para una experiencia óptima, recomendamos usar el Inspector MCP.
Puede iniciar el Inspector MCP con este comando:
npx @modelcontextprotocol/inspector uv --directory /path/to/surf-mcp run surf-mcpAl iniciarse, el Inspector mostrará una URL a la que podrá acceder en su navegador para comenzar a depurar.
El Inspector proporciona:
Monitoreo de solicitudes y respuestas en tiempo real
Validación de entrada/salida
Seguimiento de errores
Métricas de rendimiento
Uso
El servicio proporciona una herramienta FastMCP para obtener información sobre las mareas:
@mcp.tool()
async def get_tides(latitude: float, longitude: float, date: str) -> str:
"""Get tide information for a specific location and date."""Parámetros:
latitude: valor flotante que representa la latitud de la ubicaciónlongitude: valor flotante que representa la longitud de la ubicacióndate: cadena de fecha en formato AAAA-MM-DD
Ejemplo de respuesta:
Tide Times:
Time: 2024-01-20T00:30:00+00:00 (UTC)
Type: HIGH tide
Height: 1.52m
Time: 2024-01-20T06:45:00+00:00 (UTC)
Type: LOW tide
Height: 0.25m
Station Information:
Name: Sample Station
Distance: 20.5km from requested locationCasos de uso
Ejemplo n.° 1: Encontrar el mejor momento para surfear
Puedes usar esta herramienta para determinar el mejor momento para surfear en tu playa favorita y la estación más cercana. Generalmente, las mejores condiciones para surfear se dan durante la marea alta, unas dos horas antes de la pleamar.
Ejemplo de mensaje para Claude:
Nota: Las condiciones óptimas de marea pueden variar según la geografía y el tipo de rompiente de cada playa. Esta herramienta también proporciona información sobre la distancia entre estaciones, que debe considerarse junto con la información sobre mareas. (Por ejemplo, una mayor distancia entre estaciones implica una mayor probabilidad de inexactitud; también puede preguntarle a Claude si se lo solicita).
Manejo de errores
El servicio incluye un manejo robusto de errores para:
Errores en las solicitudes de API
Coordenadas no válidas
Claves API faltantes o no válidas
Tiempos de espera de la red
Available Tools
1 toolget_tidesB
Get tide information for a specific location and date.
Args:
latitude: Float value representing the location's latitude
longitude: Float value representing the location's longitude
date: Date string in YYYY-MM-DD format
Returns:
Formatted string containing tide information and station details
| Name | Required | Description | Default |
|---|---|---|---|
| latitude | Yes | ||
| longitude | Yes | ||
| date | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions what the tool returns ('Formatted string containing tide information and station details'), it lacks critical behavioral context such as rate limits, error conditions, authentication requirements, or whether this is a read-only operation. The description provides basic output format but misses important operational details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is perfectly structured and concise. It begins with a clear purpose statement, then provides organized sections for arguments and returns with specific formatting details. Every sentence adds value, and the information is front-loaded with the most important details first.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-parameter tool with no annotations and no output schema, the description provides adequate but incomplete coverage. It explains parameters well and gives output format, but lacks behavioral context like error handling, rate limits, or authentication requirements. The absence of an output schema means the description should ideally provide more detail about the return structure beyond 'formatted string.'
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description provides excellent parameter semantics despite 0% schema description coverage. It clearly explains each parameter's purpose: 'Float value representing the location's latitude/longitude' and 'Date string in YYYY-MM-DD format.' This fully compensates for the lack of schema descriptions and adds meaningful context beyond what the bare schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Get tide information for a specific location and date.' It uses a specific verb ('Get') and resource ('tide information'), and specifies the scope ('for a specific location and date'). However, with no sibling tools provided, there's no opportunity to differentiate from alternatives, preventing a perfect score of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. It simply states what the tool does without any context about appropriate usage scenarios. With no siblings listed, this omission is less critical but still represents a gap in guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as retrieving tide information for a specific location and date, making it distinct by default.
The single tool follows a clear verb_noun pattern (get_tides), which is consistent and predictable. Since there are no other tools to compare against, the naming convention is perfectly uniform.
A single tool is too few for a server named 'Surf MCP Server', which implies a broader scope related to surfing or ocean conditions. This minimal toolset feels incomplete and under-scoped for the apparent domain.
The tool surface is severely incomplete for a surfing-related server. While get_tides covers tide information, there are obvious gaps such as wave forecasts, weather data, or surf spot details, which are essential for the domain and will likely cause agent failures.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Find NOAA tide stations and NDBC buoys, fetch tide predictions, currents, and live conditions.
NOAA Tides & Currents — observations, predictions, datums, station metadata
NOAA tides and currents: water levels, tide predictions, currents, met data, flooding, sun and moon
Tides MCP — NOAA Tides and Currents data
Related MCP Servers
- AlicenseDqualityDmaintenanceProvides access to the Timezone By Location API to retrieve timezone information based on geographic location data.1MIT
- FlicenseNot gradedqualityCmaintenanceProvides Canadian tide predictions from the IWLS API, enabling retrieval of 7-day tide forecasts and station listings for monitoring stations across Canada.
- FlicenseNot gradedqualityBmaintenanceMCP server that provides tide predictions, station lookup, and tidal event alerts for US coastal locations using live NOAA data.
- AlicenseNot gradedqualityFmaintenanceProvides NOAA tide predictions and observed water levels, allowing AI agents to query tide stations and current water level data.5MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ravinahp/surf-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server