Puppeteer MCP Server
The Puppeteer MCP Server enables browser automation and web interaction through Puppeteer, providing tools for:
Navigate to any URL (
puppeteer_navigate)Capture screenshots of pages or elements (
puppeteer_screenshot)Click elements identified by CSS selectors (
puppeteer_click)Hover over elements (
puppeteer_hover)Fill input fields with specified values (
puppeteer_fill)Select options from dropdowns (
puppeteer_select)Execute JavaScript in the browser context (
puppeteer_evaluate)Monitor and access browser console logs (
console://logs)Retrieve captured screenshots (
screenshot://<name>)Get history of visited URLs (
puppeteer_page_history)Make HTTP requests with various methods (
make_http_request)Semantically search network requests within specific pages (
semantic_search_requests)
Enables interaction with web page elements through CSS selectors for actions like clicking, hovering, and capturing screenshots of specific elements
Allows executing JavaScript code in the browser console using the puppeteer_evaluate tool
Provides browser automation capabilities using Puppeteer, enabling LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Puppeteer MCP Server take a screenshot of the homepage and save it as homepage.png"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Puppeteer
A Model Context Protocol server that provides browser automation capabilities using Puppeteer. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
Components
Tools
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 screenshotselector(string, optional): CSS selector for element to screenshotwidth(number, optional, default: 800): Screenshot widthheight(number, optional, default: 600): Screenshot height
puppeteer_click
Click elements on the page
Input:
selector(string): CSS selector for element to click
puppeteer_hover
Hover elements on the page
Input:
selector(string): CSS selector for element to hover
puppeteer_fill
Fill out input fields
Inputs:
selector(string): CSS selector for input fieldvalue(string): Value to fill
puppeteer_select
Select an element with SELECT tag
Inputs:
selector(string): CSS selector for element to selectvalue(string): Value to select
puppeteer_evaluate
Execute JavaScript in the browser console
Input:
script(string): JavaScript code to execute
Resources
The server provides access to two types of resources:
Console Logs (
console://logs)Browser console output in text format
Includes all console messages from the browser
Screenshots (
screenshot://<name>)PNG images of captured screenshots
Accessible via the screenshot name specified during capture
Related MCP server: Puppeteer MCP Server
Key Features
Browser automation
Console log monitoring
Screenshot capabilities
JavaScript execution
Basic web interaction (navigation, clicking, form filling)
Configuration to use Puppeteer Server
Here's the Claude Desktop configuration to use the Puppeter server:
Docker
NOTE The docker implementation will use headless chromium, where as the NPX version will open a browser window.
{
"mcpServers": {
"puppeteer": {
"command": "docker",
"args": ["run", "-i", "--rm", "--init", "-e", "DOCKER_CONTAINER=true", "mcp/puppeteer"]
}
}
}NPX
{
"mcpServers": {
"puppeteer": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-puppeteer"]
}
}
}Build
Docker build:
docker build -t mcp/puppeteer -f src/puppeteer/Dockerfile .License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Available Tools
4 toolsmake_http_requestC
Make an HTTP request with curl
Inputs: body (required), headers (required), type (required), url (required).
puppeteer_page_historyB
Get the history of visited URLs, most recent urls first
Inputs: no named parameters.
semantic_search_requestsC
Semantically search for requests that occurred within a page URL. Returns the top 10 results.
Inputs: page_url (required), query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: make_http_request performs general HTTP requests, puppeteer_navigate navigates to URLs in a browser context, puppeteer_page_history retrieves navigation history, and semantic_search_requests searches within page requests. There is no overlap or ambiguity between these functions.
The naming is mixed with no consistent pattern: make_http_request uses verb_noun format, puppeteer_navigate and puppeteer_page_history use a prefix_noun format, and semantic_search_requests uses an adjective_noun_noun format. While readable, the conventions vary without a predictable structure.
With only 4 tools, the count feels thin for a Puppeteer server, which typically handles browser automation tasks like clicking, typing, or screenshotting. The tools cover basic navigation and HTTP requests but lack broader automation capabilities, making the scope borderline under-scoped.
For a Puppeteer server, there are significant gaps in the tool surface. Missing are core operations like interacting with page elements (e.g., click, type), evaluating scripts, taking screenshots, or managing browser contexts. The tools provided focus narrowly on navigation and HTTP requests, leaving major automation workflows uncovered.
Related MCP Connectors
A real browser for your agent: screenshots, page checks, Markdown and PDFs.
Control a real browser from AI agents: navigate, click, type, screenshot, read the page.
Hosted browser for agents: open pages, search the web, extract data, read PDFs and take screenshots.
Provides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to i…
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment10264 npm297MIT
- AlicenseBqualityDmaintenanceEnables AI agents to automate browser interactions including navigation, content extraction, form filling, screenshots, and JavaScript execution across multiple tabs using Puppeteer.2765 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to perform browser automation tasks including web scraping, taking screenshots, and executing JavaScript using Playwright. It facilitates real-time interaction with web pages and the generation of automated test code.23 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to perform browser automation including web navigation, element interaction, and screenshot capture using Puppeteer. It provides capabilities for executing JavaScript in the browser and monitoring console logs for debugging and data extraction.28,579 npmMIT