plan_trip — skimetric MCP Tool
plan_trip
(plan trip) 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 plan_trip from your client
- Claude Code skimetric plan_trip run in your project directory
- Claude Desktop skimetric plan_trip ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor skimetric plan_trip ~/.cursor/mcp.json
- VS Code skimetric plan_trip .vscode/mcp.json
- Zed skimetric plan_trip ~/.config/zed/settings.json
- Windsurf skimetric plan_trip ~/.codeium/windsurf/mcp_config.json
- Cline skimetric plan_trip ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI skimetric plan_trip ~/.gemini/settings.json
- Grok skimetric plan_trip .mcp.json (in your project root)
- ChatGPT skimetric plan_trip Settings → Connectors → Advanced → Developer mode
- Claude.ai skimetric plan_trip Settings → Connectors → Add custom connector
- LangChain skimetric plan_trip pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http skimetric https://skimetric.eu/mcpOther tools on this server
- find_resorts
- where_to_ski
- 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
- 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.