Start by checking the connection between the Playwright MCP server and the Chrome profile that has the Playwright MCP Bridge extension. Run the server with --extension, set PLAYWRIGHT_MCP_EXTENSION_TOKEN to the current token from that same profile, then restart the MCP client and try a browser tool. If it still shows “No MCP clients are currently connected,” check for a stale process, mismatched extension and server versions, or Chrome opening a different profile than the one inspected.
What the message means
The status indicates that the Playwright MCP Bridge extension has not completed its connection to the Playwright MCP server. It does not, by itself, tell you which part is at fault. The server may be running while the extension is disconnected, so a browser tool call can wait and then fail with an extension connection timeout.
A report in Microsoft’s Playwright MCP GitHub issue #1571 described a server running with a matching PLAYWRIGHT_MCP_EXTENSION_TOKEN while the extension continued to show the disconnected status. A separate reproduction repository, crawled September 29, 2026, records a browser_navigate call timing out with the same general symptom. Those reports establish that the message can persist despite a running server; they do not establish one universal cause.
Use a known-good extension configuration
First verify the server command and environment in the MCP client configuration. The configuration below follows the pattern shown in the Playwright issue report and the Test-Lab.ai guide published August 4, 2026. Replace the token placeholder with the current token shown by your extension; do not paste the placeholder literally.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors#1 Best Overall
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest", "--extension"],
"env": {
"PLAYWRIGHT_MCP_EXTENSION_TOKEN": "PASTE_CURRENT_EXTENSION_TOKEN_HERE"
}
}
}
}Keep the JSON syntax valid for your client’s configuration file. If you already have an mcpServers object, add or update the playwright entry rather than replacing unrelated server entries. The essential details for extension mode are the --extension argument and the token in the server’s environment.
- Open the Chrome profile that contains the extension. Confirm that the Playwright MCP Bridge extension is installed and open its UI to read the current token.
- Update the client configuration. Use that profile’s token for
PLAYWRIGHT_MCP_EXTENSION_TOKENand confirm that--extensionappears in the Playwright server arguments. - Save and restart the MCP client. A restart makes the client launch the server with the updated arguments and environment. If the client has a reload or restart action for MCP servers, use it; otherwise fully quit and reopen the client.
- Try a browser action. Invoke a browser tool such as
browser_navigate, then check whether the extension reports an active client.
Fix the common causes in order
Wrong Chrome profile or stale token
The extension token is profile-specific, according to the Test-Lab.ai guide. A token copied from one Chrome profile will not pair with an extension running in another. Open the profile you intend to use, copy the token currently displayed there, and replace any older token in the MCP client environment. If you have reinstalled or reset the extension, fetch the token again rather than assuming the old one remains valid.
Extension mode is missing
Check the actual server arguments loaded by the MCP client, not just a separate terminal command or an unsaved edit. If --extension is absent, the server is not being started in the extension mode described by the setup guide. Add it to the arguments array, save the configuration, and restart the client.
The client or server is still using old settings
A configuration change does not help a server process that was started before the change. Quit and relaunch the MCP client, and stop duplicate or stale Playwright MCP processes before retrying. If you are unsure whether a process is stale, close the client that launched it and verify that the old server has exited before starting a fresh session.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Extension and package versions have drifted
If the connection stopped working after an update, check whether the extension and @playwright/mcp package changed at different times. The Test-Lab.ai guide identifies version drift as a common failure category, but the available reports do not specify a single universally compatible version pair. Update the components together where possible; if that is not practical, pin a version combination known to work in your environment and record it so later updates can be tested deliberately.
Chrome launches a different profile
A Playwright issue, #41916, documents a possible profile-selection mismatch: a preflight check found the extension in one profile, but Chrome was later launched without an explicit selection of that profile. The issue author tied that behavior to a possible disconnected state. Treat this as a plausible explanation, not a confirmed cause for every case. If the extension appears installed but never activates, check which Chrome profile the launched browser actually uses and compare it with the profile from which you copied the token.
Separate a bridge failure from a server failure
When a call hangs, inspect the extension status page and, if you are comfortable with browser developer tools, the extension service-worker console and network activity. Also check whether the MCP server process is still running and listening on its expected socket. In issue #41916, the report described a listening server but no extension runtime activity, evidence that helped narrow attention to the bridge or profile path rather than a completely absent server.
- Server is not running: inspect the MCP client’s server startup output and correct the command, package resolution, or configuration error before investigating the extension.
- Server is running, extension shows disconnected: re-check the profile, token, extension mode, and launched Chrome profile.
- Extension shows active, but a browser call still fails: test a simple navigation again after a clean restart and note the exact tool error. The disconnected status and a later page-navigation failure are different observations; do not treat them as proof of the same fault.
- No useful extension activity appears: check that the intended profile is open and that the installed extension is enabled there. A server process alone does not establish that the extension handshake succeeded.
The reports available for this issue are issue reports and a reproducible repository, not a measured failure-rate study. Microsoft’s issue #1571 was closed without a root cause, despite a report of a running server, matching token, and timeout. The profile-launch explanation in issue #41916 is code-backed by its author’s report, but it is not established as the explanation for all users.
When extension mode is the wrong fit
Use the local extension route when the task depends on the existing browser profile or its logged-in state. Before switching approaches, decide whether your task truly needs that state, whether it can run repeatably in a clean browser context, how much profile and token upkeep is acceptable, and whether sending the relevant page or data to a hosted service is acceptable for your use case.
If your goal is specifically to capture website screenshots rather than control the current Chrome session, try ScreenshotNeo first as a separate hosted screenshot workflow. It is not a repair for the Playwright MCP Bridge handshake and does not use the local Chrome profile. It may fit when a URL-based screenshot is enough and you want to avoid maintaining the extension-token connection.
Or skip the browser setup
For a URL-based screenshot, ScreenshotNeo takes a GET request and returns an image or PDF. Its API can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Its response identifies page verdict and billing status in headers: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. An MCP server exposes take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpReplace the example target URL with the page you want to capture and use your API key. The call saves the response as shot.webp.
Recommended Free Tools
Python
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo also supports full-page screenshots with lazy images loaded, CSS-selector element captures, dark mode, device and viewport settings, retina scale, PDF page settings, HTML/CSS capture, custom CSS or JavaScript, clicks, waits, request blocking, custom headers and cookies, timezone and geolocation, resizing, caching, signed image links, asynchronous jobs, webhooks, batches of up to 100 URLs, a usage API, and an OpenAPI specification. Parameters used by other screenshot APIs also work, which can ease migration. These are screenshot-capture controls, not a way to attach to an already authenticated local Chrome session.
All features are available on every plan: Free includes 1,000 screenshots per month with no card; Starter is $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free. To try the hosted screenshot workflow, sign up for 1,000 free screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
