Integration

PDF-API.io integration

PDF-API.io generates PDF documents from templates designed in its WYSIWYG or HTML editor. List templates and read the variables each one expects, render a template filled with your data into a PDF file (or a download link valid 15 minutes), and merge several filled templates into one PDF. Creating or editing templates and managing webhooks happen in the PDF-API.io web app, not through this API. Rate limit 60 requests per minute; renders count toward the plan's monthly quota. Authentication is an API token created on the API Tokens page, sent as a Bearer token.

Connect PDF-API.io How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in PDF-API.io.Built from the 6 PDF-API.io tools below, on the connection you add once.

What you can do with PDF-API.io

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.

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

Pdf, 4 operations

merge_templatesMerge templatesPOSTFills several templates, each with its own data, and combines them in order into one PDF, returned as a stored file for a later node. Use merge_templates_to_url for a temporary link instead.
merge_templates_to_urlMerge templates to urlPOSTFills several templates with their data, merges them in order into one PDF and returns a download link to it in data, valid 15 minutes. Same as merge_templates, which returns the file itself.
render_templateRender templatePOSTFills a template with data and returns the generated PDF as a stored file for a later node. Each PDF counts toward the plan's monthly PDF allowance. Use render_template_to_url for a temporary link instead.
render_template_to_urlRender template to urlPOSTFills a template with data and returns a download link to the generated PDF (url), valid 15 minutes, then deleted. Same as render_template, which returns the file itself. Counts toward the monthly PDF allowance.

Template, 2 operations

get_templateGet templateGETReturns one template with its name, team, type, creation date, metadata and the variables it expects, so you know which keys to send in data to render_template.
list_templatesList templatesGETLists every template of the account with its id, name, type, creation date, metadata and expected variables. Use the id as templateId and the variable names as data keys for render_template.

Use PDF-API.io from Claude Code, Cursor or Codex

Connect PDF-API.io in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its PDF-API.io 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 PDF-API.io

Create your workspace
Sign up free. Nothing to install.
Connect PDF-API.io once
Add your PDF-API.io 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.