Browser MCP is a browser automation server that enables AI assistants to interact with web pages through Anchor Browser's cloud-based infrastructure, eliminating the need for local browser installations. Key features include: - Remote browser execution via Anchor Browser's cloud service with Playwright integration - Built-in residential proxy rotation and geo-targeting capabilities - Advanced anti-detection and stealth features to bypass bot detection systems - Structured data access using Playwright's accessibility tree rather than pixel-based screenshots - Deterministic tool execution that operates without vision models - Seamless integration with VS Code, Cursor, Claude Desktop, and other MCP clients

Browser MCP Server

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

Key Features

Requirements

Getting Started

1. Clone and Build

Since this is a custom Browser MCP server, you need to build it locally:

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

2. Get Your Anchor API Key

1. Sign up at anchorbrowser.io 2. Get your API key from the dashboard 3. Copy your API key (starts with sk-)

3. Configure MCP Client

#### Cursor

Add to your ~/.cursor/mcp.json:

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

#### VS Code

Add to your MCP configuration:

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

#### Claude Desktop

Add to your claude_desktop_config.json:

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

4. Restart Your MCP Client

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

Configuration Options

The Browser MCP server supports only essential configuration options:

node cli.js --help

Available Options:

Example with Options:

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

HTTP Server Mode (Docker):

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"
    }
  }
}

Why So Few Options?

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

This keeps the MCP server simple and focused on what matters: connecting to Anchor's remote browser service.

How It Works

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

Benefits Over Local Browsers

🌐 Global Proxy Network

🛡️ Advanced Stealth