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
Available Tools
Session Management
Browser Actions
Profiles
Fleet
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
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.