{"id":"roxybrowserlabs-roxybrowser-mcp-server","name":"roxybrowser-mcp-server","af_score":60.0,"security_score":51.0,"reliability_score":32.5,"what_it_does":"An MCP server that integrates with RoxyBrowser to manage browser instances and return Chrome DevTools Protocol (CDP) WebSocket endpoints for automation. It exposes MCP tools for workspace/browser/proxy/account management and health checks, and can be run via CLI, in-process (stdio), or used as a library for direct tool handler calls.","best_when":"You already run RoxyBrowser with its API enabled and want an MCP tool layer to create/open browsers, optionally configure proxies/accounts, and obtain CDP endpoints for downstream automation.","avoid_when":"You need strong guarantees about idempotent operations, retry safety, or detailed rate-limit/error-code specifications for agent orchestration (these are only partially described).","last_evaluated":"2026-03-30T15:27:34.042736+00:00","has_mcp":true,"has_api":false,"auth_methods":["API key via ROXY_API_KEY / --api-key"],"has_free_tier":false,"known_gotchas":["Config is read at process start and cannot be changed at runtime (env/config timing matters for agents).","Closing browsers does NOT free quota; only deletion does.","Correct dirIds/workspace IDs are required; agents should use list tools and health checks before opening."],"error_quality":null}