Drive stealth browser automation from agents with Invisible Playwright MCP
Use Invisible Playwright MCP when an agent needs a self-hosted browser automation runtime for permitted web research, scraping, form navigation, and computer-use workflows that must run through a real headed browser.
npx skills add agentskillexchange/skills --skill drive-stealth-browser-automation-from-agents-with-invisible-playwright-mcp
codex plugin marketplace add feder-cr/invisible_playwright_mcp and codex plugin add invisible-playwright-mcp@feder-cr. For standalone UI usage, run uvx invisible-playwright-mcp ui --openrouter-key sk-or-....Invisible Playwright MCP is a Python MCP server and agent plugin that gives coding agents a browser automation runtime built on an undetected Firefox/Playwright stack. Use it when an operator wants an agent to drive a real browser for bounded web research, data extraction, lead research, job-search workflows, or UI navigation where an API is unavailable and the task benefits from browser state, pointer movement, profile persistence, proxy control, or supervised review. The scope boundary is the repeatable agent workflow: install the MCP/plugin, connect a supported agent, provide a permitted browsing task, let the agent operate the browser, and review the resulting findings or artifacts. It is not a general browser, scraping platform, or invitation to bypass site rules; keep usage to authorized automation, respect terms, and avoid credential, paywall, or abuse workflows.
What this skill actually does
Inputs and prerequisites: Invisible Playwright MCP, uv/uvx, MCP-capable assistant or supported plugin host such as Claude Code, Codex, or Gemini CLI.
Setup notes: Install uv, then add the upstream plugin to a supported agent, for example codex plugin marketplace add feder-cr/invisible_playwright_mcp and codex plugin add invisible-playwright-mcp@feder-cr . For standalone UI usage, run uvx invisible-playwright-mcp ui –openrouter-key sk-or-… .
Source and verification boundary: use https://github.com/feder-cr/invisible_playwright_mcp/wiki as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.