Connectors / Hobbies, outdoors & playing sport

OhMyWind

OhMyWind helps sailors answer three questions: which way to go, when to leave, and how comfortable the trip will be.

Describe a passage and OhMyWind compares departure times, estimates the arrival leg by leg from your boat’s polar, and qualifies the conditions on the way: wind strength and angle, sea state, wind against tide, share of motoring. An interactive card shows the departures, the route on a map and the detail of each leg, with a link to adjust the plan on ohmywind.fr.

MCP connector

Server URL: https://mcp.ohmywind.fr/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: OhMyWind answers sailors' weather, sea and tide questions on European coasts, from marine forecasts and tidal atlases. Pick the tool by the question:
A place rather than a passage (wind at Groix this afternoon, when the mistral eases, the thermal breeze, whether the models agree): .
When to be at a pass, slack water, high or low water, the tidal coefficient: . It costs no weather request.
A trip from A to B (does it go, how long, which departure): , comparing departures unless the user pins a time. A day out and back is two trips: plan the return as well.
Two ways to go (north or south of an island, two destinations): one call with alternatives.
A cruise of several days (a week out of Biograd, a loop of the islands) is not one passage: read the days ahead at the cruising area with one call, and plan only the next leg.
How OhMyWind computes: . Don't call OhMyWind's tools for questions that are not about weather, sea or tide (gear, regulations, marinas, formalities), nor for typical seasonal weather beyond about 16 days (the meltem in July): no forecast reaches that far. Send every time with the user's UTC offset: the answers come back in that offset, so read them as the user's clock, and each departure carries its weekday: check it is the day the user named. Take the coordinates of the place itself, the pass rather than the nearest town: a few kilometres off a pass the stream is a fraction of its strength. Make independent calls in the same turn: the stream at a pass and the wind there, the outbound and return legs. Durations are under sail alone unless you pass motor_threshold_kn and motor_speed_kn: when the user must arrive by a given time (before dark) on a boat with an engine, pass 4 and 5.5, a cruiser under 4 kn motors. The values are model forecasts, not observations of what is blowing right now; real-time conditions and warnings come from the official sources (the CROSS bulletin on VHF, the national weather service). Reliability falls with lead time: AROME up to two days, ICON-EU to five, ECMWF to ten, GFS beyond; past five days they show a trend, not a plan. Reuse a result already in the conversation rather than asking again for the same place and dates, and for a quick question compare departures every three to six hours, not every hour.

Tools

Reads data5

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.ohmywind.fr/mcp

None

Protocol

MCP 2025-11-25

Instructions

OhMyWind answers sailors' weather, sea and tide questions on European coasts, from marine forecasts and tidal atlases. Pick the tool by the question:

A place rather than a passage (wind at Groix this afternoon, when the mistral eases, the thermal breeze, whether the models agree): .

When to be at a pass, slack water, high or low water, the tidal coefficient: . It costs no weather request.

A trip from A to B (does it go, how long, which departure): , comparing departures unless the user pins a time. A day out and back is two trips: plan the return as well.

Two ways to go (north or south of an island, two destinations): one call with alternatives.

A cruise of several days (a week out of Biograd, a loop of the islands) is not one passage: read the days ahead at the cruising area with one call, and plan only the next leg.

How OhMyWind computes: . Don't call OhMyWind's tools for questions that are not about weather, sea or tide (gear, regulations, marinas, formalities), nor for typical seasonal weather beyond about 16 days (the meltem in July): no forecast reaches that far. Send every time with the user's UTC offset: the answers come back in that offset, so read them as the user's clock, and each departure carries its weekday: check it is the day the user named. Take the coordinates of the place itself, the pass rather than the nearest town: a few kilometres off a pass the stream is a fraction of its strength. Make independent calls in the same turn: the stream at a pass and the wind there, the outbound and return legs. Durations are under sail alone unless you pass motor_threshold_kn and motor_speed_kn: when the user must arrive by a given time (before dark) on a boat with an engine, pass 4 and 5.5, a cruiser under 4 kn motors. The values are model forecasts, not observations of what is blowing right now; real-time conditions and warnings come from the official sources (the CROSS bulletin on VHF, the national weather service). Reliability falls with lead time: AROME up to two days, ICON-EU to five, ECMWF to ten, GFS beyond; past five days they show a trend, not a plan. Reuse a result already in the conversation rather than asking again for the same place and dates, and for a quick question compare departures every three to six hours, not every hour.