resolve_blocker — AgentWork Outcome Router MCP Tool Read-only
resolve_blocker
(resolve blocker) is one of 10 tools on the
AgentWork Outcome Router
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolve_blocker from your client
- Claude Code AgentWork Outcome Router resolve_blocker run in your project directory
- Claude Desktop AgentWork Outcome Router resolve_blocker ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentWork Outcome Router resolve_blocker ~/.cursor/mcp.json
- VS Code AgentWork Outcome Router resolve_blocker .vscode/mcp.json
- Zed AgentWork Outcome Router resolve_blocker ~/.config/zed/settings.json
- Windsurf AgentWork Outcome Router resolve_blocker ~/.codeium/windsurf/mcp_config.json
- Cline AgentWork Outcome Router resolve_blocker ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentWork Outcome Router resolve_blocker ~/.gemini/settings.json
- Grok AgentWork Outcome Router resolve_blocker .mcp.json (in your project root)
- ChatGPT AgentWork Outcome Router resolve_blocker Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentWork Outcome Router resolve_blocker Settings → Connectors → Add custom connector
- LangChain AgentWork Outcome Router resolve_blocker pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentwork https://agent-work-api.agentwork-market.workers.dev/mcpOther tools on this server
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.