A Rust-native MCP server that gives AI agents full control over a real Chrome browser through the Chrome DevTools Protocol. No browser extensions, no Puppeteer, no Node.js — just a single binary that speaks CDP.
Power your agent
Yayıncıdan kurulum. PlugMCP uç noktası değildir.
Host a copy with our keys and logs.
Registry'de henüz paketlenmiş bir sürüm yok. Deponun README dosyasını izleyin.
Uzak URL mi, yoksa makinenizde bir komut mu? İki kurulum arasındaki fark
PlugMCP’de çalıştır
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
BaşlatYayıncıdan
A Rust-native MCP server that gives AI agents full control over a real Chrome browser through the Chrome DevTools Protocol. No browser extensions, no Puppeteer, no Node.js — just a single binary that speaks CDP.
A Rust MCP server for headless Chrome automation via CDP — built as a Claude Code plugin.
_See dev-browser-eval for methodology. The model used was sonnet 4.5
/plugin marketplace add hkd987/remix-browser
/plugin install remix-browser@hkd987-remix-browser
That's it — the binary downloads automatically on first use. No Rust required.
curl -fsSL https://raw.githubusercontent.com/hkd987/remix-browser/main/scripts/install.sh | sh
git clone https://github.com/hkd987/remix-browser.git
cd remix-browser
cargo build --release
Add to your Claude Code MCP config (~/.claude/mcp.json):
{
"mcpServers": {
"remix-browser": {
"command": "/path/to/remix-browser"
}
}
}
That's it. Claude now has a browser.
{
"mcpServers": {
"remix-browser": {
"command": "/path/to/remix-browser",
"args": ["--headed"]
}
}
}
Chrome 144+ has a built-in toggle that lets any agent connect to your running browser — no extensions needed.
chrome://inspect/#remote-debugging in Chrome{
"mcpServers": {
"remix-browser": {
"command": "/path/to/remix-browser",
"args": ["--cdp-url", "ws://127.0.0.1:9222"]
}
}
}
Or use an environment variable:
{
"mcpServers": {
"remix-browser": {
"command": "/path/to/remix-browser",
"env": {
"CDP_URL": "ws://127.0.0.1:9222"
}
}
}
}
HTTP URLs also work — the WebSocket URL is auto-discovered from /json/version:
CDP_URL=http://127.0.0.1:9222 remix-browser
When connected to an external browser, remix-browser uses your existing tabs and gracefully disconnects on exit without closing Chrome.
For the best experience, add this line to your project's CLAUDE.md (or ~/.claude/CLAUDE.md for all projects):
When I ask to use Chrome or browser automation, use remix-browser MCP tools.
For 1-2 simple actions, granular tools are fine.
For workflows with 3+ actions, loops, or extraction, prefer `run_script`.
Use `fill` for setting any form control — it auto-detects input type (text, select, checkbox, range slider).
Snapshots auto-append after every tool call, so [ref=eN] selectors are always fresh.
This tells Claude to automatically reach for remix-browser whenever you mention browser tasks — no need to say "remix-browser" by name.
navigate -> click -> get_text).run_script for multi-step workflows, loops, and repeated extraction.fill instead of type_text + select_option — it auto-detects the control type (text, select, checkbox, range slider, ARIA slider).[ref=eN] selectors are always available without a separate snapshot call.click, type_text, fill) include auto-wait — they poll up to 5 seconds for the element to appear before acting, eliminating timing errors on dynamic pages.remix-browser exposes a broad toolset organized by category.
All element-targeting tools support three selector strategies:
CSS (default): "button.submit", "#login-form", "div > p:first-child"
Text: "Sign In", "Submit Order", "Click here"
XPath: "//button[@type='submit']", "//div[contains(@class, 'menu')]"
Text selectors use a TreeWalker to find elements by their visible text content — no need to inspect the DOM to find the right CSS class.
Most browser automation tools fail on modern JS-heavy sites. Dropdown menus, overlays, dynamically positioned elements — they all break simple element.click().
remix-browser uses a hybrid click strategy:
mousedown -> mouseup -> click) at the element's coordinatesclick()This means clicks just work — even on sites with complex overlays, sticky headers, dynamic menus, and late-loading elements.
remix-browser automatically finds Chrome on your system:
/Applications/Google Chrome.app, Homebrew paths, Chrome Canary/usr/bin/google-chrome, snap packages, ChromiumFalls back to which google-chrome / which chromium if standard paths don't exist.
--headless=new (Chrome's latest headless implementation)src/
├── main.rs # CLI entry point
├── server.rs # MCP ServerHandler — routes tool calls
├── browser/
│ ├── session.rs # Browser lifecycle management
│ ├── pool.rs # Multi-tab tracking (TabPool)
│ └── launcher.rs # Chrome binary detection & launch config
├── tools/
│ ├── navigation.rs # navigate, go_back, go_forward, reload
│ ├── dom.rs # find_elements, get_text, get_html, wait_for
│ ├── interaction.rs # click, type_text, fill, hover, select_option, press_key, scroll
│ ├── screenshot.rs # screenshot capture
│ ├── snapshot.rs # compact interactive tree + ref generation
│ ├── javascript.rs # execute_js, console log capture
│ ├── network.rs # network monitoring
│ ├── page.rs # tab management
│ └── script.rs # run_script JS engine and page API
├── interaction/
│ ├── click.rs # Hybrid click strategy implementation
│ ├── keyboard.rs # Key press & text input
│ ├── scroll.rs # Scroll logic
│ └── wait.rs # Auto-wait polling for element existence
└── selectors/
├── mod.rs # Selector normalization & :has-text() conversion
├── css.rs # CSS selector resolution
├── text.rs # Text content matching via TreeWalker
├── xpath.rs # XPath evaluation
└── ref.rs # [ref=eN] snapshot reference resolution
Built on:
# Run all 50 integration tests (uses real headless Chrome)
cargo test -- --test-threads=4
# Run a specific test
cargo test test_navigate
Tests use fixture HTML files and spin up isolated Chrome instances with unique profiles — no shared state, no flakiness.
MIT
A Rust MCP server for headless Chrome automation via CDP — built as a Claude Code plugin.
Araçlar
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için stdio yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Bu kayıtta gerekli bir ortam değişkeni listelenmiyor.
Remix Browser yerel olarak stdio üzerinden çalışır.
Son kontrol: 2026-10-28. A Rust MCP server for headless Chrome automation via CDP — built as a Claude Code plugin.