RoxyBrowser MCP Server
OfficialThe RoxyBrowser MCP Server enables programmatic management of RoxyBrowser antidetect browser environments via MCP tools, covering browser lifecycle, proxy, account, workspace, and health operations.
Browser Management
List, create (individually or in batch), open, close, update, delete, and get detailed info for browsers
Open browsers and retrieve CDP WebSocket endpoints and PIDs for automation
Configure OS, user agent, core version, search engine, default URLs, and fingerprinting options (WebGL, Canvas, WebRTC, timezone, geolocation, resolution, device memory, etc.)
Randomize a browser's fingerprint for enhanced anonymity
Clear local or server-side cache for specific browser instances
List labels within a workspace for browser organization
Proxy Management
List, create (individually or in batch), get detail, detect/test, modify, and delete proxy configurations
Supports HTTP, HTTPS, SOCKS5, and SSH proxy types
Platform Account Management
List, create (individually or in batch), modify, and delete platform accounts with credentials (username, password, cookies, EFA, URL, remarks)
Workspace & Health
List all workspaces and their projects
Perform a health check to verify the RoxyBrowser server is running and reachable
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RoxyBrowser MCP Serveropen a new browser in workspace 1"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RoxyBrowser MCP Server 2.0
RoxyBrowser MCP Server 2.0 is a breaking redesign of the RoxyBrowser OpenAPI MCP package. The 1.x line remains available for compatibility maintenance; 2.0 is built for embedded MCP usage, fixed workspace/project context, instance-based configuration, and unit-tested runtime behavior.
Install
npm install @roxybrowser/openapi@betaRelated MCP server: open_browser_use
CLI Usage
roxybrowser-openapi-mcp --api-key "YOUR_API_KEY"Options:
-H, --api-host <url>: RoxyBrowser API base URL. Default:http://127.0.0.1:50000-k, --api-key <key>: RoxyBrowser API key.-t, --timeout <ms>: request timeout. Default:30000
Environment variables are also supported: ROXY_API_HOST, ROXY_API_KEY, ROXY_TIMEOUT.
Embedded MCP Usage
import { createRoxyMcpServer } from '@roxybrowser/openapi'
import { InMemoryTransport } from '@modelcontextprotocol/sdk/inMemory.js'
const server = createRoxyMcpServer({
roxy: {
apiKey: 'YOUR_API_KEY',
apiHost: 'http://127.0.0.1:50000',
},
context: {
workspaceId: 123,
},
})
const [clientTransport, serverTransport] = InMemoryTransport.createLinkedPair()
await server.connect(serverTransport)When context.workspaceId is provided, workspace-scoped tools no longer expose workspaceId in their public MCP schema. The runtime injects it into tool calls automatically and rejects conflicting caller-provided values.
In fixed workspace mode, roxy_workspace_list is hidden and roxy_project_list is exposed instead. roxy_project_list returns projects under the bound workspace.
SDK Client
import { RoxyClient } from '@roxybrowser/openapi'
const client = new RoxyClient({
apiKey: 'YOUR_API_KEY',
apiHost: 'http://127.0.0.1:50000',
})
const health = await client.request('/health')Tool Names
Public MCP tool names use OpenAI-safe underscores:
roxy_workspace_listroxy_project_list(fixed workspace mode)roxy_health_checkroxy_browser_listroxy_browser_create(array input; supports one or many browsers)roxy_browser_openroxy_browser_closeroxy_browser_updateroxy_browser_deleteroxy_browser_detailroxy_browser_connection_inforoxy_browser_clear_local_cacheroxy_browser_clear_server_cacheroxy_browser_list_labelsroxy_proxy_listroxy_proxy_detailroxy_proxy_create(array input; supports one or many proxies)roxy_proxy_detectroxy_proxy_modifyroxy_proxy_deleteroxy_account_listroxy_account_create(array input; supports one or many accounts)roxy_account_modifyroxy_account_delete
Development
npm install
npm run build
npm testThe test suite uses node:test and includes runtime, client, MCP InMemoryTransport, tool catalog coverage, and real RoxyBrowser API integration coverage.
Real integration tests load .env through dotenv/config and require:
ROXY_API_KEY="YOUR_API_KEY"
ROXY_API_HOST="http://127.0.0.1:50000"
ROXY_TEST_WORKSPACE_ID="123"Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/roxybrowserlabs/roxybrowser-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server