Browser MCP

A Model Context Protocol (MCP) server that provides browser automation capabilities usingAnchor Browser's remote browser service withPlaywright. This server enables LLMs to interact with web pages through Anchor's cloud-based browsers with built-in proxies, stealth features, and advanced capabilities.

- Node.js 18 or newer
- Anchor Browser API Key(Get one here)
- VS Code, Cursor, Windsurf, Claude Desktop, Goose or any other MCP client

# Clone the repository git clone https://github.com/anchorbrowser/anchor-mcp.git cd anchor-mcp # Install dependencies and build npm install npm run build

- Sign up atanchorbrowser.io
- Get your API key from the dashboard
- Copy your API key (starts withsk-)

{ "mcpServers": { "anchor-browser": { "command": "node", "args": [ "/path/to/anchor-mcp/cli.js" ], "env": { "ANCHOR_API_KEY": "sk-your-api-key-here" } } } }

{ "mcpServers": { "anchor-browser": { "command": "node", "args": [ "/path/to/anchor-mcp/cli.js" ], "env": { "ANCHOR_API_KEY": "sk-your-api-key-here" } } } }

Add to yourclaude_desktop_config.json:

{ "mcpServers": { "anchor-browser": { "command": "node", "args": [ "/path/to/anchor-mcp/cli.js" ], "env": { "ANCHOR_API_KEY": "sk-your-api-key-here" } } } }

After updating the configuration, restart your MCP client (Cursor, VS Code, etc.) to load the new server.

The Browser MCP server supports only essential configuration options:

- --host <host>- Host to bind server to (default: localhost, use 0.0.0.0 for all interfaces)
- --port <port>- Port to listen on for HTTP transport (Docker/server mode)

{ "mcpServers": { "anchor-browser": { "command": "node", "args": [ "/path/to/anchor-mcp/cli.js", ], "env": { "ANCHOR_API_KEY": "sk-your-api-key-here" } } } }

For Docker or headless server environments:

# Run as HTTP server ANCHOR_API_KEY="sk-your-key" node cli.js --port 8931 --host 0.0.0.0

Then configure your MCP client to use the HTTP endpoint:

{ "mcpServers": { "anchor-browser": { "url": "http://localhost:8931/mcp" } } }

Since Anchor Browser handles all the complex browser management remotely, most traditional browser options are unnecessary:

- No browser selection- Anchor uses optimized remote browsers
- No proxy configuration- Anchor provides built-in proxy rotation
- No browser profile management- Handled by Anchor's infrastructure
- No network filtering- Use Anchor's dashboard for advanced controls
- No viewport/device options- Configure these through Anchor Browser API

This keeps the MCP server simple and focused on what matters: connecting to Anchor's remote browser service.
- Browser Session Creation: When you use browser tools, the MCP server calls Anchor's API to create a remote browser session
- Remote Connection: Connects to the remote browser via WebSocket using Chrome DevTools Protocol (CDP)
- Tool Execution: All browser automation happens in Anchor's cloud infrastructure
- Proxy & Stealth: Automatic residential proxy rotation and advanced anti-detection features
- Session Management: Each session is isolated and can be viewed live via Anchor's dashboard

- Automatic residential proxy rotation
- Geo-targeting for different regions
- No proxy configuration needed

- Browser fingerprinting protection
- Anti-bot detection bypass
- Real browser environments

- No local browser dependencies
- Consistent browser versions
- Scalable execution

- Live view of browser sessions
- Session recordings and traces
- Network request logging

The Browser MCP server provides all standard browser automation tools:

- anchor_navigate- Navigate to URLs
- anchor_click- Click elements
- browser_type- Type text into inputs
- browser_snapshot- Get page accessibility tree
- browser_take_screenshot- Take screenshots
- browser_evaluate- Execute JavaScript
- browser_wait_for- Wait for conditions

- browser_tab_new- Open new tabs
- browser_tab_list- List open tabs
- browser_tab_select- Switch between tabs
- browser_tab_close- Close tabs

- browser_file_upload- Upload files
- browser_handle_dialog- Handle alerts/confirms
- browser_network_requests- View network traffic
- browser_pdf_save- Generate PDFs (with--caps=pdf)

Error: Missing ANCHOR_API_KEY environment variable

Solution: Make sure your API key is correctly set in the MCP configuration.

Solution: Make sure you have Node.js 18+ and runnpm installfirst.

Check the MCP logs for Anchor API responses and WebSocket connection status.

Each Anchor API key has session limits. Check your dashboard atanchorbrowser.iofor usage.

# Make changes to TypeScript files in src/ # Then rebuild npm run build # Test your changes node cli.js --help

- Anchor Browser:anchorbrowser.io
- Documentation:Anchor Browser Docs
- MCP Protocol:Model Context Protocol

Retrieve and analyze Claude Code conversation history from local files.