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