MCP Puppeteer — MCP Protocol
Server that browses and screenshots the web with Puppeteer
Basic information
| Program name | MCP Puppeteer (MCP puppeteer) |
|---|---|
| One-line introduction | Server that browses and screenshots the web with Puppeteer |
| Developed and maintained by | Model Context Protocol project |
| Official homepage | https://github.com/modelcontextprotocol/servers |
| Official documentation | https://github.com/modelcontextprotocol/servers |
| Installation/deployment | npx -y @modelcontextprotocol/server-puppeteer |
| Runtime environment | MCP host apps (Claude Desktop, Cursor, opencode, etc.) |
| License | MIT License |
| Stable version | npm modelcontextprotocol/server-puppeteer (confirmed 2026-10) — confirmed on 2026-10-18 |
| GitHub repository | https://github.com/modelcontextprotocol/servers |
| Category | MCP protocol (tags: MCP, reference server, tools, agent) |
What is this program?
This server is a server implementation that browses and screenshots the web with Puppeteer, included in the official MCP reference server collection. It can be run with a single npx command, and once registered in the settings of an MCP host app, agents can use it immediately.
Primary use: web automation and scraping for agents
What problems does it solve?
- ('Puppeteer tasks', 'when an agent needs to use the server feature that browses and screenshots the web with Puppeteer', 'connect immediately with standard MCP tools')
- ('Quick connection', 'when you need to run it with npx without building a separate server', 'reuse the official implementation')
- ('Safe access', 'when you need to access it while limiting the allowed scope', 'restrict with path and permission parameters')
Key features
Exposed tools
navigate, screenshot, click, fill
- Use case: Provide agents with web automation and scraping
- Result: Standard MCP tool calls
- Limitations: Be careful with permission settings
Installation and execution
npx (Run)
Run @modelcontextprotocol/server-puppeteer with npx.
npx -y @modelcontextprotocol/server-puppeteer /path
Real-world usage example
Register with the host
Add a server entry to mcp.json.
{"mcpServers":{"puppeteer":{"command":"npx","args":["-y","@modelcontextprotocol/server-puppeteer","/path"]}}
Advantages and limitations
Advantages
- Official project implementation
- Run with a single npx command
- Exposes standard MCP tools
Things to consider before use
- Requires host app configuration
- Be careful with permission and path settings
Comparison with similar programs
| Program | Features | Suitable when |
|---|---|---|
| Direct implementation | Write only the tools you need yourself | In-house specialized tools |
| Community server | Choose alternative implementations | Exploring alternatives |
Official resources and further learning
- Official homepage — https://github.com/modelcontextprotocol/servers
- Official documentation / knowledge base — https://github.com/modelcontextprotocol/servers
- Installation/deployment — npx -y @modelcontextprotocol/server-puppeteer
- Release notes — https://github.com/modelcontextprotocol/servers/releases
- Source / development resources — https://github.com/modelcontextprotocol/servers
Version and supported environment information was confirmed on the official site as of 2026-10-18. Installation commands may vary depending on the distribution and version you use, so please also check the official installation documentation.
Actual execution screenshot
Synthetic example — not an actual execution result. The screen is a synthetic example and not an actual execution result.
Actual server in operation
Source (HTML): https://games.aidebatehub.com/programs/mcp/protocol/server-puppeteer.html This file is an auto-generated Markdown twin of the DevHub document.
AI Knowledge Hub
Visitor Comments