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