browsermcp-skill

# BrowserMCP Skill

This skill enables MCP Clients to automate browser interactions through the BrowserMCP protocol. It leverages a local MCP server and a Chrome extension to control the user's actual browser session, allowing for authenticated actions and bypassing common bot detection.

## Key Features

- ⚡ **Fast**: Automation happens locally without network latency
- 🔒 **Private**: Browser activity stays on the device
- 👤 **Logged In**: Uses existing browser profile with active sessions
- 🥷 **Stealth**: Avoids basic bot detection and CAPTCHAs via real browser fingerprint

## Prerequisites

Before using BrowserMCP automation:

1. **MCP Server**: BrowserMCP server must be running (via npx)
2. **Chrome Extension**: Browser MCP Chrome extension must be installed and connected
3. **Active Tab**: The target browser tab must be connected via the extension

> [!IMPORTANT]
> The AI can only control tabs that are actively "Connected" via the Browser MCP extension. If you switch tabs, you must reconnect the new tab.

## Core Workflow

The standard browser automation process follows an iterative approach:

```mermaid
flowchart TD
    A[Navigate to URL] --> B[Take Snapshot]
    B --> C[Identify Elements]
    C --> D[Interact: Click/Type/etc]
    D --> E[Wait for Changes]
    E --> B
    E --> F[Verify: Screenshot/Logs]
```

### Standard Pattern

| Step | Tool | Purpose | Key Consideration |
|------|------|---------|-------------------|
| **1** | [`navigate`](references/tools.md#browser_navigate) | Open the target URL | Ensure extension is connected first |
| **2** | [`snapshot`](references/tools.md#browser_snapshot) | Capture ARIA tree to identify interactive elements | Refresh after any page changes |
| **3** | [`click`](references/tools.md#browser_click) / [`type`](references/tools.md#browser_type) | Interact with page elements | Use exact `ref` from snapshot |
| **4** | [`wait`](references/tools.md#browser_wait) | Pause for dynamic content to load | Essential after na...