MCP Screenshot Server
Give Claude, Cursor, or any MCP client native screenshot powers. The RenderKit MCP server exposes the screenshot primitive as a tool your agent calls directly — no glue code.
Give Claude, Cursor, or any MCP client native screenshot powers. The RenderKit MCP server exposes the screenshot primitive as a tool your agent calls directly — no glue code. The renderkit-mcp server installs in one config block and exposes all three render primitives as tools — your agent screenshots, archives, and reads pages without leaving the conversation.
Add it to your MCP client
{
"mcpServers": {
"renderkit": {
"command": "npx",
"args": ["renderkit-mcp"],
"env": { "RENDERKIT_API_KEY": "your-key" }
}
}
}Under the hood — the REST call it wraps
curl https://api.renderkit.tech/v1/screenshot \
-H "x-api-key: $RENDERKIT_API_KEY" \
-H "content-type: application/json" \
-d '{ "url": "https://example.com", "full_page": true, "block_ads": true }'What the agent gets
- screenshot tool available to any MCP client
- Full-page or element capture, ad/banner blocking
- Returns a signed image URL the agent can reason over
- Same server also exposes pdf and extract tools
More
See the MCP server overview, or the underlying screenshot, PDF, and markdown APIs.
Common questions
Install the RenderKit MCP server (npx renderkit-mcp) and add it to your MCP client config. The screenshot tool becomes available to Claude, Cursor, or any MCP-compatible agent.
Yes — renderkit-mcp implements the Model Context Protocol, so any MCP client (Claude Desktop, Cursor, custom agents) can use its tools.
Ship your first render in 60 seconds.
500 free renders to start. No card. Cancel by ignoring it.