Skip to main content
Claude Desktop speaks MCP over Streamable HTTP natively. Add one entry to claude_desktop_config.json and the Computer Use tools appear next to your other MCP servers.

​
Managed Yambr

{
  "mcpServers": {
    "yambr-computer-use": {
      "url": "https://api.yambr.com/mcp/computer_use",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer sk-yambr-...",
        "X-Chat-Id": "claude-desktop"
      }
    }
  }
}
Get the key at app.yambr.com. Use a stable X-Chat-Id for a persistent sandbox; rotate it to start fresh. Claude Desktop uses your Anthropic subscription for the model — we only provide the tools. Why MCP-only →

​
Self-hosted

{
  "mcpServers": {
    "computer-use": {
      "url": "http://localhost:8081/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer <MCP_API_KEY>",
        "X-Chat-Id": "desktop-session"
      }
    }
  }
}

​
Config file location

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop. You should see the Computer Use tools in the tool picker.

​
Single-user mode (self-hosted)

Since Claude Desktop is one user, flip the self-hosted server to single-user mode so you don’t have to manage X-Chat-Id: 
echo "SINGLE_USER_MODE=true" >> .env
docker compose restart computer-use-server
Every request then reuses the same sandbox; X-Chat-Id can be anything. Managed Yambr runs strict multi-user — always pass a meaningful X-Chat-Id.

​
Headers reference

HeaderRequiredPurpose
AuthorizationYesBearer <yambr-key> or Bearer <MCP_API_KEY>
X-Chat-IdYes (strict mode)Session identifier → one sandbox per id
X-User-EmailNoPer-user skills / PAT lookup
X-User-NameNoDisplay name (URL-encoded)
X-MCP-ServersNoComma-separated MCP server names passed to the sub_agent