MCP PDF Server
Let your agent turn URLs, HTML, or components into PDFs. The RenderKit MCP server exposes the PDF primitive as a callable tool for Claude, Cursor, and other MCP clients.
Let your agent turn URLs, HTML, or components into PDFs. The RenderKit MCP server exposes the PDF primitive as a callable tool for Claude, Cursor, and other MCP clients. 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/pdf \
-H "x-api-key: $RENDERKIT_API_KEY" \
-H "content-type: application/json" \
-d '{ "url": "https://example.com", "format": "A4", "print_background": true }'What the agent gets
- pdf tool callable from any MCP client
- URL, HTML, or JSX source with print CSS
- Returns a signed PDF URL
- Archive sources for compliance trails
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 pdf 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.