MCP server that connects AI assistants to Chrome DevTools. Ask your AI to profile a page, find a memory leak, or measure coverage — PEN runs the browser profiling and returns structured results.
Single Go binary. No Node.js. No browser launch. Attach to your dev browser and go.
Install
Quick install (recommended):
MCP server that connects AI assistants to Chrome DevTools.
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/edbnme/pen/main/install.sh | sh
# Windows (PowerShell)
irm https://raw.githubusercontent.com/edbnme/pen/main/install.ps1 | iex
Then run the interactive setup wizard:
pen init
Package managers:
# macOS / Linux
brew install edbnme/tap/pen
# Windows
scoop bucket add pen https://github.com/edbnme/scoop-pen
scoop install pen
Other options:
# Download binary from GitHub Releases (all platforms)
# → https://github.com/edbnme/pen/releases/latest
# Or install with Go 1.23+
go install github.com/edbnme/pen/cmd/pen@latest
Verify it works:
pen --version
More install methods (from source, manual binary setup): docs/INSTALL.md
Quick Start
The fastest way to get going is the interactive setup wizard:
pen init
This auto-detects your environment, lets you pick your IDE and browser, generates the MCP config, and optionally launches your browser with debugging — all in one command.
Manual setup
If you prefer to configure things by hand:
1. Launch a debug browser — PEN can do this automatically:
pen --auto-launch
This detects an installed browser, launches it with a separate debug profile (your existing browser stays untouched), and connects via CDP. No need to close your browser or manage anything manually.
Use --user-data-dir so it doesn't conflict with your existing browser:
macOS:
open -a "Google Chrome" --args --remote-debugging-port=9222 --user-data-dir=/tmp/pen-debug-profile --no-first-run
Verify the debug port is open — visit http://localhost:9222/json in a new tab. You should see a JSON array.
Why --user-data-dir? Chrome's debug port flag is silently ignored when Chrome is already running. --user-data-dir forces a separate instance that works alongside your existing browser.
2. Add PEN to your IDE
VS Code — create .vscode/mcp.json in your project:
New in this release: console.go (real-time console capture via Runtime CDP domain), lighthouse.go (Lighthouse CLI integration), pen_navigate in utility.go (browser navigation control), and pen_trace_insights in cpu.go (offline trace analysis engine).
Security
Localhost only — rejects remote CDP URLs
No browser launch — attaches to existing browser
Eval gated — pen_evaluate needs --allow-eval
Expression blocklist — blocks fetch, document.cookie, eval, etc. even with eval on
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo Pen?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Pen precisa de uma chave de API?
Este registro não lista nenhuma variável de ambiente obrigatória.
Qual transporte Pen usa?
Pen roda localmente via stdio.
Quando Pen foi verificado pela última vez?
Última verificação: 2026-10-28. MCP server that connects AI assistants to Chrome DevTools.