Playwright Cloud Browsers

com.microsoftPublished by microsoft.comOfficial publisherv1.0.1Updated Oct 29, 2026

Managed Playwright cloud browsers for scalable browser automation and AI agent workflows

The publisher's own server: Microsoft Learn MCP

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Remote MCP server giving AI agents managed Playwright cloud browsers to create sessions, navigate and inspect pages, and interact with elements.

What you can do
  • Create and close managed cloud browser sessions over Streamable HTTP
  • Navigate to pages and inspect their content, such as reporting a page's main heading
  • Interact with page elements inside a session
  • Run browser work without installing Playwright or a browser locally
  • Underpin end-to-end web testing and AI agent workflows on managed cloud browsers
When to use it
Useful when an agent needs to drive a real browser in the cloud for page inspection, element interaction, or web app verification, and you already have a Playwright workspace. It avoids local browser installs and suits CI or agent workflows that need managed, region-aware browsers.
Requirements
A remote endpoint at the workspace's region, including the workspace ID in the path. An Azure subscription, a Playwright workspace with access to the remote MCP preview, and an identity with workspace RBAC permission to use browser sessions. Authentication uses Microsoft Entra ID with a client that supports OAuth discovery.
Before you install
The remote MCP server is in preview, has no service-level agreement, and is not recommended for production workloads. Access tokens must never be committed or pasted into prompts. The agent can act on live web pages, so review what it navigates to and interacts with. Pricing applies to the underlying service.

Installation

In SourceWeft

  1. Open Playwright Cloud Browsers in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

Playwright 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:

text
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:

Migrating from Microsoft Playwright Testing

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

Source: README.md at commit 5b1f85e

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.1LatestOct 29, 2026
  2. v1.0.0Oct 23, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Microsoft integrations