@kiro-paradigm/browser
v0.1.0
Published
MCP server providing Chrome DevTools Protocol (CDP) browser automation — connects to an already-running Chrome instance when Playwright MCP cannot launch
Maintainers
Readme
Browser Power for Kiro
A Kiro power providing browser automation with a CDP fallback MCP server.
What's Included
| Component | Purpose |
|-----------|---------|
| .kiro/powers/browser/ | Kiro power (Playwright + CDP + Chrome DevTools MCP servers) |
| src/ | CDP fallback MCP server (@renfeng/kiro-browser-alternative) |
MCP Servers
- Playwright (enabled) — Full browser automation via
@playwright/mcp - alternative (enabled) — Fallback for when Chrome is already running with the same user data directory
- Chrome DevTools (disabled) — Alternative via
chrome-devtools-mcp
Quick Start
As a Kiro Power
- Clone this repo
- In Kiro, open Command Palette → "Powers" → "Add power from Local Path"
- Select the
.kiro/powers/browserdirectory
As a Workspace Root
Add to your .code-workspace:
{ "name": "browser", "path": "../browser-kirospace" }The power at .kiro/powers/browser/ is auto-discovered.
CDP Fallback
When Playwright fails with "Opening in existing browser session", the alternative server auto-discovers the running Chrome's CDP port and connects directly. Tools:
cdp_list_tabs— List open tabscdp_navigate— Navigate a tab to a URLcdp_screenshot— Capture viewport as PNGcdp_evaluate— Run JavaScript in a tabcdp_reload— Reload a tab
Development
npm install
npm run build
npm testLicense
MIT
