Repository navigation
playwright mcp blocked
"Blocked" covers four failures that look the same from inside a chat window and need completely different responses. Getting the attribution right is most of the work, because three of the four are not detection at all.
The snapshot is empty or missing what you can see in a browser. Not blocked. The page rendered its content after the snapshot was taken, or the content is inside an iframe the snapshot did not descend into, or it is drawn on a canvas that has no accessibility representation. Ask for the snapshot again after the page settles, or take a screenshot and compare: if the screenshot has the content and the tree does not, this is your case.
A page that says something about verifying you are human. A challenge. This is a judgement made mostly before your page interaction, on the address and the connection. Cloudflare and Playwright MCP covers what one is actually reading.
It worked for a while and then stopped. A rate limit, almost always. The signature is that it is time-based rather than immediate, and that waiting fixes it. No browser setting reaches this. Slow down.
It fails immediately, on the first request, from this machine only. Now you have a candidate for either the address or the browser. Those two are separable and the next section separates them.
Run the same page from the same machine in an ordinary browser you use by hand.
- The hand browser is fine, the agent is not: the browser is a candidate. Same address, different result.
- Both are refused: the address. Nothing about your server or engine matters yet, and switching servers will waste a day.
Then run the agent from a different network, a phone hotspot is enough.
- Different network, works: confirmed address.
- Different network, still refused: now it is the browser or the pacing.
This costs ten minutes and is the difference between fixing the problem and switching tools at random. Why an agent gets blocked has the longer version of the same reasoning.
Address. A proxy, and the type matters: Playwright MCP with a proxy, including the three leaks that a proxy does not close by itself.
Pacing. Fewer actions per minute, and pauses that are not identical. An agent under a model is naturally slower than a script, which helps, but a model told to check forty pages will do it in a rhythm no person has.
The browser. This is the one where the server choice matters, and only here. A stock automation build is a specific set of observable choices that no flag changes. Engine-modified alternatives exist and stealth MCP servers compared lists them, along with the claims among them that we could not verify.
The snapshot. Not blocked. Read again, or screenshot.
A challenge you are meant to solve interactively stays a challenge. This project does not solve captchas and does not claim non-detection: can an AI agent solve a captcha is the direct answer, and it applies to every tool in this category regardless of what its README says.
If a site is refusing an agent deliberately and consistently, that is a decision the site made. The useful question at that point is whether the data is available another way, not which server to try next.
Why does Playwright MCP get blocked and my normal browser does not? Usually not the same test. Your normal browser has history, a profile and a session; the agent's is fresh. Sometimes it is the address. Occasionally it is the automation build.
Does --isolated make blocking worse? It can. A profile with no history is
one more thing that is unusual, though far less decisive than the address.
Will a different MCP server fix it? Only if the browser was the cause, which is the least common of the four. Attribute first.
Is a headless browser more likely to be blocked? Headless is detectable in its own right, and running headed costs you nothing on a desktop. Try headed before concluding anything.
Why does it work locally but fail on the server? The classic case, and it is the machine and the address rather than the code: no GPU, a container font set, a datacenter address.
See also: when the agent gets blocked, browser-use getting blocked, and Claude computer use detected as a bot.
- microsoft/playwright-mcp, retrieved 2026-09-10, for the snapshot model and the isolation options.
- The engine wiki's how to test bot detection for running the comparison yourself.
Written while maintaining a server whose differentiator is the browser. The page puts the browser fourth out of four causes, because that is where it belongs by frequency.
- 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