screenshotapi-mcp
Related Servers
Alternatives to screenshotapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to capture any public URL as PNG, JPEG, or PDF via REST API or MCP tools, including screenshot capture, page description, and PDF rendering.14 npmMIT

screenshotrun-mcpofficial
AlicenseAqualityCmaintenanceGive your AI agent the ability to capture website screenshots. Works with Claude, Cursor, and any MCP client. Supports full-page, dark mode, mobile emulation, OG image generation, base64 output, and more. Free tier included.2307 npmMIT- AlicenseAqualityBmaintenanceEnables MCP-compatible AI agents to search, scrape, crawl, map, and interact with live web pages, returning clean, structured, agent-ready content. It also supports recurring page monitoring, autonomous deep research, and credit-usage checks.26168,149 npm1MIT

Grabbitofficial
AlicenseNot gradedqualityCmaintenanceScreenshot MCP for agents. Send a public URL, get a pixel-perfect CDN image. Full page, header, mobile, or custom. Cookie banner suppression. Handles sites that block headless browsers. Works with Claude, Cursor, Codex. $0.002/grab.MIT- AlicenseAqualityBmaintenanceDeterministic file operations for AI agents: 40 operations over plain HTTPS. PDF merge, split, redact, sanitize, OCR, Office and PDF to Markdown, RAG chunking, charts, QR codes, C2PA AI labelling. find_tool suggests the right one. $0.01 per operation, 100 free, no signup, credits never expire.552 npmMIT

crawlbrulee-mcpofficial
AlicenseAqualityBmaintenanceEU-native web scraping for AI agents & developers. scrape web pages into markdown, screenshots, metadata, and links, map sites, run asynchronous scrape jobs, and check usage, with EU-hosted, GDPR-aligned processing.7257 npm1Apache 2.0
TDQS
Scored across 5 tools
Tools are mostly distinct: render-screenshot captures full pages, capture-element targets specific DOM elements, convert-to-markdown extracts text, get-screenshot retrieves by ID, and get-usage is account-related. The only minor overlap is between the two capture tools, but their descriptions clearly differentiate full-page vs. element capture.
All tool names follow a consistent verb-noun pattern with hyphenated lowercase (render-screenshot, capture-element, convert-to-markdown, get-usage, get-screenshot). The verbs clearly indicate actions, and the nouns identify the object, making the naming predictable and easy to infer.
With 5 tools, the server is well-scoped for a screenshot utility. Each tool serves a distinct purpose without redundancy, covering the core capture, retrieval, conversion, and account management needs. This count is appropriate and not overwhelming or thin.
The tool surface covers the primary workflow: capturing screenshots (full-page and element), converting to markdown, retrieving past captures, and checking usage. Minor gaps exist, such as no tool for listing all captures or deleting them, but these are not essential for the core screenshot API functionality and can be worked around.