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