Browser Control MCP — Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Browser extension + MCP server that lets AI agents drive your real Firefox browser with DOM access.
Maintained by eyalzh (community)
Written in TypeScript
286+ GitHub stars at last check
Open source on GitHub

Live-Demo

In der Praxis

browser-control-mcp.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "browser-control-mcp": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/eyalzh/browser-control-mcp"
      ]
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "browser-control-mcp": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/eyalzh/browser-control-mcp"
      ]
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "browser-control-mcp": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/eyalzh/browser-control-mcp"
      ]
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "browser-control-mcp": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/eyalzh/browser-control-mcp"
      ]
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "browser-control-mcp",
      "command": "TODO",
      "args": [
        "See README: https://github.com/eyalzh/browser-control-mcp"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "browser-control-mcp": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/eyalzh/browser-control-mcp"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add browser-control-mcp -- TODO 'See README: https://github.com/eyalzh/browser-control-mcp'

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: Browser Control MCP

Use Browser Control MCP for its primary workflow

👤 Developers using AI coding agents ⏱ ~10 min beginner

Wann einsetzen: You need the capability: Browser extension + MCP server that lets AI agents drive your real Firefox browser with DOM access.

Voraussetzungen

MCP server installed — See https://github.com/eyalzh/browser-control-mcp for install instructions

Ablauf

Install

Install Browser Control MCP following the README at https://github.com/eyalzh/browser-control-mcp✓ Kopiert

→ MCP server appears in your client's available tools/skills
Invoke

Use Browser Control MCP to complete the task described in its docs.✓ Kopiert

→ Agent calls the relevant tool/skill and returns a result

Ergebnis: Working integration with the capabilities advertised by the project.

Fallstricke

README is the source of truth; details here may lag upstream — Check https://github.com/eyalzh/browser-control-mcp for the latest setup steps and tool list

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen