PuppeteerMCP Server
Related Servers
Alternatives to PuppeteerMCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that enables AI assistants to visually inspect and interact with rendered web pages via a persistent headless Chromium browser, supporting navigation, screenshots, clicks, viewport resizing, and console log retrieval.81MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for browser automation using Puppeteer that enables AI assistants to navigate web pages, interact with UI elements, and capture screenshots. It supports comprehensive web tasks including form filling, content extraction, and executing custom JavaScript within the browser context.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for headless browser automation using Puppeteer, enabling AI to navigate, click, fill forms, take screenshots, and execute JavaScript on web pages.-
- FlicenseBqualityNot gradedmaintenanceAn MCP server that provides web development tools including taking screenshots of screens, enabling AI agents to capture and analyze visual content during development.239 npm11-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enables AI assistants to capture and view screenshots, supporting multiple AI tools and platforms.38 npm20MIT
- AlicenseBqualityDmaintenanceAn MCP server providing web development tools such as screen capturing capabilities that let AI agents take and work with screenshots of the user's screen.239 npm15MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose focused on capturing screenshots at multiple viewport breakpoints.
The tool name 'screenshot' follows a simple, descriptive noun-based pattern. Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'PuppeteerMCP Server', which suggests broader web automation capabilities beyond just screenshots. This feels thin and under-scoped for the apparent domain of Puppeteer-based web interactions.
The tool surface is severely incomplete for a Puppeteer server, covering only screenshot functionality. Obvious gaps include navigation, form interaction, content extraction, and other core web automation tasks, which will likely cause agent failures in broader workflows.