MCP Server
Themeshbrow-mcp server exposes Meshbrow’s stealth browser capabilities as MCP tools. Compatible with Claude Desktop, VS Code Copilot, Cursor, and any MCP-compatible client.
Installation
- Homebrew (macOS/Linux)
- Go Install
- Binary
- Docker
Configuration
Claude Desktop
Add to~/Library/Application Support/Claude/claude_desktop_config.json:
VS Code (GitHub Copilot)
Add to.vscode/mcp.json in your project:
Cursor
Add to.cursor/mcp.json:
Standalone (WebSocket)
Run the MCP server over WebSocket for remote/shared access:CLI Flags
| Flag | Env Variable | Default | Description |
|---|---|---|---|
--mode | MESHBROW_MCP_MODE | stdio | Transport: stdio or ws |
--port | MESHBROW_MCP_PORT | 9090 | WebSocket listen port |
--api-url | MESHBROW_API_URL | https://api.meshbrow.dev | API endpoint |
--api-key | MESHBROW_API_KEY | (required) | Your API key |
--log-level | MESHBROW_LOG_LEVEL | info | Log level |
Available Tools
Session Management
| Tool | Description |
|---|---|
session_create | Launch a stealth browser session with proxy and fingerprint |
session_list | List all active sessions |
session_get | Get session details and CDP endpoint |
session_destroy | Destroy a session (optionally save profile) |
Browser Actions
| Tool | Description |
|---|---|
browser_navigate | Navigate to a URL |
browser_screenshot | Take a screenshot (base64 PNG) |
browser_click | Click an element by CSS selector |
browser_type | Type text into an input field |
browser_extract | Extract text/data from the page |
browser_execute | Execute arbitrary JavaScript |
browser_wait | Wait for an element to appear |
browser_scroll | Scroll the page |
Profiles
| Tool | Description |
|---|---|
profile_create | Create a persistent browser profile |
profile_list | List saved profiles |
profile_get | Get profile details |
profile_delete | Delete a profile |
Fleet
| Tool | Description |
|---|---|
fleet_create | Launch multiple sessions in parallel |
fleet_status | Check fleet session statuses |
fleet_destroy | Destroy all fleet sessions |
Example: AI Agent Web Research
Security
The MCP server enforces:- API key required — all tool calls require a valid
MESHBROW_API_KEY - Session isolation — each session runs in its own network namespace
- No credential leakage — proxy credentials and fingerprint internals are never exposed in tool responses
- Structured logging — all operations are logged to stderr (never stdout, which is reserved for MCP protocol)
Best Practices
Reuse sessions across related tasks
Reuse sessions across related tasks
Use profiles for authenticated workflows
Use profiles for authenticated workflows
Store login cookies in profiles so agents don’t need to re-authenticate each time.
Always destroy sessions
Always destroy sessions
Include cleanup in your agent’s error handling. Leaked sessions cost money and resources.
Prefer extract over screenshots
Prefer extract over screenshots
Text extraction is faster and uses fewer tokens than screenshot-based approaches.