puppeteer_click
Click an element on the page
LABSCO SUMMARY
Automation runs inside the browser session you are already signed into.
puppeteer_connect_active_tab is the distinguishing tool: attaching to a Chrome that is already running means the cookies, extensions and logged-in state are there, so a flow behind an SSO wall does not need a scripted sign-in that will break the next time the login page changes. The rest is the familiar set — navigate, click, fill, select, hover, screenshot — with puppeteer_evaluate as the escape hatch. Everything addresses elements by CSS selector, so a page that only distinguishes controls visually will still be awkward.
What it is
A Puppeteer driver that can either work on its own page or connect to a running Chrome over its remote debugging port.
What you get
- A connection to an existing Chrome instance over its remote debugging port, optionally aimed at a target URL
- Page interaction by CSS selector: click an element, fill an input, choose an option in a select, hover
- Screenshots of the whole page or of a single element, at a width and height you set
- puppeteer_evaluate, which runs JavaScript in the page console when a selector is not enough
Requirements
Chrome on the machine, started with remote debugging enabled if you want to attach to a session you are already signed into. MIT licensed.
Setup effort
One command — npx -y puppeteer-mcp-server
USE CASES
01
Automating a flow that sits behind a login
Attach to the Chrome you are already signed into over its debugging port, go to the page, and work it from there — no scripted sign-in to maintain.
02
Filling in a form nobody wants to fill in by hand
Type into the inputs, pick the dropdown values, hover anything that only reveals itself on hover, and submit.
03
Capturing what a page actually looks like right now
Open the URL and take the shot — the whole page, or the one element you care about, at the width and height you set.
04
Pulling data off a page that has no clean selector for it
When the markup will not cooperate, run the JavaScript in the page context and take the result back.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
puppeteer_connect_active_tab
Connect to an existing Chrome instance with remote debugging enabled
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
8 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"puppeteer-mcp-server": {
"command": "npx",
"args": [
"-y",
"puppeteer-mcp-server"
]
}
}
}npx
TERMINAL
npx -y puppeteer-mcp-server
