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