app-screenshot-mcp
Related Servers
Alternatives to app-screenshot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol (MCP) server for taking screenshots of web pages using Playwright, allowing AI agents to automatically capture and analyze screenshots for UI verification or other tasks.108 npm23AGPL 3.0
- AlicenseBqualityNot gradedmaintenanceA MCP server that provides browser automation tools, allowing users to navigate websites, take screenshots, click elements, fill forms, and execute JavaScript through Playwright.82Apache 2.0
- AlicenseBqualityDmaintenanceA browser automation server providing Playwright capabilities for controlling web browsers, capturing screenshots, extracting content, and performing complex interactions through an MCP interface.6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides structured control of a Playwright browser for QA, scraping, diagnostics, and reproducible browser workflows.4,799 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.3 npm2MIT
- FlicenseNot gradedqualityFmaintenanceA unified MCP server that combines screenshot capture with HTTP/SSE gateway for remote access, enabling full-page and element-specific screenshots via Puppeteer.-
TDQS
Scored across 2 tools
The tools are clearly distinguished by their purpose: one captures a public URL, the other handles form-based authentication before capturing. Though both ultimately produce screenshots, the workflow differs enough to avoid confusion.
Both tool names start with 'capture_' and follow a verb-led pattern. The second name uses a prepositional phrase ('with_login') but it remains readable and consistent in style.
With only two tools, the server feels minimal. This is borderline for a narrow purpose but is not egregiously thin; the two covered scenarios (public and authenticated) justify the count.
The domain is screenshot capture, and the two tools cover basic capture and authenticated capture. However, there are minor gaps such as no support for element screenshots, cookie injection, or alternative rendering options, which agents might need but can work around.