OhMyWind is an MCP server with 4 tools an agent can call, among them get_marine_forecast, list_boat_archetypes, plan_passage. It answers at https://mcp.ohmywind.fr/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Sailing passage planner for any coast, with high-precision tides on the French Atlantic.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_marine_forecast | 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 Inputs: lat, lon, start, end, models |
list_boat_archetypes | List the 7 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. |
plan_passage | 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* Inputs: waypoints, departure, archetype, efficiency, segment_length_nm, model |
read_me | 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?"). |
Every block below points at https://mcp.ohmywind.fr/mcp. Pick your client and copy.
claude mcp add --transport http ohmywind https://mcp.ohmywind.fr/mcp
{
"mcpServers": {
"ohmywind": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.ohmywind.fr/mcp"]
}
}
}{
"mcpServers": {
"ohmywind": {
"url": "https://mcp.ohmywind.fr/mcp"
}
}
}{
"servers": {
"ohmywind": {
"type": "http",
"url": "https://mcp.ohmywind.fr/mcp"
}
}
}{
"context_servers": {
"ohmywind": {
"url": "https://mcp.ohmywind.fr/mcp"
}
}
}{
"mcpServers": {
"ohmywind": {
"serverUrl": "https://mcp.ohmywind.fr/mcp"
}
}
}{
"mcpServers": {
"ohmywind": {
"url": "https://mcp.ohmywind.fr/mcp"
}
}
}name: OhMyWind
version: 0.0.1
schema: v1
mcpServers:
- name: OhMyWind
type: streamable-http
url: https://mcp.ohmywind.fr/mcp{
"mcpServers": {
"ohmywind": {
"httpUrl": "https://mcp.ohmywind.fr/mcp"
}
}
}{
"mcpServers": {
"ohmywind": {
"type": "http",
"url": "https://mcp.ohmywind.fr/mcp"
}
}
}{
"mcpServers": {
"ohmywind": {
"url": "https://mcp.ohmywind.fr/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.ohmywind.fr%2Fmcp&type=streamable_http&id=ohmywind&name=OhMyWind
It answered our last check on 19 October 2026 in 406 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by ohmywind.fr and served from mcp.ohmywind.fr, the vendor's own domain: https://mcp.ohmywind.fr/mcp.
4, as returned by the server's own tools/list on 11 September 2026: get_marine_forecast, list_boat_archetypes, plan_passage, read_me.
It answered our last check on 19 October 2026 in 406 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.ohmywind.fr/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: fr.ohmywind. Endpoint host: mcp.ohmywind.fr. ARD identifier: urn:air:fr.ohmywind:mcp:sailing-planner.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.