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
- Start Virtual Browser and open API; confirm MCP is available (not “VIP only”)
- Open Settings → MCP, add an HTTP server
- Paste the full MCP URL from the client (e.g.
http://localhost:{port}/mcp) - Reload MCP in Cursor; tools such as
getBrowserListandlaunchBrowsershould appear
Example (replace port with yours):
json
{
"mcpServers": {
"virtual-browser": {
"url": "http://localhost:9000/mcp"
}
}
}TIP
For headless CLI startup, run VirtualBrowser.exe --cli, then --cli-print --cli-json to get port and append /mcp.
Configure in Claude Desktop
- Active Pro membership and a working MCP URL on the API screen
- Edit the Claude Desktop config file (path depends on OS—see MCP docs)
- Add the same HTTP entry under
mcpServersand restart Claude
Example prompts
- “Call getBrowserList and list my profiles.”
- “launchBrowser id 1, then open https://example.com with Playwright.”
- “stopBrowser id 1.”
See Playwright integration if page automation fails after launch.
Troubleshooting
| Symptom | Fix |
|---|---|
| VIP only | Subscribe to Pro |
| Connection refused | Client not running or wrong port |
| Empty tool list | Restart client and MCP host; allow localhost in firewall |
| Session errors | Use a client that supports Streamable HTTP for 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.