Playwright MCP Servers Explained: Automation and Testing

Did you know Playwright has two MCP servers. Yes kinda confusing, let me explain it. The Playwright MCP server is great from Browser Automation, filling out forms for example or even using so LLM’s can verify their work by opening the browser and taking a page snapshot to see it actually implemented what it said it did. It is built in to GitHub Copilot Coding Agent so if you assign a pr to Copilot it will use Playwright which you can see in the session logs. It is very cool indeed.

Then we have another Playwright MCP server called Playwright Test MCP which is built into Playwright test and is for, yes you guessed it, testing. It has some similar tools as the Playwright MCP server but it also has other ones that you only need if you are testing. It starts running when you use the Playwright Agents, Planner, Generator and Healer. However this MCP server only supports TypeScript/JavaScript for now.

So depending on your needs you can use one MCP server or the other. The Playwright MCP server you need to install while the Playwright Test MCP server is installed when you run an npx command when using the latest version of Playwright.

npx playwright init-agents --loop=vscode

The installing of the MCP server is done for you and it doesn’t matter what other MCP server you have as the agent will only use the tools that it has assigned to it.

Check out the docs for more info on how to get started. Have fun and happy testing with Playwright MCPs

https://playwright.dev/docs/test-agents
https://github.com/microsoft/playwright-mcp

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post

The Ultimate Guide to High-Performance Web Animations

Next Post
how-i-turned-sales-call-chaos-into-gtm-gold-using-a-3-step-framework

How I turned sales call chaos into GTM gold using a 3-step framework

Related Posts