F
licenseB
qualityNot graded
maintenanceAn MCP server that provides web development tools including taking screenshots of screens, enabling AI agents to capture and analyze visual content during development.
2
22 npm
11
-
Screenshot MCP
by upnorthmedia
Related Servers
Alternatives to Screenshot MCP
No user-submitted related servers found.
Related Servers
- 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.222 npm15MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to capture and analyze web page screenshots using Puppeteer, supporting multi-breakpoint captures, error reporting, and page interactions.151 npm6MIT
- AlicenseBqualityBmaintenanceAn official MCP server implementation that allows AI assistants to capture website screenshots through the ScreenshotOne API, enabling visual context from web pages during conversations.115 npm36MIT
- 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.-
- AlicenseAqualityDmaintenanceMCP server for ScreenshotFreeAPI – capture website screenshots, render HTML/PDF, and fetch app store listing screenshots from any MCP-compatible AI client.75 npmMIT
TDQS
B3.2/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: capture_element targets specific webpage elements, capture_screenshot handles full-page captures with advanced options, and list_device_presets deals with device configurations. There is no overlap or ambiguity between these functions.
Naming Consistency4/5
The naming follows a consistent verb_noun pattern (capture_element, capture_screenshot, list_device_presets), with all tools using snake_case. The minor deviation is that list_device_presets uses 'list' instead of 'capture', but this is appropriate for its distinct function.
Tool Count3/5
With only 3 tools, the count feels thin for a screenshot domain that might benefit from additional operations like managing screenshots or adjusting capture settings. However, it covers core capture functions adequately.
Completeness3/5
The toolset covers basic screenshot capture (element and full-page) and device preset listing, but lacks operations for managing captured screenshots (e.g., save, delete, annotate) or advanced configuration beyond presets. This creates minor gaps in the workflow.
Maintenance
ActivitySlowing
ResponsivenessSlow