Agentic AI

PDFox runs a remote Model Context Protocol (MCP) server at https://api.pdf-fox.com/mcp. AI agents connect with OAuth, then find templates, author drafts, upload assets and generate PDFs for the organisation you approved.

What is MCP?

The Model Context Protocol is an open standard for giving AI assistants access to external tools. An MCP server exposes a set of typed tools; a compatible client (Claude, ChatGPT, Cursor, VS Code Copilot and others) calls them as it works on your request.

What PDFox exposes via MCP

Tool	What it does
`list_templates`	List templates in the organisation
`get_template`	Fetch template metadata with its schema and sample JSON
`get_template_schema`	Fetch the schema and sample JSON to shape generation data
`get_template_draft`	Fetch the editable draft HTML, CSS, schema and sample JSON
`get_template_language_guide`	Read the PDFox template authoring guide
`list_template_helpers`	List the whitelisted Handlebars helpers
`create_template_draft`	Create a new unpublished template
`update_template_draft`	Update a template draft
`validate_template_draft`	Check a draft for Handlebars and schema errors
`preview_template_draft`	Render a draft to HTML
`preview_template_pdf`	Render a draft to a PDF preview
`list_assets`	List logos, images and fonts with their render paths
`upload_asset`	Upload a logo, image or font
`generate_pdf`	Queue a PDF job and return the job ID
`generate_pdf_and_wait`	Queue a job and wait up to 120 s, returning the PDF
`get_job`	Check the status of a job
`list_jobs`	List recent jobs
`get_job_events`	Read a job's event history
`download_pdf`	Return the PDF for a completed job
`get_pdf_quota`	Return remaining credits and limits
`get_usage_history`	Return daily generation counts

MCP isn't tied to a plan. Access depends on your role in the organisation: owners and admins can grant every scope, editors and billing admins can approve read-only access, and viewers can't connect agents. Agents can't publish templates; a person publishes from the dashboard.

How it works end-to-end

Connect your agent

Follow Connect an agent to add the PDFox MCP URL to your client and approve the OAuth connection.

Agent lists templates

The agent calls list_templates to find a template, then get_template_schema to learn the data it expects.

Agent generates a PDF

The agent maps your data to the schema and calls generate_pdf_and_wait. When the job completes, it gets the PDF as an embedded resource plus a downloadUrl that opens in a browser signed in to PDFox.

Agent uses the PDF

The client can save the file, share the link, or pass the PDF to another connector. If the job takes longer than the wait, the agent polls get_job and then calls download_pdf.

Next steps

Connect an agent — setup for Claude, Cursor and VS Code
MCP tools reference — full parameter docs for every tool
Template drafts via MCP — let agents create and edit templates
Template assets via MCP — list and upload logos, images and fonts