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