buyer_capabilities — AgentWork Outcome Router MCP Tool
buyer_capabilities
(buyer capabilities) 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 buyer_capabilities from your client
- Claude Code AgentWork Outcome Router buyer_capabilities run in your project directory
- Claude Desktop AgentWork Outcome Router buyer_capabilities ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentWork Outcome Router buyer_capabilities ~/.cursor/mcp.json
- VS Code AgentWork Outcome Router buyer_capabilities .vscode/mcp.json
- Zed AgentWork Outcome Router buyer_capabilities ~/.config/zed/settings.json
- Windsurf AgentWork Outcome Router buyer_capabilities ~/.codeium/windsurf/mcp_config.json
- Cline AgentWork Outcome Router buyer_capabilities ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentWork Outcome Router buyer_capabilities ~/.gemini/settings.json
- Grok AgentWork Outcome Router buyer_capabilities .mcp.json (in your project root)
- ChatGPT AgentWork Outcome Router buyer_capabilities Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentWork Outcome Router buyer_capabilities Settings → Connectors → Add custom connector
- LangChain AgentWork Outcome Router buyer_capabilities 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.