Superpowers Chrome plugin
A Claude Code plugin that drives your Chrome over the DevTools Protocol: tabs, forms, page extraction and screenshots with no third-party dependencies
- 362 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent acts in a live Chrome with your signed-in sessions: it clicks, fills forms and runs JavaScript with the eval command
- Screenshots, HTML and console output of pages are saved to disk, and pages can hold personal data and secrets
- Chrome opens a debugging port on the local address 127.0.0.1 that any program on the machine can connect to
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/superpowers-chromeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent acts in a live Chrome with your signed-in sessions: it clicks, fills forms and runs JavaScript with the eval command
- Screenshots, HTML and console output of pages are saved to disk, and pages can hold personal data and secrets
- Chrome opens a debugging port on the local address 127.0.0.1 that any program on the machine can connect to
This is third-party code. Review the repository files before installing.
What it does
Superpowers Chrome gives Claude Code control of the Chrome browser over the DevTools Protocol. The plugin has two modes. In skill mode the agent runs 17 chrome-ws commands: it opens tabs, navigates, clicks, fills forms, picks list values, pulls out text, attributes and HTML, takes screenshots and saves a page as markdown. In MCP mode the same set is available through a single use_browser tool for any MCP client. Tabs are addressed by index (0, 1, 2) instead of long WebSocket URLs. After every DOM action the plugin saves a screenshot, markdown, the page HTML and the console output into the session directory. The agent sees alert, confirm and prompt dialogs, permission requests and USB device pickers as an ordinary response and closes them with click dialog::accept and dialog::dismiss. Chrome starts on its own on a free port in the 9222–12111 range.
Who it is for. For developers and testers who want Claude Code to work in an already running Chrome with signed-in sessions, several tabs and forms.
Good fit when
- The agent needs Chrome with your signed-in session and you do not want to log in to the service again
- You need to work across several tabs: open one, fill in a form, go back to another
- Playwright MCP is unavailable or too heavy for the job
- You want to pull text, attributes or HTML from a page and save it as markdown
- A page throws an alert or a permission prompt and the agent has to dismiss it with a command
Not a fit when
- You need a clean fresh browser instance: SKILL.md points to Playwright MCP for that
- You need PDFs and screenshots at a higher level of abstraction: SKILL.md again sends you to Playwright MCP
- You use another browser: the plugin drives Chrome only
- You need production-grade automation: the author calls the plugin a beta and says it is very lightly tested
Example request
Open the admin panel in a second Chrome tab, fill in the new project form and save the result page as markdownLimitations
The author marks the plugin as BETA and very lightly tested. You need Chrome and Node.js installed: the MCP server starts with node or through npx. On Linux and WSL2 a visible browser window needs the DISPLAY variable for the MCP server, in a container or as root the Chrome sandbox is switched off automatically, and headless runs use CHROME_EXTRA_ARGS. The author verified startup on Windows 11 in November 2025.
DevTools listens on 127.0.0.1 by default. CHROME_WS_HOST and CHROME_WS_PORT change the address and port.
How to disable. Remove the plugin from the /plugin menu in Claude Code. If you wired MCP by hand, delete the chrome entry from the client config. Chrome profiles and their meta files live in ~/.cache/superpowers/browser-profiles/ and the directory can be deleted by hand.
FAQ
How do I install Superpowers Chrome in Claude Code?
Run two commands: /plugin marketplace add obra/superpowers-marketplace and /plugin install superpowers-chrome@superpowers-marketplace. In skill mode the chrome-ws commands sit in the skills/browsing folder of the installed plugin, and ./chrome-ws start launches Chrome.
How do I connect Superpowers Chrome to another MCP client?
Add a chrome server to the config with the npx command and the argument github:obra/superpowers-chrome. Add --headless to run without a window. The author also checked MCP mode through Codex.
What does the plugin write to disk?
After each DOM action it writes a screenshot, markdown, HTML and the browser console into the session directory. If a page shows tokens or keys, no files are created and values in responses are replaced with a REDACTED marker. A secret revealed by a show button is not recognized, so call pause_capture before it.
How is Superpowers Chrome different from Playwright MCP?
SKILL.md gives it the job of working with already open signed-in sessions and several tabs. It recommends Playwright MCP for fresh browser instances, PDFs and screenshots at a higher level.
How do I run several Chromes in parallel?
Since version 3.0 the bridge separates MCP servers by profile on its own: the first claims superpowers-chrome on port 9222, the next falls through to superpowers-chrome-2 on 9223 and so on, each with its own Chrome. To make several processes share one Chrome, set the profile with CHROME_WS_PROFILE.
Discussion
No questions or reviews yet.
Related
PluginsA skill for Amp, Claude Code and Cursor: the agent drives your live Chrome with its open tabs and signed-in accounts through a single debugging toggle
A Python Chrome MCP: the agent connects to Chrome over the DevTools Protocol, reads network, console and cookies, runs JavaScript and takes page metrics
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A CLI, skill and MCP server for driving Chrome with short Puppeteer scripts, with tabs that keep state between calls
A skill and CLI from Browser Use: the agent drives your real Chrome over the DevTools Protocol, logged in as you, and writes any missing helper itself
The cdp skill: an agent drives your Chrome straight through the DevTools protocol, with 652 typed methods and no ready-made click or goto helpers
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Superpowers Chrome (this entry) | no | 362 | ||
| Chrome DevTools MCP | yes | not required | 54,001 | the official MCP server from the Chrome DevTools team, focused on network, console and performance traces |
| Chrome MCP Server | no | not required | 12,502 | a Chrome extension with an MCP server that also works with bookmarks and history |
| Playwright MCP | yes | not required | 38,551 | the Microsoft MCP server on Playwright, fresh browser instances driven by the accessibility tree |
README in short
The description opens by contrasting the two modes, skill and MCP, and lists the features: zero dependencies, a built-in WebSocket, tab addressing by index and 17 commands. It goes on to marketplace installation, a chrome-ws quick start, rules for ports and profiles, Windows and Linux tips, the Windows 11 verification and dialog handling with a table of dialog::* selectors. It ends with the MCP server section, which has the single use_browser tool and launch options through npx or from a cloned repository.