Integration

pdfrender integration

pdfrender turns an HTML and CSS document into a PDF with WeasyPrint, hosted in Germany: page size, margins, headers, footers and page numbers come from CSS @page rules, images and fonts are inlined as data: URIs, and no JavaScript runs. Render a PDF (returned as a file) and check your plan, remaining requests and credits; the vendor's MCP endpoint and health check are not exposed. Authentication is an API key created after signing in at pdfrender.dev, sent in the X-API-Key header; a missing or wrong key is not refused, the call then runs anonymously at 10 renders a day per IP address (get_account_status shows is_keyed).

Connect pdfrender How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in pdfrender.Built from the 2 pdfrender tools below, on the connection you add once.

What you can do with pdfrender

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Account, 1 operation

get_account_statusGet account statusGETAgents: ask firstReturns the plan the API key runs on, whether the key was recognized, the requests left in the current rate-limit window, the credits left this billing period and the plan's features. Free: this call costs no credit and no request.

Pdf, 1 operation

render_html_to_pdfRender html to pdfPOSTAgents: ask firstRenders one HTML document (up to 2 MB, 50 pages) to a PDF, returned as a stored file. Billed: after the day's 10 free renders, 1 credit per successful render. External URLs are refused (inline assets as data: URIs); no JavaScript runs.

Use pdfrender from Claude Code, Cursor or Codex

Connect pdfrender in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its pdfrender operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect pdfrender

Create your workspace
Sign up free. Nothing to install.
Connect pdfrender once
Add your pdfrender connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.