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