puppeteer_click
Click an element on the page
LABSCO SUMMARY
Standard Puppeteer tools, with the launch config left in your hands.
The tool surface is the familiar navigate/click/fill/screenshot set; what you are choosing here is the escape hatch. Anything Puppeteer accepts at launch — a different browser, a fixed viewport, extra flags — goes in one environment variable, which is the difference between working around a site and forking the server.
What it is
A Puppeteer-backed browser automation server whose distinguishing feature is that the browser launch options are yours to set. A JSON string in PUPPETEER_ARGS is passed straight to Puppeteer, so you can switch the engine or fix the viewport without touching the server code.
What you get
- Navigation to any URL —
puppeteer_navigate - Screenshots of the whole page or one element, with width and height you choose (defaults 800 by 600) —
puppeteer_screenshot - Clicking and hovering elements by CSS selector —
puppeteer_click,puppeteer_hover - Form input and dropdown selection —
puppeteer_fill,puppeteer_select - Arbitrary JavaScript executed in the page —
puppeteer_evaluate - Two resources to read from: browser console output at
console://logs, and each capture atscreenshot://<name>
Requirements
No account and no key. Launched straight from GitHub with npx -y github:afshawnlotfi/mcp-configurable-puppeteer, optionally pinned to a branch, tag or commit. PUPPETEER_ARGS takes a JSON string of Puppeteer launch options — the README shows {"browser": "firefox"} and a defaultViewport of 1280 by 800.
Setup effort
One command — npx -y github:afshawnlotfi/mcp-configurable-puppeteer
USE CASES
01
Checking a page renders correctly at a specific size
Set defaultViewport in PUPPETEER_ARGS to the width and height you care about, navigate, and capture the screenshot at that size.
02
Filling in and submitting a form end to end
Navigate to the page, fill the inputs and pick from the dropdowns by CSS selector, click submit, then read the console resource to see whether anything errored.
03
Reproducing a bug that only appears in Firefox
Pass {"browser": "firefox"} through PUPPETEER_ARGS and run the same steps — no code change, just a different launch option.
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.
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
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-configurable-puppeteer": {
"command": "npx",
"args": [
"-y",
"github:afshawnlotfi/mcp-configurable-puppeteer"
]
}
}
}npx
TERMINAL
npx -y github:afshawnlotfi/mcp-configurable-puppeteer
