Connect Playwright MCP to Conductor
Browser automation over MCP from the Playwright team. Agents use it to open the built UI, take screenshots and check layouts against the design.
MCP serverOfficialChecked 2026-11-16
Before you start
- Conductor installed (see its MCP documentation (opens in a new tab)).
- Playwright MCP is available on macOS, Windows and Linux.
Step 1: Add Playwright MCP to Conductor
For Claude Code sessions
Saves the server to your Claude Code user settings, so every Conductor workspace gets it.
Terminal claude mcp add --scope user playwright -- npx -y @playwright/mcp@latestFor Codex sessions
Saves the server to
~/.codex/config.toml, which Codex sessions in every workspace read.Terminal codex mcp add playwright -- npx -y @playwright/mcp@latestOr share it with your team
Add this to
.mcp.jsonat the project root and commit it. Claude Code sessions in every workspace on that branch pick it up..mcp.json { "mcpServers": { "playwright": { "type": "stdio", "command": "npx", "args": [ "-y", "@playwright/mcp@latest" ] } } }Or edit Codex's config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.playwright] command = "npx" args = ["-y", "@playwright/mcp@latest"]Good to know- Start a new session in Conductor after adding a server, so the agent loads it.
Step 2: Check it's connected
Terminal claude mcp listIn a Conductor session, click the plug icon in the composer or run
/mcp-statusto see each server's status.Step 3: Try a first request
Ask Conductor something that only works with Playwright MCP connected:
Say to Conductor Open http://localhost:3000, take a screenshot at 375 px wide and tell me what looks broken.
If it doesn't work
- Conductor has no MCP settings of its own. Claude Code and Codex sessions load the same servers they use outside Conductor.
- Each workspace is a separate git worktree. Servers added with plain
claude mcp addonly apply to the folder you ran it in, so use--scope useror a committed.mcp.json. - Conductor runs on macOS. Environment variables for local servers can go in
.conductor/settings.local.toml, under[environment_variables].






