Puppeteer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| puppeteer_connect_active_tabB | Connect to an existing Chrome instance with remote debugging enabled |
| puppeteer_navigateB | Navigate to a URL |
| puppeteer_screenshotB | Take a screenshot of the current page or a specific element |
| puppeteer_clickC | Click an element on the page |
| puppeteer_fillC | Fill out an input field |
| puppeteer_selectC | Select an element on the page with Select tag |
| puppeteer_hoverC | Hover an element on the page |
| puppeteer_evaluateB | Execute JavaScript in the browser console |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Browser console logs |
TDQS
Scored across 8 tools
Each tool targets a distinct browser action (click, navigate, fill, hover, etc.) with no overlap, making selection unambiguous.
All tools follow a consistent pattern: 'puppeteer_' prefix followed by a clear action verb, ensuring predictability.
With 8 tools covering essential browser interactions, the count is well-scoped for a focused automation server.
Core operations are covered, but missing explicit waiting or content extraction tools; however, puppeteer_evaluate can compensate.