Browser Automation MCP Servers
Find MCP servers that let agents open websites, inspect pages, capture screenshots, scrape data, and run repeatable browser tasks.
匹配的 MCP 服务器
结果来自现有 MCP Servers 目录,没有单独的主题数据库。
Browser Automation MCP 适合的场景
Give agents a real browser for QA, research, screenshots, and page inspection.
Automate navigation, clicks, form flows, and visual checks from an MCP-compatible client.
Choose between general browser control, Playwright workflows, Puppeteer automation, and DevTools inspection.
设置清单
- 1Choose a browser automation server based on the actions and browser engine you need.
- 2Install the server package or follow the repository setup instructions.
- 3Add the command or remote endpoint to your MCP client configuration.
- 4Verify a small navigation, screenshot, and page-inspection task before relying on longer workflows.
如何选择
- Check support for screenshots, DOM or accessibility snapshots, console logs, network data, and JavaScript execution.
- Prefer servers with clear sandboxing, browser session, and permission behavior.
- Use Playwright or Chrome DevTools specific servers when your workflow depends on those exact APIs.
Browser Automation MCP 常见问题
What is Browser Automation MCP?
Browser Automation MCP connects an AI client to a browser automation layer so agents can navigate pages, inspect UI state, capture screenshots, and run browser tasks through MCP.
Is Browser Automation MCP only for testing?
No. Testing is common, but the same capability is useful for web research, scraping, visual QA, debugging, and workflows where an agent needs to interact with real websites.
Should I choose Playwright MCP or a general browser MCP server?
Use Playwright MCP when you specifically want Playwright actions and repeatable test-style flows. Use a broader browser MCP server when you need discovery, screenshots, or page inspection across a wider workflow.