A Model Context Protocol server for browser automation using Puppeteer with Linux display server support
A Model Context Protocol server for browser automation using Puppeteer with Linux display server support. The mcp puppeteer linux mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
A Model Context Protocol server that provides browser automation capabilities using Puppeteer, with full support for Linux display servers (X11 and Wayland). This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
puppeteer_navigate — Navigate to any URL in the browserInput — url (string)puppeteer_screenshot — Capture screenshots of the entire page or specific elementsInputs — - name (string, required): Name for the screenshotpuppeteer_click — Click elements on the pagepuppeteer_hover — Hover elements on the pagepuppeteer_fill — Fill out input fieldspuppeteer_select — Select an element with SELECT tagpuppeteer_evaluate — Execute JavaScript in the browser consoleTools — The Tools tool exposed by this serverResources — The server provides access to two types of resources: 1. Console Logs (console://logs) - Browser console output in text format - Includes allThis sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Puppeteer Linux's toolset — puppeteer_navigate, Input, puppeteer_screenshot and 8 more — is a fair guide to whether it matches your workflow. It is maintained by PhialsBasement; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| puppeteer_navigate | Navigate to any URL in the browser |
| Input | url (string) |
| puppeteer_screenshot | Capture screenshots of the entire page or specific elements |
| Inputs | - name (string, required): Name for the screenshot |
| puppeteer_click | Click elements on the page |
| puppeteer_hover | Hover elements on the page |
| puppeteer_fill | Fill out input fields |
| puppeteer_select | Select an element with SELECT tag |
| puppeteer_evaluate | Execute JavaScript in the browser console |
| Tools | The Tools tool exposed by this server. |
| Resources | The server provides access to two types of resources: 1. **Console Logs** (console://logs) - Browser console output in text format - Includes all console messages from the browser 2. **Screenshots** (screenshot://<name>) |
{
"mcpServers": {
"puppeteer": {
"command": "npx",
"args": ["ts-node", "/path/to/index.ts"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.