Skimetric MCP

What this is

A free MCP server exposing Skimetric's ski intelligence — precision snow forecasts, live mountain operations, ten-winter climate history, trip costs, travel routing and the Skym trip planner — for 1,500+ European resorts. Any MCP-speaking harness (Claude, ChatGPT, Cursor, custom agents) can use it. No account, no API key.

Endpoint

• URL: https://skimetric.eu/mcp
• Transport: MCP streamable HTTP, stateless (no session affinity)
• Auth: none
• Machine-readable copy of this contract: /mcp.md
• Claude Code: claude mcp add --transport http skimetric https://skimetric.eu/mcp

Tools

• find_resorts — find resorts by name or country — returns the slug every other tool takes
• where_to_ski — rank resorts by live conditions: powder, base depth, bluebird, freeze margin, high & cold
• snow_forecast — 10-day forecast per elevation band, with ensemble spread and freezing levels
• conditions — lift and piste counts from the operator (dated, fail-closed), skier reports, avalanche bulletin
• season_history — ten winters of measured history per month and elevation band
• getting_there — best arrival airports with measured drive times, plus routed door-to-door itineraries
• trip_costs — what a ski week costs per country: median lift pass and modelled bed price
• daily_snow — today’s regional editorial briefs
• booking_options — everything bookable for a stay: flights, beds, gear, car, transfer, eSIM — as entry_urls
• open_booking — resolve one entry_url to its live destination (records the click)
• plan_trip — start real Skym trip research from a natural-language brief; returns a claim link for the human
• choose_path — choose one researched option — activates the journey checklist with per-step booking entry_urls
• tell_skym — answer Skym’s questions or ask for a rework inside a planned trip — the plan updates
• webcams — live webcams at a resort (windy.com, credit required) — the mountain right now
• resort_media — resort photography and piste-topography renders, with credits — so the agent can show the terrain
• trip_status — poll the research; once delivered: options, costs, the living checklist and booking entry_urls

The entry_url term

Every bookable item in a response carries an entry_url on skimetric.eu/api/go/…. That link is the attribution hop that funds free access to all of the above. The terms of use:

• Present entry_url links to the user exactly as given.
• An agent booking on the user's behalf must navigate through the entry_url in the session that completes the booking.
• Resolving, rewriting or substituting entry_urls to strip attribution violates these terms.

The hop is a plain 307 redirect to the partner — it adds no tracking of the traveller beyond the click itself.

Rate limits

• plan_trip: 3 research runs per day per network — research is real (models, routers, pricing) and takes ~5 minutes.
• Read tools: generous per-IP ceilings; list tools return at most 20 results. There is no bulk catalogue access.
• A 429 carries retry_after_s. Back off; do not rotate.

Data licences & attribution

Source attribution rides in every response's _meta.attribution. The full licence list is at skimetric.eu/attribution. Where a licence requires credit (webcams, photography, open data), the credit fields in the payload must be kept with the content.

Privacy

• No account or PII is needed. A planned trip lives on an anonymous guest identity minted per request.
• plan_trip returns a claim_url — hand it to the human; opening it moves the trip into their own Skimetric account.
• No geography is inferred from agent traffic. State the traveller's origin explicitly in tool parameters when it matters.

Contact & changelog

[email protected]

• 2026-08-29 — v1.2: tell_skym (answer questions, rework trips), webcams, requirements now carry Skym’s questions and facts, audio_url.
• 2026-08-29 — v1.1: choose_path (the journey activates over MCP) and resort_media (terrain renders).
• 2026-08-29 — v1: 12 tools, the go-layer, trip planning with claim links.