Superpowers Chrome
Direct browser control via Chrome DevTools Protocol. Zero dependencies.
Maintained fork of obra/superpowers-chrome by @cameronsjo.
Two modes: Skill Mode (CLI tool, 17 commands) and MCP Mode (ultra-lightweight MCP server, single use_browser tool).
Installation
/plugin marketplace add cameronsjo/superpowers-marketplace
/plugin install superpowers-chrome@superpowers-marketplace
Quick Start
# Find your plugin installation path (varies by marketplace and version)
# Common locations:
# ~/.claude/plugins/cache/superpowers-marketplace/superpowers-chrome/<version>/skills/browsing
# ~/.claude/plugins/cache/superpowers-chrome/skills/browsing
cd ~/.claude/plugins/cache/superpowers-marketplace/superpowers-chrome/*/skills/browsing
./chrome-ws start # Launch Chrome
./chrome-ws new "https://example.com" # Create tab
./chrome-ws navigate 0 "https://google.com"
./chrome-ws fill 0 "textarea[name=q]" "test"
./chrome-ws click 0 "button[name=btnK]"
Windows tip: The tooling defaults to 127.0.0.1:9222 for DevTools traffic. Override via CHROME_WS_HOST / CHROME_WS_PORT if you forward Chrome elsewhere.
Linux/WSL2 tip: For headed mode (visible browser), the MCP server needs the DISPLAY environment variable. If show_browser doesn't work, configure "env": {"DISPLAY": ":0"} in your MCP server config. See mcp/README.md for details.
Windows Verification (November 7, 2025)
node skills/browsing/chrome-ws start launched Chrome with remote debugging enabled on a fresh Windows 11 Pro install.node skills/browsing/chrome-ws tabs and node skills/browsing/chrome-ws navigate 0 https://example.com confirmed CLI control with the IPv4 default binding.codex exec -c "mcp_servers.superpowers-chrome.enabled=true" "List Chrome tabs via MCP to verify the Windows override patch." listed the Example Domain tab through the MCP server, demonstrating that the overrides also work through Codex.
Commands
- Setup:
start (auto-detects platform)
- Tab management:
tabs, new, close
- Navigation:
navigate, wait-for, wait-text
- Interaction:
click, fill, select
- Extraction:
eval, extract, attr, html
- Export:
screenshot, markdown
- Raw protocol:
raw (full CDP access)
MCP Server Mode
Ultra-lightweight MCP server with a single use_browser tool. Perfect for minimal context usage with automatic page captures.
Installation Options
Option 1: NPX from GitHub (Recommended)
{
"mcpServers": {
"chrome": {
"command": "npx",
"args": [
"github:obra/superpowers-chrome"
]
}
}
}
Option 1b: NPX with Headless Mode
{
"mcpServers": {
"chrome": {
"command": "npx",
"args": [
"github:obra/superpowers-chrome",
"--headless"
]
}
}
}
Option 2: Git Clone + Local Path (Current)
git clone https://github.com/obra/superpowers-chrome.git
cd superpowers-chrome/mcp && npm install && npm run build
{
"mcpServers": {
"chrome": {
"command": "node",
"args": [
"/path/to/superpowers-chrome/mcp/dist/index.js"
]
}
}
}
Auto-Capture Features
DOM-changing actions (navigate, click, type, select, eval) automatically capture:
- Page HTML: Full rendered DOM state
- Page Markdown: Structured content extraction
- Screenshot: Visual page state
- DOM Summary: Token-efficient page structure
- Session Organization: Time-ordered captures in temp directory
Response format:
→ https://example.com (capture #001)
Size: 1200×765
Snapshot: /tmp/chrome-session-123/001-navigate-456/
Resources: page.html, page.md, screenshot.png, console-log.txt
DOM:
Example Domain
Interactive: 0 buttons, 0 inputs, 1 links
Layout: body
Usage
{
"action": "navigate",
"payload": "https://example.com"
}
Get help: {"action": "help"} - Returns complete documentation
See mcp/README.md for complete documentation.
When to Use
Use Skill Mode when:
- Working with Claude Code agents
- Need full CLI control with 17 commands
Use MCP Mode when:
- Using Claude Desktop or other MCP clients
- Want minimal context usage (single tool)
Use Playwright MCP when:
- Need fresh browser instances
- Complex automation with screenshots/PDFs
- Prefer higher-level abstractions
Documentation
License
MIT
Support
cameronsjo
cameronsjo
