execute
Execute JS with Puppeteer 24.43.1. Globals: browser. Use 'return' for result. Use Puppeteer selectors: CSS, text/, aria/, xpath/, pierce/. Response includes screenshots (path, url) for each open tab.
LABSCO SUMMARY
One tool that takes code trades safety for reach, and the trade is explicit rather than hidden.
Fixed browser tools are safer and hit a wall: a multi-step interaction becomes a dozen round trips, each carrying the page state back into the model's context, and anything the tool author did not anticipate is simply unavailable. Handing over the Browser instance removes the wall entirely — a login flow, a scrape with retries, a wait on a custom condition is one call. What you give up is any boundary on what the code does, since arbitrary JavaScript with a browser handle can navigate anywhere and read anything the browser can. That is a reasonable trade for a local development machine and a poor one for anything shared, and it is worth deciding which you have before attaching it.
What it is
A browser automation server that takes the opposite approach from the usual one: rather than exposing predefined actions, it exposes a single execute tool that runs arbitrary JavaScript in a Node VM with the Puppeteer Browser instance as a global.
What you get
- execute runs your code with
browserin scope andreturnfor the result, so a whole workflow is one call rather than a sequence of round trips. - The full Puppeteer API is reachable, including the parts a fixed tool set never covers — request interception, frame handling, evaluating in page context, waiting on arbitrary conditions.
Requirements
Nothing to supply. The code runs on the machine the server runs on, with a real browser attached.
Setup effort
One command — npx pptr-mcp
USE CASES
01
Doing a multi-step interaction in one call
Write the whole flow — navigate, wait, fill, submit, extract — as one script and return the result, instead of a round trip per action.
02
Reaching the part of Puppeteer no fixed tool exposes
Use request interception, frame handling or an arbitrary wait condition, because the API is not being mediated by a tool schema.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
- npx on PATH
- Node.js >= 20
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"pptr-mcp": {
"command": "npx",
"args": [
"pptr-mcp"
]
}
}
}npx
TERMINAL
npx pptr-mcp
