roxybrowser

This MCP server provides programmatic control over RoxyBrowser instances, proxies, and related workspace assets via the Model Context Protocol. It exposes a set of tools to create, open, manage, and monitor browser sessions, retrieve Chrome DevTools Protocol (CDP) endpoints for automation, and integrate with Playwright-based automation flows. Use this server to provision browsers, assign proxies, and fetch CDP endpoints that your AI agents or automation pipelines can connect to for browser automation. The server is designed to work alongside the RoxyBrowser Playwright MCP, enabling seamless handoffs between browser provisioning, opening, and Playwright-driven automation tasks. Typical workflows include creating a browser, opening it to obtain a CDP endpoint, and then performing automation steps such as navigation, typing, and clicking via Playwright MCP-compatible commands.

Prerequisites:

• Node.js (14.x or newer) and npm/yarn installed
• Access to a RoxyBrowser instance with API enabled and a valid API key (for features requiring API calls)

Installation steps:

1. Install the MCP server package (example using npm): npm install -g roxybrowser-mcp-server

2. Verify installation: roxybrowser-mcp-server --version

3. Configure environment (optional but recommended for API access):

   • Ensure ROXY_API_KEY and ROXY_API_HOST are set if the server communicates with RoxyBrowser APIs
   • Example (bash): export ROXY_API_KEY="your_api_key" export ROXY_API_HOST="http://127.0.0.1:50000"

4. Run the MCP server (development/test): npm run dev

5. In production, build or run the server as appropriate for your deployment environment (e.g., using a process manager like PM2 or systemd).

Environment variables: The server may require ROXY_API_KEY and ROXY_API_HOST to access RoxyBrowser APIs for certain features (proxy management, account handling, etc.). Ensure network access to the RoxyBrowser API port (default 50000) and verify API keys are correctly configured. If you encounter connection issues, confirm that RoxyBrowser is running, API status is enabled, and that your API host/port are reachable from the MCP server. For production deployments, consider secure handling of API keys (e.g., secret managers) and restricting access to the MCP endpoints. Regularly update to the latest versions of the MCP server and compatible Playwright MCP to ensure compatibility with RoxyBrowser features like fingerprinting and cache management.