mcp_servers config lets you register Computer Use as a tool-providing MCP server and expose it to any model call routed through your proxy. Your LiteLLM still handles LLM traffic; Yambr stays a tool provider.
Pointing LiteLLM at managed Yambr
chat/completions endpoint — see Access model.
Pointing LiteLLM at a self-hosted Computer Use Server
mcp_servers section of your LiteLLM config. The {chat_id} and {user_email} templates get filled from the incoming request context.
Networking
If LiteLLM and the Computer Use Server run in the same Docker compose network, use the service name (computer-use-server:8081). Across hosts, use the public URL — matching the server’s PUBLIC_BASE_URL for consistency.
Claude Code through LiteLLM
The sandbox’ssub_agent tool runs Claude Code. To route Claude Code’s own API traffic through LiteLLM, set the gateway vars in the Computer Use Server’s .env:
MCP-servers-for-sub-agent
LiteLLM can act as an MCP gateway for multiple servers. PassX-MCP-Servers: github,jira,slack on the incoming Computer Use request — the server writes ~/.mcp.json in the sandbox with URLs templated as {ANTHROPIC_BASE_URL}/mcp/{server_name}. Claude Code picks them up automatically. See Sub-agents.
Related
- Yambr LiteLLM gateway — managed setup
- MCP API reference — raw endpoint details
