plan_multi_city_trip — Sparkling Tracks Tours MCP Tool
plan_multi_city_trip
(plan multi city trip) is one of 15 tools on the
Sparkling Tracks Tours
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call plan_multi_city_trip from your client
- Claude Code Sparkling Tracks Tours plan_multi_city_trip run in your project directory
- Claude Desktop Sparkling Tracks Tours plan_multi_city_trip ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sparkling Tracks Tours plan_multi_city_trip ~/.cursor/mcp.json
- VS Code Sparkling Tracks Tours plan_multi_city_trip .vscode/mcp.json
- Zed Sparkling Tracks Tours plan_multi_city_trip ~/.config/zed/settings.json
- Windsurf Sparkling Tracks Tours plan_multi_city_trip ~/.codeium/windsurf/mcp_config.json
- Cline Sparkling Tracks Tours plan_multi_city_trip ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sparkling Tracks Tours plan_multi_city_trip ~/.gemini/settings.json
- Grok Sparkling Tracks Tours plan_multi_city_trip .mcp.json (in your project root)
- ChatGPT Sparkling Tracks Tours plan_multi_city_trip Settings → Connectors → Advanced → Developer mode
- Claude.ai Sparkling Tracks Tours plan_multi_city_trip Settings → Connectors → Add custom connector
- LangChain Sparkling Tracks Tours plan_multi_city_trip pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.sparklingtracks.com/mcpOther tools on this server
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.