Pickadive MCP server
{
"mcpServers": {
"pickadive": {
"type": "http",
"url": "https://pickadive.com/mcp"
}
}
}{
"mcpServers": {
"pickadive": {
"type": "http",
"url": "https://pickadive.com/mcp"
}
}
}{
"mcpServers": {
"pickadive": {
"type": "http",
"url": "https://pickadive.com/mcp"
}
}
}{
"servers": {
"pickadive": {
"type": "http",
"url": "https://pickadive.com/mcp"
}
}
}{
"mcpServers": {
"pickadive": {
"type": "http",
"url": "https://pickadive.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.1.0
What it does
PickADive exposes live dive-conditions forecasts, historical climatology, marine-life seasonality data, and site facts for 4,800+ dive sites worldwide. It is for AI agents helping users plan dive trips, find favorable conditions, and understand what to expect at specific destinations or times.
- Find favorable dive forecast windows near a location for a given day, with wave height, wind, and timing details.
- Look up month-by-month climatology for a destination to determine the best time to visit, including water temperature and marine-life seasons.
- Check when and where specific marine species are seasonally present based on historical sighting records.
Tools this server exposes
| Tool | Does |
|---|---|
| find_dive_windows | Returns ranked favorable and moderate forecast windows near a place for a specific day, with wave height, wind speed, timing, and site links. |
| best_time_to_dive | Provides 12-month climatology for a destination, including typical conditions, water temperature, and marine-life season windows. |
| species_seasonality | Returns peak month and regional season windows for a species, along with historical sighting counts from GBIF records. |
| site_facts | Retrieves public facts for a named dive site including depths, difficulty level, access type, hazards, and entry/exit notes. |
| top_dive_regions | Ranks world regions by favorable forecast windows over the next ~72 hours. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.