In-depth architectural comparison of the Screenshotrender MCP and Site Shot MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Screenshotrender MCP
Browser Automation · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Site Shot MCP
Browser Automation · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose Screenshotrender MCP if you need specialized Browser Automation tools running via a local process. Choose Site Shot MCP if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Screenshotrender MCP when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: SCREENSHOTRENDER_API_KEY, SCREENSHOTRENDER_BASE_URL.
Capture a screenshot of any public URL. Returns the image inline plus a hosted URL and page metadata (title, description).
Site Shot MCP Tools (2)
capture_screenshot
Take a screenshot of a web page with Site-Shot and return it as an image. Renders in a real Chromium browser. Supports viewport/device sizing, full-page capture, country proxies, and automatic ad & cookie-banner removal (cleaner image, fewer vision tokens).
capture_full_page
Take a full-page (entire scrollable height) screenshot of a web page with Site-Shot and return it as an image. Convenience wrapper around capture_screenshot with full-page capture enabled.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Screenshotrender MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Site Shot MCP belongs to Browser Automation using local stdio subprocess. Select Screenshotrender MCP when you need capabilities focused on browser automation and Site Shot MCP when you require tools for browser automation.
Capture website screenshots from any MCP client via the ScreenshotRender API.
Website screenshot API for AI agents. Real Chromium rendering, full-page capture up to 20,000px, country/geo proxies, and automatic ad & cookie-banner removal (cleaner images, fewer vision tokens). Two tools: capturescreenshot, capturefullpage. Install: npx -y site-shot-mcp.