Webshot Now Speaks MCP: Screenshots as a Tool for AI Agents

Webshot.site now speaks the Model Context Protocol. If you use Claude Desktop, Cursor, or anything else that talks MCP, your assistant can render a page and look at it directly — no copy-pasting URLs, no describing what you see. Point your client at it One line of config, no key, no signup: { "mcpServers": { "webshot": { "url": "https://webshot.site/mcp" } } } The endpoint is https://webshot.site/mcp, JSON-RPC 2.0 over HTTP POST. It exposes a single tool: capture_sandbox_webshot(url, viewport?, full_page?, format?) Ask your assistant to "take a screenshot of example.com and tell me what's above the fold" and it will call that tool, get back an image, and answer. Why it returns a link, not the image The obvious implementation is to base64 the PNG and hand it straight to the model. We deliberately don't. A modest screenshot is 25–200 KB, which becomes a wall of base64 in the model's context window and crowds out the actual conversation. Most