{"version":"2.1.285","anchor":"built-in-browser-mcp-server-via-playwright-mcp-script","canonical_anchor":"built-in-browser-mcp-server-via-playwright-mcp-script","heading":"Browser MCP server setup now runs a bundled Playwright script","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/built-in-browser-mcp-server-via-playwright-mcp-script","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Browser MCP server setup now runs a bundled Playwright script\n\nClaude Code can build a browser MCP server that runs a bundled Playwright script with node and sets CLAUDE_TEST_PROJECT_DIR\n\n**Unclear.** It is not clear what switches the browser server on or where it is used.\n\n**What**\n\nMCP servers are external tools Claude Code can connect to. Claude Code can now produce a server setup named `browser` that runs the script `skills\/run\/scripts\/playwright-mcp.mjs` with node. It sets `CLAUDE_TEST_PROJECT_DIR` to your project folder.\n\nSeparately, the list of keys Claude Code recognises in a plugin's manifest (the file describing a plugin) now includes `channels`, `monitors`, `settings`, `userConfig` and `experimental`.\n\n**Why**\n\nThis points to a bundled skill for running and controlling a browser.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}