roxybrowser-mcp-server
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.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses an API key supplied via CLI/env vars and targets a local API host by default. No scope granularity or rotation guidance is provided. README does not state whether TLS is enforced on the upstream RoxyBrowser API host; examples use http://127.0.0.1:50000. No dependency vulnerability status is provided in the manifest beyond basic dependencies.
⚡ Reliability
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).
Use Cases
- • Automate browser lifecycle (create/open/close/delete) for RoxyBrowser instances
- • Retrieve CDP WebSocket endpoints to drive browser automation via CDP-based tools
- • Build agent workflows that manage workspaces, proxies, and accounts before launching automation
- • Provide an MCP-compatible integration path for AI assistants to control RoxyBrowser
- • Run connectivity diagnostics via a health check tool
Not For
- • Use as a standalone browser automation engine (it delegates to RoxyBrowser and other tools like Playwright MCP for actual page interactions)
- • Environments that cannot securely store and supply an API key to the MCP server
- • Use cases requiring documented REST/OpenAPI endpoints for this MCP server itself (the README references an OpenAPI package but does not provide an OpenAPI URL/spec in this repo content)
Interface
Authentication
Authentication is provided as a single API key passed to the MCP server environment/CLI; the README does not describe OAuth flows or fine-grained scopes.
Pricing
RoxyBrowser itself likely has pricing (e.g., profile quota), but package pricing/tiers are not described in the provided README/manifest.
Agent Metadata
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.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for roxybrowser-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.