puppeteer_click
Click an element on the page
LABSCO SUMMARY
puppeteer_evaluate runs arbitrary JavaScript in the page, which moves the capability question off the tool list and onto the sites you point it at.
The interaction tools address elements by CSS selector alone, so a page that renames its classes on deploy breaks the script rather than the server, and puppeteer_navigate is where browser-level configuration goes through launchOptions and the allowDangerous flag. There is no wait or condition tool in the surface: timing on a page that renders late is handled inside puppeteer_evaluate, which is also where any assertion about the page has to live.
What it is
A Puppeteer-backed browser automation server with 7 tools: navigation with launch options, pointer and form interactions addressed by CSS selector, page or element screenshots, and JavaScript execution in the browser console.
What you get
- Navigation with the browser launch under your control: puppeteer_navigate takes a url plus launchOptions for the browser itself and an allowDangerous flag.
- Interaction addressed by CSS selector: puppeteer_click clicks the element a selector matches, puppeteer_fill writes a value into an input, puppeteer_select chooses a value inside a select element, and puppeteer_hover moves the pointer over an element.
- Screenshots of the page or of one element: puppeteer_screenshot takes a name, an optional selector to scope the shot, width and height, and an encoded flag.
- An escape hatch for anything the interaction tools do not cover: puppeteer_evaluate runs a script in the browser console and returns its result.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y @modelcontextprotocol/server-puppeteer
USE CASES
01
Reading a page that does not exist until its JavaScript runs
Load the URL in a real browser, pull what you need out of the live DOM, and keep a screenshot of what was on screen when you did.
02
Driving a form through to the page behind it
Fill the inputs, set the dropdowns, submit, and carry on from wherever the site lands you.
03
Capturing how a page looks, including the states you have to reach first
Size the shot, trigger the hover or click that reveals the thing, and capture the page or the element on its own.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
puppeteer_evaluate
Execute JavaScript in the browser console
puppeteer_fill
Fill out an input field
puppeteer_hover
Hover an element on the page
puppeteer_navigate
Navigate to a URL
puppeteer_screenshot
Take a screenshot of the current page or a specific element
puppeteer_select
Select an element on the page with Select tag
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected. console://logs and screenshot://<name> are resources, not tools.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @modelcontextprotocol/server-puppeteerThis command installs @modelcontextprotocol/server-puppeteer — the reference Puppeteer server this repository adapts (its package.json carries the same name) — not a package published by code-craka, and npm marks it "no longer supported". The Docker route builds this repository's own code.
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"puppeteer": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-puppeteer"
]
}
}
}Runs @modelcontextprotocol/server-puppeteer, the reference server this repository adapts, which npm marks no longer supported; use the Docker route to run this repository's own build.
Any MCP client — Docker
Build the image
You build this image yourself from the repository before the client can start it.
ANY MCP CLIENT — DOCKER · TERMINAL
git clone https://github.com/code-craka/puppeteer-mcp.git
cd puppeteer-mcp
docker build -t puppeteer-mcp .Add this to your client's config
The client starts a container from the image you just built.
ANY MCP CLIENT — DOCKER · JSON
{
"mcpServers": {
"puppeteer": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e",
"DOCKER_CONTAINER=true",
"puppeteer-mcp"
]
}
}
}
