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