Site Shot MCP vs Rendex MCP

In-depth architectural comparison of the Site Shot MCP and Rendex 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.

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.
• Primary tools included: capture_screenshot, capture_full_page.

Explore Site Shot MCP Details

Choose Rendex 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 (Freemium).
• You have access to required keys: RENDEX_API_KEY.
• Primary tools included: watch_create, watch_test, watch_list.

Feature & Specification Comparison

Specification	Site Shot MCP site-shot Browser Automation	Rendex MCP copperline-labs Browser Automation
Summary	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.	Screenshot, PDF, and HTML rendering API for AI agents. Capture any URL or raw HTML as PNG/JPEG/WebP/PDF with batch processing, geo-targeting, async webhooks, and MCP-native integration. Free tier included.
Category & Scope

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "site-shot-site-shot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "site-shot-mcp"
      ],
      "env": {
        "SITESHOT_API_KEY": "YOUR_SITESHOT_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "copperline-labs-rendex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@copperline/rendex-mcp"
      ],
      "env": {
        "RENDEX_API_KEY": "YOUR_RENDEX_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons