Playwright (local) logo

Playwright (local)

Beta

Microsoft's browser automation server drives a real browser for the agent. It navigates, fills forms, clicks and reads pages.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx, Docker
Platform
macOS
Publisher
Microsoft

How it works

Every agent request passes through Ferentin policy before it reaches Playwright (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @playwright/mcp or docker run -i --rm mcp/playwright.

Ferentin's endpoint agent finds Playwright (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Playwright (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Playwright (local)

Microsoft's browser automation server drives a real browser for the agent. It navigates, fills forms, clicks and reads pages.

Frequently asked about Playwright (local)

How do I connect Playwright (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Playwright (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Playwright (local) integration generally available?
The Playwright (local) integration is currently beta on Ferentin.