PickADive MCP Server

MCP serverDev tools

Plan scuba dives by asking your AI. Once added, it checks live forecast windows, historical best-time data, and species seasons across more than 4,800 dive sites, so you can ask when and where to dive and get an answer based on actual conditions.

Available today. Use it from your connected AI after setup.

Add it, then ask your AI when the best dive windows are for your dates or which species are in season where you want to go.

Then ask your AI: use PickADive MCP Server to find dive windows

What your AI can do with it

  • Find good dive windows from live forecasts for your dates
  • Identify the best time of year to dive a site using historical climate data
  • Check which marine species are in season at a given site
  • Search across 4,800+ dive sites
  • Plan a dive trip around both conditions and wildlife sightings

From the project's README

As published by afiliptsov/pickadive-mcp in README.md.

Live dive-conditions data for AI agents — forecast windows, best-time climatology, marine-life seasonality, and site facts for 4,800+ dive sites worldwide.

Hosted at https://pickadive.com/mcp — nothing to install

Setup · Tools · What you can do · Data & honesty · Security · Support


What can you do with it?

  • "Where can I dive near Boston this Saturday?" — ranked favorable and moderate forecast windows near any place for any day, with wave height, wind, timing, and site links.
  • "When should I book Komodo?" — month-by-month climatology for a destination: the share of days historically favorable, typical water temperature and seas, and marine-life season windows.
  • "When and where do whale sharks peak?" — species seasonality from 236k+ recorded GBIF sightings: peak month and regional season windows.
  • "How deep is Molasses Reef, and what are the hazards?" — public facts for any named dive site: depths, difficulty, shore/boat access, hazards, entry and exit notes.
  • "Where in the world is good for diving right now?" — regions ranked by favorable windows over the next ~72 hours.

Setup

Add the server to any MCP-compatible client — no key, no OAuth:

{
  "mcpServers": {
    "pickadive": { "url": "https://pickadive.com/mcp" }
  }
}
ClientHow
Claude Codeclaude mcp add --transport http pickadive https://pickadive.com/mcp
Claude.ai / DesktopSettings → Connectors → Add custom connector → https://pickadive.com/mcp
Cursor · Windsurf · VS Code · ZedAdd the JSON block above to your MCP config
Gemini CLIgemini mcp add --transport http pickadive https://pickadive.com/mcp
Local-only clientsBridge with npx mcp-remote https://pickadive.com/mcp

Discovery manifest: /.well-known/mcp.json · Agent onboarding: /llms.txt

Tools

ToolInputOutput
find_dive_windows{near | lat+lng, day?, radius_km?}Ranked windows: quality, wave_m, wind_kn, timing, site links
best_time_to_dive{destination}12-month climatology + marine-life seasons + source page
species_seasonality{species, lat?, lng?}Peak month, regional season windows, sighting counts
site_facts{site}Depths, difficulty, access, hazards, entry/exit, cert level
top_dive_regions{}World regions ranked by favorable windows (~72 h)

All values are metric with unit-suffixed field names (max_depth_m, wave_m, distance_km); wind is knots — the marine convention everywhere. Tool descriptions instruct agents to convert for US users. Every response includes a source link — please cite pickadive.com when presenting results.

Data & honesty

Answers come from PickADive's own pipeline: hourly conditions gradings across 4,800+ curated dive sites (Open-Meteo marine + weather, NOAA tides), multi-year climatology, and 236k+ GBIF species sighting records.

Two rules the server never breaks:

  1. Forecasts are planning context, never a safety clearance. Every response carries the disclaimer; agents should keep it.
  2. Missing data is stated, never invented. Thin destinations return an honest "not enough history" rather than a guess.

Security

Read-only by designNo write tools — the server cannot create, modify, or delete anything. The worst a prompt injection can achieve through it is reading public dive data.
No auth, no tokens, no user dataNothing to leak, phish, or exfiltrate; connecting grants an agent no identity.
Stateless JSON modeOne POST in, one JSON body out; no sessions, no server-push channel.
HTTPS only, CORS openRead-only public data.

Transport & limits

Streamable HTTP (JSON-RPC 2.0 over POST), stateless — protocol versions 2024-11-052025-06-18.

Free for individual and assistant use at fair, non-bulk volumes; per-IP rate limiting applies. For sustained high-volume or commercial integrations, write to team@pickadive.com.

Example agent guidance (optional)

Add to your AGENTS.md / CLAUDE.md to reduce round-trips:

## PickADive MCP
- For "can I dive…?" questions use find_dive_windows with the user's
  place; default day is Saturday.
- For trip planning use best_time_to_dive per destination; present
  depths/waves in the user's customary units, keep wind in knots.
- Always keep the safety disclaimer and cite the linked page.

Support & feedback

License

MIT — see LICENSE. The PickADive name and logo are trademarks of PickADive and are not covered by the code license.

Disclaimer

Dive conditions are graded forecasts — planning context only, never a safety judgment about any specific dive on any specific day. Always assess conditions at the water, dive within your training, and follow local guidance. Wildlife seasonality reflects recorded sightings, never a promise of encounters.

Tools it offers (5)

What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.

  • find_dive_windows
  • species_seasonality
  • top_dive_regions
  • site_facts
  • best_time_to_dive

Signals

Last commit
Aug 2026
Advanced
Delivery
mcp MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
Catalog kind
mcp-server
Gateway key
com-pickadive-mcp
Source
github.com/afiliptsov/pickadive-mcp
Hosted endpoint
https://pickadive.com/mcp