Superpowers Chrome

Why it's ranked here

The appeal is focused control with little setup overhead. Tab indexes hide WebSocket endpoint details, while the MCP surface compresses many browser actions into one tool. Automatic HTML, Markdown, screenshot, console, and DOM-summary captures give agents useful state after changes. Dialog handling also prevents common prompts and device choosers from freezing the session.

What's good

It covers routine browsing without giving up lower-level access. Agents can navigate, wait, click, fill, select, extract content, take screenshots, and send raw protocol commands. Dynamic port allocation reduces local conflicts, named profiles support persistence or deliberate sharing, and separate default profiles let parallel MCP processes control independent Chrome instances. Page prompts become explicit synthetic responses with accept, dismiss, credential, and device controls.

Tradeoffs

Mode changes restart Chrome, reload tabs with GET requests, and lose POST state. They may also create extra blank tabs. A profile cannot change while Chrome is running. Headed Linux and WSL2 sessions require display configuration, while headless containers may need extra Chrome flags. Console capture is described as incomplete. The project itself recommends another automation stack for fresh browser instances, PDFs, and higher-level workflows.

How to use it well

Use it for agent workflows that need persistent browser state, direct tab control, compact MCP context, or inspectable captures after each interaction. Choose the command-line mode for explicit scripting and the MCP mode for clients that benefit from one browser tool. Assign fixed profile names when processes should share Chrome, and separate profiles when isolation matters. Do not treat it as the documented choice for fresh instances, PDF-heavy work, or higher-level automation abstractions.

Observed

License

MIT

Primary language

JavaScript, with TypeScript used for the MCP server source

Runtime

Node.js 18 or newer

Interfaces

Claude Code browsing skill with CLI commands, plus an MCP server exposing one browser tool

Installation surface

Claude Code marketplace plugin, NPX directly from GitHub, or local clone and build

Platform support

macOS, Linux, Windows, WSL2, and container guidance are documented

Dependencies

No runtime dependencies are declared; Biome and jsdom are development dependencies

Testing structure

The package test script runs linting, bundle freshness validation, and Node test files