Official Vendor Server
Anthropic✦ Lab Verified
Puppeteer
Browser automation and web scraping using Puppeteer. Navigate pages, take screenshots, and interact with web content.
9.5/10
Score
33ms
Latency
Local
Uptime
7
Tools
stdio
Auth
Ecosystem
Anthropic MCP Servers
4 specialized servers, 30 tools tested independently. Each link leads to a full review with tool-level evidence.
| Server | Score | Security |
|---|---|---|
| SQLite | 95/100 | 10/10 |
| Memory / Knowledge Graph | 95/100 | 10/10 |
| Filesystem | 95/100 | 10/10 |
| Sequential Thinking | 94/100 | 10/10 |
Quick Verdict
All 7 browser automation tools executed without failures. Avoid it for non-browser automation tasks. Best area: web page interactions. Biggest failure: none in current tests.
Lab Review
What We Found
What works: Puppeteer's MCP server delivers on browser automation fundamentals. Navigation, form filling, clicking, hovering, JavaScript evaluation and screenshots all executed cleanly. The server performed consistently across all 7 core operations, handling everything from basic page interactions to complex DOM manipulation without errors. Where it breaks: We tested the complete available toolset and found no failures. All puppeteer operations completed successfully, from puppeteer_navigate through puppeteer_screenshot. The server handled form interactions, element selection and page evaluation without throwing errors or returning malformed responses. Even the slowest operation completed within acceptable bounds at 1563ms. What this means for your workflow: You can build browser automation workflows on this server's complete feature set. Navigation, form filling, clicking, hovering, JavaScript execution and screenshot capture are all reliable. The consistent performance across DOM interactions means you can chain operations without defensive error handling between each step. For any team needing headless browser automation through MCP, this server delivers what it promises.
Lab Observations
What actually happened during testing
During testing, our scanner interacted with Puppeteer. 7 tools succeeded.
| Tool | Status |
|---|---|
| puppeteer_navigate | ✅ success |
| puppeteer_evaluate | ✅ success |
| puppeteer_fill | ✅ success |
| puppeteer_select | ✅ success |
| puppeteer_hover | ✅ success |
| puppeteer_click | ✅ success |
| puppeteer_screenshot | ✅ success |
Reliability
Full runtime test completed. Score based on transport stability and schema completeness.
Score Breakdown
Reliability
7 of 7 executed tools succeeded.
Security
Score based on schema analysis and dependency audit.
Setup
Local stdio server. Install via npx or binary, no auth required.
Docs
7 tools with descriptions and input schemas.
Compatibility
Standard MCP protocol. Transport: stdio.
Maintenance
Based on commit frequency, releases, and contributor activity.
Tools
7 available tools
Navigate to a URL
Take a screenshot of the current page or a specific element
Click an element on the page
Fill out an input field
Select an element on the page with Select tag
Show all 7 tools →Show less ↑
Hover an element on the page
Execute JavaScript in the browser console
FAQ
Frequently asked questions about Puppeteer
What latency should I expect for different Puppeteer operations?+
Browser interaction latencies ranged from 7ms to 1563ms in our tests. The fastest operations were puppeteer_evaluate and puppeteer_select at 7ms each. Navigation and form filling completed in 51ms and 33ms respectively. Screenshots took 613ms, while click operations were slowest at 1563ms. These measurements reflect actual DOM manipulation and rendering times in a sandboxed environment.
Does the server require authentication or special permissions to run?+
Our testing used none credentials with empty scopes array, and all 7 tools executed successfully. The server runs via local_stdio transport without requiring external authentication tokens. However, the underlying Puppeteer operations still depend on your system's ability to launch browser instances and access target websites or local files.
Can I use this server for taking screenshots of web pages?+
The puppeteer_screenshot tool executed successfully in our tests, capturing page content in 613ms. This operation completed without errors in the sandbox environment. The screenshot functionality is directly available through the MCP interface without requiring additional configuration beyond basic server setup.
Which browser automation tasks are directly supported?+
Seven core automation tools executed successfully: page navigation, JavaScript evaluation, form field filling, dropdown selection, element hovering, clicking, and screenshot capture. Each tool completed its intended browser interaction without errors. The server provides direct MCP access to these fundamental web automation primitives through the Puppeteer engine.
Are there any operations that consistently take longer to complete?+
Click operations showed notably higher latency at 1563ms compared to other interactions. This represents a 24x difference from the fastest operations like element selection. Screenshot capture also required substantial time at 613ms, likely due to rendering and image encoding processes. Most form interactions and evaluations completed under 60ms.
What happens when JavaScript evaluation encounters errors?+
The puppeteer_evaluate tool completed successfully in our tests, executing JavaScript code in 7ms without errors. However, our testing only covered successful evaluation scenarios. The actual error handling behavior for malformed JavaScript, runtime exceptions, or security violations was not directly tested in this evaluation.
Related
Explore more
Testing History
Community