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