routes — Aviationstack MCP Tool
routes
(routes) is one of 42 tools on the
Aviationstack
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call routes from your client
- Claude Code Aviationstack routes run in your project directory
- Claude Desktop Aviationstack routes ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Aviationstack routes ~/.cursor/mcp.json
- VS Code Aviationstack routes .vscode/mcp.json
- Zed Aviationstack routes ~/.config/zed/settings.json
- Windsurf Aviationstack routes ~/.codeium/windsurf/mcp_config.json
- Cline Aviationstack routes ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Aviationstack routes ~/.gemini/settings.json
- Grok Aviationstack routes .mcp.json (in your project root)
- ChatGPT Aviationstack routes Settings → Connectors → Advanced → Developer mode
- Claude.ai Aviationstack routes Settings → Connectors → Add custom connector
- LangChain Aviationstack routes pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aviationstack https://gateway.pipeworx.io/aviationstack/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- flights
- airports
- airlines
- cities
- countries
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.