Direct Chrome control through the use_browser MCP tool: tabs, forms, content extraction
One action-based MCP tool covering navigate/click/type/extract/eval, multi-tab management, dialog handling, console capture, auto-capture of screenshots and DOM, and credential-shaped content redaction
- What
- One action-based MCP tool covering navigate/click/type/extract/eval, multi-tab management, dialog handling, console capture, auto-capture of screenshots and DOM, and credential-shaped content redaction
- Cost
- Free
- Needs
- obra's chrome-ws bridge exposing the mcp__chrome__use_browser MCP tool in the agent's runtime (e.g. Claude Code) — the skill teaches the protocol; the driver must already be installed
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @obra's browsing skill: full control of a real Chrome through a single `use_browser` MCP tool — navigate and wait (elements, text), click/type/select/keyboard interactions, CDP-level mouse (hover, drag-drop, move, scroll) that bypasses synthetic-event detection, file uploads, extraction (markdown/text/html/attributes), `eval` for arbitrary JavaScript, screenshots, multi-tab management with sticky active tabs, headed/headless mode control, profile management with multi-MCP disambiguation, kill/restart lifecycle with auto-restart detection, console logging per tab, and native dialog handling (alerts, basic-auth, permissions, device choosers). Thoughtful safety design: every DOM action auto-captures a screenshot, structured markdown and the DOM for inspection; credential-shaped pages suppress capture and redact secrets in output (overridable via `SUPERPOWERS_CHROME_ALLOW_CREDENTIAL_CAPTURE=1` — leave it off); mode toggles restart Chrome and lose POST state, so they are warned loudly. Honest caveats: it requires the `mcp__chrome__use_browser` MCP server (obra's chrome-ws bridge) installed in the agent's runtime — the skill teaches the protocol, it doesn't install the driver; Playwright MCP remains the better pick for fresh throwaway instances and screenshots/PDFs. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: obra's chrome-ws bridge exposing the mcp__chrome__use_browser MCP tool in the agent's runtime (e.g. Claude Code) — the skill teaches the protocol; the driver must already be installed Install "Direct Chrome control through the use_browser MCP tool: tabs, forms, content extraction" for me. It gives my agent @obra's browsing playbook: one action-based MCP tool for navigate/await/click/type/keyboard/drag-drop/scroll/file-upload/extract/eval, multi-tab management, dialog handling (alerts, basic-auth, permissions), console capture, auto-capture of screenshots + DOM after every action, credential-shaped content redaction, profile and lifecycle management, and common patterns (form fill, multi-tab workflows, dynamic content, responsive testing). MIT licensed. Repository: https://github.com/obra/superpowers-chrome/blob/main/skills/browsing/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "browsing". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. confirm the use_browser MCP tool is available in my agent runtime and announce usage per the skill's rule; keep SUPERPOWERS_CHROME_ALLOW_CREDENTIAL_CAPTURE unset (off); remember that show_browser/hide_browser restarts Chrome and loses POST state — prefer headless). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.