Repository navigation
playwright mcp and captchas
An agent driving a browser meets a challenge and stops. The obvious next thought is that a vision model could just read it. That thought is wrong for reasons worth knowing, and the useful routes past a challenge are not the ones people try first.
Most modern challenges are not an image test. reCAPTCHA v3 and Turnstile in its managed mode present no puzzle at all most of the time. They score the session from signals gathered before and during the page: the address, the connection, how the pointer moved, how quickly the form was filled, whether the browser has a history. A model with perfect vision has nothing to look at, because the decision was already made.
When there is a visible puzzle, the puzzle is the smallest part. The token the server accepts is produced by client-side code that observed the interaction that produced it. Getting the right answer to the question is not the same as having the token issued, which is why "the model can read the letters" does not translate into a working session.
And the challenge is often the symptom. A challenge shown to you and not to your colleague on the same site is a statement about your address and your pacing. Solving it does not change either, so it comes back.
Fix what triggered it. The three levers, in the order they pay:
- The address. A datacenter address is pre-judged. Playwright MCP with a proxy covers the routing and the three leaks that survive it.
- The pacing. Forty pages in forty seconds is not a person.
- The browser. A stock automation build has observable properties that a hand-driven browser does not. This is the axis where engine-modified servers differ, and it is the third of three for a reason: why an agent gets blocked.
Use the sanctioned door. A surprising share of the sites people fight have an API, a data export, or a documented feed. It is faster, it does not break next month, and it is allowed. This is the answer people skip because it feels like giving up, and it is usually the correct one.
Hand the challenge to a person. If the flow is interactive and occasional,
a headed browser where you solve it yourself, once, and then keep the session,
is entirely legitimate. --storage-state on Microsoft's server exists partly
for this shape: solve it in a real browser, save the state, start from there.
invisible_playwright_mcp does not solve captchas, and does not promise non-detection. The engine is a Firefox patched at the C++ source, which changes what a page can observe about the browser. It does not read a challenge, does not fetch a token, and does not repair an address's reputation or an agent's rhythm.
We say this plainly because the category does not. Several MCP servers in this space advertise a bypass of a named challenge product or an AI solver as a headline feature. Those may work; we have not verified them and we do not repeat them as fact. Stealth MCP servers compared names them with the same caveat.
The reason for the restraint is not only honesty. A tool that promises to defeat a challenge attracts people whose actual problem is an address, and it fails them, loudly, in a way that is nobody's fault but the promise's.
Can Playwright MCP solve a captcha? No. It can drive a browser to a page that has one.
Can a vision model solve it? Sometimes it can answer the visible puzzle. That is usually not what the site is measuring, and it is not what issues the token.
Why do I get a challenge every time and my browser does not? Fresh profile, different address, and a rhythm no person produces. In that order of likelihood.
Is there an MCP server that gets past Cloudflare? Several claim it. Treat a claim as a claim, and read Cloudflare and Playwright MCP for what the challenge is reading.
Is it legal to bypass a captcha? Depends where you are and what the site's terms say, and it is a question for the site's terms rather than for us. The practical answer is that a challenge is a site telling you it does not want this traffic, and there is usually a sanctioned route that does not involve arguing with it.
See also: can an AI agent solve a captcha for the category-level answer, Playwright MCP session getting blocked for attributing the failure, and when the agent gets blocked.
-
microsoft/playwright-mcp, retrieved 2026-09-10, for
--storage-stateand the capability model. - The engine wiki's explainers on the challenge products, which describe the mechanisms rather than defeating them.
Written by a project that would sell more if it claimed otherwise. The section saying what invisible_playwright_mcp does not do is the point of the page, not a disclaimer at the bottom of it.
- OpenAI Operator alternatives
- Open-source Operator-style agents
- Is OpenAI Operator still available?
- OpenAI Operator vs Claude computer use
- browser-use alternatives
- Choosing an AI browser agent
- Open-source AI browser agents
- Open-source computer-use agents
- What is an AI web agent?
- AI browser agents vs traditional scraping
- Cloud browser infrastructure for AI agents, explained
- Browserbase alternatives
- Firecrawl vs an AI browser agent
- Skyvern alternatives
- Stagehand vs browser-use
- Project Mariner is gone: what replaced it
- Manus alternatives
- Gemini computer use vs Claude computer use
- A stealth browser MCP, reviewed honestly by its own wiki
- AI browser vs AI browser agent: which one do you want?
- AI browser agent vs RPA: which one fits the job
- AI browser agent vs n8n, Zapier and Make
- Vercel agent-browser alternatives, compared honestly
- What is an agentic browser? Definition and the two kinds
- Open-source agentic browsers: the three layers, compared
- Choosing an MCP server for browser automation: four axes
- Stealth MCP servers compared: Camoufox, nodriver, Patchright
- Playwright MCP alternatives, and the three you don't need
- Autonomous browser agents: the four rungs of autonomy
- What is actually free in the AI browser agent stack
- browser-use on GitHub: what the repo actually gives you
- Playwright MCP vs Chrome DevTools MCP: different jobs
- How to choose among MCP servers: a map by category
- Which MCP servers are worth adding to Claude Code
- MCP on GitHub: finding servers and judging them fast
- MCP vs an API: the decision, and what the wrapper costs
- MCP alternatives: when the protocol is the wrong shape
- Why does my AI agent get blocked?
- The timing signal AI agents give off
- Agent retry loops trip rate limits, not fingerprints
- Claude computer use detected as a bot
- browser-use getting blocked: what you can and cannot change
- Playwright MCP session blocked: four causes, four fixes
- Playwright MCP and captchas: what actually gets you past
- Cloudflare and a browser MCP server: what is being read
- Can an AI agent solve a captcha? The honest answer
- Getting an AI agent to fill out forms
- The best model for an MCP browser agent, and what it really costs
- Browser problem or model problem?
- How to use a Playwright MCP server with Claude Code
- Extracting data to a CSV with an AI agent
- Monitoring a page for changes with an AI agent
- How to let Claude Desktop control a browser
- How to add a browser to Cursor as an MCP server
- Using an AI agent to hunt for apartments
- Getting website data into Google Sheets with an AI agent
- Using an AI agent to download invoices from portals
- AI agents for web research
- Using an AI agent to test your own website
- How to add a browser to Cline as an MCP server
- Posting to social media with an AI agent
- Posting to Facebook with an AI agent
- Posting to Instagram with an AI agent
- Posting to X with an AI agent
- Automating LinkedIn posts: read this first
- Appointment bots: what they are and what an agent can legitimately do
- Track prices across sites with an AI agent
- Build a lead list with an AI browser agent
- Run an AI browser agent on a schedule
- AI browser agent with a local LLM: what changes
- Should you log your AI agent into your accounts?
- How to write a task an AI browser agent can follow
- Move data between two web apps with an AI agent
- The MCP server
- How the tools are shaped, and why
- Playwright MCP vs the Playwright CLI: which fits when
- Playwright MCP: browser is already in use, and the fix
- Playwright MCP best practices: four decisions that matter
- Playwright MCP with a proxy, and the three leaks it leaves
- A browser MCP server in GitHub Copilot: setup and limits
- Using a browser MCP server for web scraping: the pattern
- Which LLM for browser automation: the four properties
- How to build a browser agent, and what to take instead
- Getting an AI agent to log into a website: three routes
- MCP tools, resources and prompts: who controls each
- How many MCP tools is too many? The context arithmetic
- How to build an MCP server: the decisions, not the scaffold
- Local or remote MCP server: what changes, and what does not
- Writing an MCP client in Python: the thirty-line version
- Self-hosted AI agent: what one actually costs to run
- How long an AI browser agent takes per step, measured
- Text, HTML, snapshot or screenshot: what the agent should read
- Giving an AI browser agent a stopping condition
- Keeping an AI browser agent out of destructive actions
- Why did the AI agent click the wrong thing
- When the page changes under the AI agent
- Running one AI agent task across a list of sites
- Seeing a page as it appears in another country
- Getting data out of a dashboard with no export button
- Two browsers in one session: main and support
- Finding the dead links on a site with an AI agent
- Filling a CRM record from a company's website
- One form submission per spreadsheet row, with an AI agent
- Dated screenshots of a page as evidence
- Checking order and delivery status with an AI agent
- Reading a PDF that opens inside the browser
- Summarising a long page or thread with an AI agent
- Collecting every image on a page with its caption
- Collecting event and course listings with an AI agent
- Cancelling a subscription with an AI agent
- What an AI agent can and cannot do inside an iframe
- Shadow DOM and an AI agent: you can click it, you cannot read it
- How to add a browser to Codex as an MCP server
- What a page snapshot costs, per control
- How to let Gemini CLI use a browser
- Native selects and the ones that only look like selects
- Clicking by selector or by coordinates
- How long the agent waits before it gives up
- What a second browser costs
- Uploading a file with an AI agent, and why this one cannot
- Watching the agent work, and when it is worth it
- When not to use an AI browser agent
- Agent or script: deciding once instead of every time
- Using the keyboard instead of the mouse
- Secrets in an agent task: where they end up
- What an agent run should log
- Deduplicating what an AI agent collects
- Normalising values across sites
- Validating an AI agent's output
- Reading a table with an AI agent
- Driving a site's own search and filters
- The task works headed and fails headless
- How to let the AdaL CLI use a browser