MCP Protocol

Pro users get an HTTP endpoint based on the Model Context Protocol (MCP). Cursor, Claude Desktop, and other AI tools can control browser profiles and combine with Playwright MCP for page automation.

Pro feature

MCP uses the same local service as the REST API. Sign in as Pro and copy the URL from the client API menu.

Endpoint

After the service starts:

http://localhost:{port}/mcp

• {port} is shown in the client API menu (not fixed to 9000)
• Transport: Streamable HTTP

Copy the full MCP URL from the client.

Built-in tools

Tool	Description
getBrowserList	List profiles (id, name, group, etc.)
launchBrowser	Start a profile; returns debuggingPort for Playwright
stopBrowser	Stop a profile

After launch, the service may attach Playwright MCP so agents can drive pages over CDP.

Configure in Cursor

1. Start Virtual Browser and open API; confirm MCP is available (not “VIP only”)
2. Add an HTTP MCP server in Cursor with the MCP URL
3. Complete initialize per your MCP client (mcp-session-id headers are handled by the SDK)

TIP

For headless CLI startup, run VirtualBrowser.exe --cli, then --cli-print --cli-json to get port and append /mcp.

REST API vs MCP

Approach	Best for
REST API	Scripts, Playwright/Selenium over CDP, classic automation
MCP	AI agents, natural language control, IDE integration

Same local port: REST under /api/*, MCP under /mcp.

Related

• Automation API
• CLI mode
• API overview
• MCP API reference