In-depth architectural comparison of the Site Shot MCP and Agent Scraper 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
Site Shot MCP
Browser Automation · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Agent Scraper MCP
Browser Automation · Local stdio
Quality: 56/100 (Good) | Auth: other
Verdict Summary: Choose Site Shot MCP if you need specialized Browser Automation tools running via a local process. Choose Agent Scraper 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 Site Shot MCP when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: SITESHOT_API_KEY.
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.
Web scraping MCP server for AI agents. 6 tools: clean content extraction, structured scraping with CSS selectors, full-page screenshots via Playwright, link extraction, metadata extraction (OG/Twitter cards), and Google search. Free tier with x402 micropayments.
Category & Scope
Tools & Capabilities Breakdown
Site Shot MCP Tools (2)
capture_screenshot
Screenshot a web page (viewport by default).
capture_full_page
Same as `capture_screenshot` with full-page capture enabled.
Agent Scraper MCP Tools (6)
title
Page title
description
Meta description
canonical
Canonical URL
favicon
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).
Site Shot MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Agent Scraper MCP belongs to Browser Automation using local stdio subprocess. Select Site Shot MCP when you need capabilities focused on browser automation and Agent Scraper MCP when you require tools for browser automation.