
browsergenie/mcp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
An MCP (Model Context Protocol) server that gives AI models full control over a Chrome browser. It pairs with the BrowserGenie Extension to expose 50+ browser automation tools over stdio —...
概要
An MCP (Model Context Protocol) server that gives AI models full control over a Chrome browser. It pairs with the BrowserGenie Extension to expose 50+ browser automation tools over stdio — navigation, clicking, typing, screenshots, touch gestures, macro recording, and complete DevTools access. This is the server half. The Chrome extension lives in a separate repository. Both are required. The MCP server bridges your AI client (over stdio) and the Chrome extension (over WebSocket). Every MCP tool call is forwarded to the extension, executed in the browser, and the result is returned to the AI client. - Node.js 18+ - npm - The companion extension installed in Chrome — Chrome Web Store | Source No installation required. Run directly from npm: For development or to use the latest unreleased changes: Add the server to your AI client's MCP configuration. File: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) File: %APPDATA%\Claude\claude_desktop_config.
README
以下は原文 README の抜粋です。原文を見る。
BrowserGenie MCP Server
An MCP (Model Context Protocol) server that gives AI models full control over a Chrome browser. It pairs with the BrowserGenie Extension to expose 50+ browser automation tools over stdio — navigation, clicking, typing, screenshots, touch gestures, macro recording, and complete DevTools access.
Two-repo setup: This is the server half. The Chrome extension lives in a separate repository. Both are required.
How It Works
AI Client (Claude, Cursor, etc.)
│ stdio (JSON-RPC / MCP)
▼
MCP Server ◄── this repo
│ WebSocket ws://localhost:7890
▼
Chrome Extension
├── chrome.tabs → Navigation, tab management
├── chrome.debugger → DevTools Protocol (CDP)
├── chrome.scripting → Content script injection
├── chrome.cookies → Cookie management
└── Content Scripts → Real DOM event simulation
The MCP server bridges your AI client (over stdio) and the Chrome extension (over WebSocket). Every MCP tool call is forwarded to the extension, executed in the browser, and the result is returned to the AI client.
Requirements
- Node.js 18+
- npm
- The companion BrowserGenie extension installed in Chrome — Chrome Web Store | Source
Installation
Option A — npx (recommended)
No installation required. Run directly from npm:
npx browser-genie-mcp-server
Or install globally:
npm install -g browser-genie-mcp-server
browser-genie-mcp-server
Option B — Run from source
For development or to use the latest unreleased changes:
git clone https://github.com/BrowserGenie/mcp.git
cd mcp
npm install
npm run build
node dist/index.js
Configuration
Add the server to your AI client’s MCP configuration.
Claude Desktop
File: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
File: %APPDATA%\Claude\claude_desktop_config.json (Windows)
{
"mcpServers": {
"browser-genie": {
"command": "npx",
"args": ["browser-genie-mcp-server"]
}
}
}
Claude Code
File: ~/.claude/settings.json or project-level .mcp.json:
{
"mcpServers": {
"browser-genie": {
"command": "npx",
"args": ["browser-genie-mcp-server"]
}
}
}
Cursor / other MCP clients
{
"mcpServers": {
"browser-genie": {
"command": "npx",
"args": ["browser-genie-mcp-server"]
}
}
}
If you installed the package globally with
npm install -g browser-genie-mcp-server, you can use"command": "browser-genie-mcp-server"with noargsinstead.
After saving the config, restart your AI client.
Environment Variables
| Variable | Default | Description |
|---|
インストール
npx browser-genie-mcp-server設定
{
"mcpServers": {
"browser-genie": {
"command": "npx",
"args": ["browser-genie-mcp-server"]
}
}
}