Integration

PDFMonkey integration

PDFMonkey document generation API: render a stored template with a JSON payload into a PDF, either queued in the background or waited for in a single request, follow the generation through its status, download the produced file from a signed link, and manage the templates of the workspace. Generation is asynchronous by default, a document starting as pending and becoming success or failure. Requests authenticate with a bearer token.

Connect PDFMonkey How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common PDFMonkey use cases

diagnosing a failed generation
provisioning a template from code
adjusting the layout of an invoice
producing an invoice from order data
discovering the keys a template expects
waiting for a queued generation to finish
removing a template that is no longer used
rendering a draft once its data is complete
finding the identifier of a template by name
honouring a retention rule on generated documents

What you can do with PDFMonkey

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.

Document, 7 operations

create_documentCreate documentPOSTCreates a PDFMonkey document and queues its generation.
create_document_syncCreate document syncPOSTGenerates a PDFMonkey document and waits for the file in one request.
delete_documentDelete documentDELETEDeletes a PDFMonkey document together with its file.
get_documentGet documentGETReads a full document including the data it was rendered with and its generation logs.
get_document_cardGet document cardGETChecks the generation status of a document and reads its download link.
list_document_cardsList document cardsGETLists generated documents, filtered by template, status or date.
update_documentUpdate documentPUTUpdates a draft document and triggers its generation.

Template, 5 operations

create_templateCreate templatePOSTCreates a PDFMonkey template from markup and styles.
delete_templateDelete templateDELETEDeletes a PDFMonkey template.
get_templateGet templateGETReads a PDFMonkey template with its body, styles and sample payload.
list_template_cardsList template cardsGETLists the PDFMonkey templates of a workspace.
update_templateUpdate templatePUTUpdates the markup, styles or settings of a PDFMonkey template.

Use PDFMonkey from Claude Code, Cursor or Codex

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

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

PDFMonkey integration FAQ

What can you do with the PDFMonkey integration?

LiveContext exposes 12 operations on PDFMonkey, covering document and template. Common uses include diagnosing a failed generation, provisioning a template from code and adjusting the layout of an invoice.