check_departure_live — Sparkling Tracks Tours MCP Tool Read-only
check_departure_live
(check departure live) 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 check_departure_live from your client
- Claude Code Sparkling Tracks Tours check_departure_live run in your project directory
- Claude Desktop Sparkling Tracks Tours check_departure_live ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sparkling Tracks Tours check_departure_live ~/.cursor/mcp.json
- VS Code Sparkling Tracks Tours check_departure_live .vscode/mcp.json
- Zed Sparkling Tracks Tours check_departure_live ~/.config/zed/settings.json
- Windsurf Sparkling Tracks Tours check_departure_live ~/.codeium/windsurf/mcp_config.json
- Cline Sparkling Tracks Tours check_departure_live ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sparkling Tracks Tours check_departure_live ~/.gemini/settings.json
- Grok Sparkling Tracks Tours check_departure_live .mcp.json (in your project root)
- ChatGPT Sparkling Tracks Tours check_departure_live Settings → Connectors → Advanced → Developer mode
- Claude.ai Sparkling Tracks Tours check_departure_live Settings → Connectors → Add custom connector
- LangChain Sparkling Tracks Tours check_departure_live 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.