MCP — Model Context Protocol

Let your AI agent generate invoices. You stay in control.

Connect Claude, ChatGPT, or any MCP-compatible agent to PDFox via OAuth. Your agent orchestrates. PDFox renders. Every template, every job, every token — scoped to your organization.

Claude
Get all overdue invoices for Acme Ltd from Stripe, then generate PDFs using our branded VAT invoice template.
Found 4 overdue invoices totalling £8,420. I'll generate PDFs using vat-invoice-v3.
Tool call pdfox.generate_pdf(template="vat-invoice-v3", batch=4)
job_8fK2n7Bq · 3 of 4 rendered
Invoice INV-2026-0431.pdf
job_8fK2n7Bq · 142 KB
Template · vat-invoice-v3 · Acme Ltd
4 PDFs
£8,420 total
2.1s render

How it works

From prompt to PDF in four steps

No custom integration code. No API key in the prompt. No layout work for the agent.

01

Connect with OAuth

Your AI agent requests access to your PDFox organization. You approve it from the dashboard. No API key sharing.

02

Use approved templates

The agent reads your published templates and their schemas — no access to drafts, settings, or billing.

03

Pull data from your tools

The agent fetches data from Stripe, your CRM, accounting exports, or whatever sources you've connected to it.

04

Generate, preview, download

PDFox renders the PDFs and returns signed download URLs. Every job is logged with a clear audit trail.

See it in action

One prompt. Branded PDFs. Full audit trail.

Watch the walkthrough

Agent generates 4 invoices from a single prompt

Example prompts

Stripe · batch

"Get all overdue invoices for Acme Ltd and generate PDFs using our branded invoice template."

Stripe · weekly

"Create invoice PDFs for every unpaid Stripe invoice this week."

CRM · single

"Use the VAT invoice template and generate a PDF for account X from the CRM data."

Draft · review

"Upload our logo, create a draft invoice template, validate it, and preview the PDF."

MCP tools

Seven tools. Nothing more.

The PDFox MCP surface is deliberately minimal. No bulk operations, no billing access, no user management.

list_templates

Enumerate approved templates the agent is allowed to use.

read
get_template_schema

Read field definitions, required values, and example payloads.

read
create_draft_template

Draft a new template for human review — never auto-published.

draft
upload_asset

Upload logos, fonts, and image assets to your asset library.

draft
generate_pdf

Render a PDF from an approved template plus a data payload.

write
get_job_status

Poll job state — queued, rendering, complete, failed.

read
download_pdf

Get a signed, time-limited URL for the generated PDF.

read

No publishing tool exists

Agents can prepare and validate template drafts, but there is no MCP method to publish a template. That action only exists behind a human review gate in the dashboard.

Why MCP

The agent handles the orchestration. PDFox handles the rendering.

AI agents are good at deciding what data belongs in a document. They are not the right tool for applying a brand, managing page breaks, or enforcing a layout that your design team approved last quarter.

With MCP, the agent identifies what to generate and hands off the data. PDFox applies the template — including fonts, spacing, tables, and headers — exactly as your designers defined it.

Template changes flow through your normal review process. The agent never touches layout. Every document you issue looks like every other one.

AI agent
  • Reads data sources
  • Selects the right template
  • Assembles the payload
  • Returns the download link
MCP tool call
PDFox
  • Applies the brand template
  • Handles layout rules
  • Renders to PDF
  • Logs the job with full audit

Data sources

PDFox renders it. Your agent brings the data.

PDFox does not pull data from external systems. Your agent does — from whatever sources it is already authorized to access.

Stripe invoices

Pull paid, unpaid, and overdue Stripe invoices from connected tools your agent can access.

via your agent's Stripe integration

CRM accounts

Account, contact, and order data from approved CRM workspaces, mapped onto your template fields.

Salesforce · HubSpot · Attio

Accounting exports

Line items and tax data from accounting exports the agent has been authorized to read.

Xero · QuickBooks · CSV

Spreadsheets

A simple sheet of customers and amounts becomes a batch of branded PDFs, in one prompt.

Google Sheets · Excel

Internal databases

Production databases or warehouses the agent can query through your data-access layer.

Postgres · BigQuery · Snowflake

Support & sales tools

Hand off from a support ticket or sales conversation directly into document generation.

Linear · Zendesk · Slack

Security and control

Your organization stays in control at every step.

MCP authorization in PDFox is designed around the principle that agents should do less, not more.

OAuth authorization

Agents request access through standard OAuth. Tokens are short-lived, revocable, and tied to a single agent install.

Organization-scoped access

Each connection is bound to one PDFox organization. No cross-tenant access, ever.

Scoped permissions

Pick exactly which actions an agent can take: read templates, generate PDFs, draft new ones — or read-only.

Draft-only template creation

Agents can prepare new templates and upload assets, but cannot push them live.

No publishing by agents

There is no MCP tool for publishing. That action only exists in the dashboard, behind human approval.

Audit-friendly job history

Every PDF generation is recorded with the agent, user, template, payload digest, and timestamp.

Use cases

Where teams are using this today

Overdue invoice batches

Generate dunning-ready PDFs for every overdue invoice in one prompt.

ops · finance

Account-specific invoices

Generate a single invoice for a named account, pulled live from CRM.

support · sales

Branded PDFs from CRM data

Map CRM fields onto your branded template in seconds.

ops

Finance team workflows

Month-end batches, VAT invoices, credit notes — without manual layout.

finance

Developer-led automation

Wire MCP into an internal copilot to standardize document generation across teams.

engineering

FAQ

Common questions

Have a different question? Read the docs or contact us.

MCP — the Model Context Protocol — is an open standard for letting AI assistants call external tools in a structured, authenticated way. A PDFox MCP server exposes a small set of document-generation tools that AI agents like Claude or ChatGPT can use on your behalf.

Yes. Any MCP-compatible AI agent — including Claude, ChatGPT, and Cursor — can connect to PDFox through OAuth, read your approved templates, and generate branded PDFs from data you supply. PDFox handles the rendering; the agent handles the orchestration.

No. Agents only see templates that have been explicitly published in your PDFox organization and are within the scopes you authorize. Drafts, archived templates, and templates in other workspaces are not visible to the agent.

No. Agents can prepare draft templates and upload assets through MCP, but publishing is a dashboard-only action that requires a human reviewer. There is no MCP tool that maps to publish.

Any source your AI agent already has access to — Stripe, your CRM, accounting exports, spreadsheets, internal databases, or support and sales tools. PDFox doesn't pull data itself; the agent assembles the payload and hands it to PDFox to render.

No. The agent connects through OAuth and receives short-lived, organization-scoped tokens. You can revoke access from the PDFox dashboard at any time, and you never paste an API key into a prompt or a tool config.

Yes. Every successful job returns a signed, time-limited URL to the rendered PDF. The agent can return that link directly, attach it to a message, or hand it off to another tool in the workflow.

Your agent is three OAuth steps away from generating invoices.

Free tier. No credit card. Revoke access at any time from the dashboard.