where_to_ski — skimetric MCP Tool
where_to_ski
(where to ski) is one of 25 tools on the
skimetric
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call where_to_ski from your client
- Claude Code skimetric where_to_ski run in your project directory
- Claude Desktop skimetric where_to_ski ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor skimetric where_to_ski ~/.cursor/mcp.json
- VS Code skimetric where_to_ski .vscode/mcp.json
- Zed skimetric where_to_ski ~/.config/zed/settings.json
- Windsurf skimetric where_to_ski ~/.codeium/windsurf/mcp_config.json
- Cline skimetric where_to_ski ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI skimetric where_to_ski ~/.gemini/settings.json
- Grok skimetric where_to_ski .mcp.json (in your project root)
- ChatGPT skimetric where_to_ski Settings → Connectors → Advanced → Developer mode
- Claude.ai skimetric where_to_ski Settings → Connectors → Add custom connector
- LangChain skimetric where_to_ski pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http skimetric https://skimetric.eu/mcpOther tools on this server
- find_resorts
- snow_forecast
- conditions
- season_history
- mountain_facts
- season_fortnights
- open_outlook
- start_powder_alert
- start_country_alert
- skier_notes
- resort_writeup
- watch_resort
- watch_country
- getting_there
- trip_costs
- daily_snow
- booking_options
- open_booking
- plan_trip
- choose_path
- resort_media
- tell_skym
- webcams
- trip_status
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.