puppeteer_navigateLABSCO SUMMARY
The Puppeteer server, minus the Linux display fight.
The automation surface is the standard one; the reason to pick this fork is that it starts on GNOME, KDE and Wayland instead of failing on a display variable it could not find.
What it is
A fork of the Puppeteer MCP server that adds Linux display-server handling: X11 and Wayland detected automatically, environment variables set dynamically, XWayland compatibility, and fallbacks when detection fails. The browser surface itself is navigation, screenshots, clicking, hovering, filling, selecting and JavaScript evaluation.
What you get
- A real browser navigated to any URL
- Screenshots of the whole page or one element, at a width and height you set
- Elements clicked and hovered, and select boxes set to a value
- Input fields filled
- JavaScript executed in the browser console
- Browser console output available as a resource
- Captured screenshots available as resources by name
- X11 and Wayland detected and configured automatically, including XWayland
Requirements
A Linux desktop running X11 or Wayland, and Node.js. The browser runs on your machine under your account, so it reaches whatever you can reach.
Setup effort
Build from source — git clone https://github.com/PhialsBasement/MCP-Puppeteer-Linux.git
USE CASES
01
Automating a site from a Linux workstation
Open the page and drive it without configuring DISPLAY or working around Wayland yourself.
02
Filling in a form you fill in every week
Set the inputs and the select boxes by CSS selector and submit.
03
Showing an agent what the page actually looks like
Capture the page or a single element at a size you choose, and read it back as a resource.
04
Working out why a page misbehaves
Run JavaScript in the page and read the console output the browser recorded.
05
Reaching something that only appears on hover
Hover the element to reveal the menu, then capture what appeared.
7 tools
Listed in project docs. Your client may show a different list.
puppeteer_screenshotpuppeteer_clickpuppeteer_hoverpuppeteer_fillpuppeteer_selectpuppeteer_evaluateBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/PhialsBasement/MCP-Puppeteer-Linux.git
cd MCP-Puppeteer-Linux
npm installMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"puppeteer": {
"command": "npx",
"args": [
"ts-node",
"<YOUR_PATH_TO_INDEX>"
]
}
}
}<YOUR_PATH_TO_INDEX> is the full path to index.ts at the top of your MCP-Puppeteer-Linux clone.
