OhMyWind

fr.ohmywind/sailing-planner

Sailing passage planner for any coast, with high-precision tides on the French Atlantic.

Yes, your AI can use this right now.Answered a live MCP handshake in 704 ms with no sign-in needed and exposes 4 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://mcp.ohmywind.fr/mcp

4 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
read_meread-only

Return OhMyWind's calculation methodology as Markdown. Call this when the user asks how passage timing, complexity, or boat speed are computed (e.g. "comment c'est calculé ?", "what assumptions does the model use?", "is tacking modelled?"). The returned text covers: polar lookup, default efficiency 0.75, VMG / tacking correction, wave derate, single-pass t

list_boat_archetypesread-only

List the boat archetypes with descriptive metadata. The LLM (or user) maps a commercial model (e.g. "Sun Odyssey 32") to one of these archetypes from the metadata — there is no server-side mapping. ``voile_aviron_16ft`` is for open sail-and-oar dinghies only (no cabin, rowed as well as sailed); a small cabin cruiser maps to ``cruiser_20ft``.

get_marine_forecastread-only

Fetch wind (and sea, when available) for a point and time window. Args: lat: latitude in degrees. lon: longitude in degrees. start: ISO-8601 datetime, timezone-aware (e.g. "2026-05-01T06:00:00+00:00"). end: ISO-8601 datetime, timezone-aware. models: optional list of model names; defaults to AROME for the Med. Pass a poin

plan_passageread-only

Plan an A→B passage. Compare departure windows by default; pin a single departure only when the user gives an explicit time. ## Tool routing: read this first Before calling, classify the user's question: 1. **Pure weather lookup at a point** ("y aura-t-il du vent à Cassis samedi à 14h ?", "quelles vagues dimanche au cap Sicié ?"): call ``get

Alternatives in Other

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”