Lets AI agents create managed cloud browser sessions to navigate pages, inspect content, and interact with elements remotely.
Also known as Azure/playwright-workspaces, playwright-workspaces
- Stars
- 16
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.1
- Last commit
- Oct 27, 2026
- License
- MIT
What is Playwright Workspaces MCP?
Playwright Workspaces lets AI agents create managed cloud browser sessions to navigate pages, inspect content, and interact with elements remotely.
Summary generated from the project's README
About Playwright Workspaces MCP server
Enabling AI agents to interact with live web content through managed cloud browser sessions is the primary function of Playwright Cloud Browsers. This remote MCP server allows agents to navigate pages, inspect content, and interact with elements without requiring any local installation of Playwright or browser binaries. It operates over Streamable HTTP, making it accessible to clients like VS Code or the GitHub Copilot app through their respective MCP configuration settings.
To use this service, developers must have an Azure subscription and a Playwright workspace with a specific workspace ID and region. Authentication relies on Microsoft Entra ID with OAuth discovery, and the connected identity requires specific workspace RBAC access. This preview version provides a way for agents to perform web tasks remotely by connecting to a workspace-specific endpoint, handling the underlying infrastructure and browser complexity on behalf of the user.
What you can do with it
- 1Remote web page inspectionAsk an AI agent to open a specific website and report back the main heading found on the page.
- 2Automated element interactionDirect an agent to navigate through a web application and interact with various UI elements.
- 3Cloud-based browser testingUse managed cloud browsers to run and scale web tests across different operating systems and browsers.
Written from the project's README. Every use case is checked against a quote from it.
How to install Playwright Workspaces MCP
Playwright Workspaces gives each account its own endpoint, so there is no address to copy here. Get yours from the provider, put it in place of the part in braces, and add it to your client as a remote server.
https://{region}.mcp.playwright.microsoft.com/playwrightworkspaces/%7BworkspaceId%7D/mcp
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableazure/playwright-workspaces is public and reachablegithub.com/azure/playwright-workspaces ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-27github.com/azure/playwright-workspaces ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeEndpoint did not answer initialize: unreachableFinding
README
View on GitHubPlaywright Workspaces
✅ Playwright Workspaces is now Generally Available!
Playwright Workspaces is a fully managed service for end-to-end web testing, built on top of Playwright. With Playwright Workspaces, you can significantly speed up test execution by running tests in parallel using managed cloud-based browers. The service takes care of the underlying infrastructure and complexity, allowing you to validate your web app across major browsers on both Linux and Windows—so you can ship features faster and with greater confidence.
👉 Get started with the Quickstart
Documentation
The full documentation is now available on learn.microsoft.com
There you’ll learn how to:
- Run and scale Playwright tests in the cloud
- Optimize test suite performance and reliability
- Test across multiple browsers and operating systems
- Set up secure, region-aware test environments
- Integrate with CI/CD
Playwright Cloud Browsers remote MCP (preview)
The Playwright Cloud Browsers remote MCP server gives AI agents managed cloud browsers over Streamable HTTP. Agents can create a browser session, navigate and inspect pages, interact with elements, and close the session without installing Playwright or a browser locally.
The remote MCP server is in preview, separately from the generally available Playwright Workspaces service. Preview features do not have a service-level agreement and are not recommended for production workloads.
Prerequisites and authentication
You need an Azure subscription, a Playwright workspace with access to the remote MCP preview, its region and workspace ID, and an identity with permission to use browser sessions in that workspace.
Use the endpoint for your workspace's region:
https://<region>.mcp.playwright.microsoft.com/playwrightworkspaces/<workspace-id>/mcp
Replace both placeholders with your workspace values. Use Microsoft Entra ID with a client that supports OAuth discovery. The server publishes protected-resource metadata; your signed-in identity must also have the required workspace RBAC access. See the authentication and setup guide for permissions and supported compatibility options. Never commit access tokens or paste them into prompts.
Connect from VS Code or the GitHub Copilot app
- VS Code: Run MCP: Add Server from the Command Palette, select HTTP, enter the resolved workspace endpoint, and choose a configuration destination. Follow the server trust and Microsoft Entra sign-in prompts. See Add MCP servers in VS Code.
- GitHub Copilot app: Open Customize > MCP, add a custom server using the resolved workspace endpoint, and follow the supported authentication prompts. See Configuring MCP servers.
With the server connected, ask the agent to create a browser session, open
https://example.com, report the page's main heading, and close the session,
including on failure. Inspect the actual MCP tool calls and outputs to verify
the connection. See the service guide for session
limits, supported tools, and troubleshooting authentication, timeouts, and
expired sessions. Report service issues through this repository's
issue tracker.
Registry metadata
The server is published as com.microsoft/playwright-cloud-browsers in the
Official MCP Registry.
The root server.json is a public copy of the published
metadata. Publication and metadata updates are managed by the service team;
changing this copy does not publish an update or establish a listing in
downstream client catalogs.
Samples
Explore sample projects for different test runners:
- Playwright Test with JavaScript/TypeScript
- NUnit with C#
- Python
- Playwright Library projects
- Foundry Prompt Agents using Playwright Workspaces Remote MCP
- Foundry Hosted Agents using Playwright Workspaces Remote MCP
- App Verification Skills (verify skill)
Migrating from Microsoft Playwright Testing
- See the Migration Guide and Troubleshooting Tips
Issues
To report a bug, request a feature, or ask for a quote limit increase, please use the Issues section of this repository.
More Resources
Playwright Workspaces MCP questions
What is the Playwright Cloud Browsers MCP server?
It is a remote MCP server that gives AI agents managed cloud browsers over Streamable HTTP, so agents can create sessions, navigate and inspect pages, and interact with elements without installing Playwright locally.
How do I authenticate to the Playwright Workspaces MCP server?
You use Microsoft Entra ID with a client that supports OAuth discovery, and your signed-in identity needs the required workspace RBAC access.
What endpoint do I use to connect?
Use the regional endpoint for your workspace, replacing the region and workspace ID placeholders.
Is the remote MCP server ready for production?
No. The remote MCP server is in preview, has no service-level agreement, and is not recommended for production workloads.
How do I add the server in VS Code?
Run MCP: Add Server from the Command Palette, select HTTP, enter your workspace endpoint, then follow the trust and Microsoft Entra sign-in prompts.