Integration

CloudFill integration

CloudFill fills PDF templates (fillable forms uploaded in the CloudFill app) with text and images and returns a link to the generated PDF. List the account's PDF templates, read a template's variable and field names, then generate a filled PDF; each generation spends account credits (10 per PDF plus 1 per image, from the monthly allowance of the Mini, Plus or Business plan). Uploading templates and placing placeholders stay in the CloudFill app. Authentication is the account's API key sent in the X-API-Key header.

Connect CloudFill How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with CloudFill

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.

generate_pdfGenerate pdfPOSTGenerates a real PDF from a template and returns its download URL; spends 10 credits per PDF plus 1 per image. Get variable and field keys from get_pdf_details first.
get_pdf_detailsGet pdf detailsGETReturns a PDF template's text variables and form fields (key, label, field type). Use the variable keys in generate_pdf variables and Image field keys in images.
list_pdfList pdfGETLists the PDF templates in the CloudFill account with their key, file name and creation time. Pass a key as pdfKey to get_pdf_details or generate_pdf.

Use CloudFill from Claude Code, Cursor or Codex

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

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