MCP overview

Imprime exposes an MCP server (Model Context Protocol). It is the richest way to work with Imprime programmatically: an AI agent can list your templates, design new ones, fill them with data and render the result.

Endpoint

https://app.imprime.io/api/mcp

• Transport: Streamable HTTP
• Self-hosted: <PUBLIC_APP_URL>/api/mcp

MCP or REST?

	MCP	REST API
Generate a PDF	✅ preview_template	✅ POST /export/{id}/pdf
List and read templates	✅	✅
Create and edit templates	✅ 26 tools — pages, shapes, variables	❌ design in the editor
Best for	AI agents, generating a template from a brief	Production pipelines, batch rendering

Tip

For a server that issues thousands of invoices, use the REST export endpoint: one request, one PDF, nothing to reason about. Use MCP when a human or an agent is designing the document.

Authentication

Two modes reach the same server:

Mode	Header	Best for
OAuth 2.1	Authorization: Bearer <token>	Interactive clients — the Claude custom connector
API key	x-api-key: <your-api-key>	Headless clients — Claude Code, scripts, your own agents

With OAuth, the client discovers everything by itself: you only paste the URL. With an API key, create one in Settings → API Keys and put it in the client config.

Note

Either way, the agent acts as you: it sees your templates, and only yours.

What agents can do

The server ships 26 tools covering the whole lifecycle — see the tools reference:

• Templates — list, read, create, duplicate, rename, delete
• Pages — add, move, duplicate, delete, set conditions and repeats
• Shapes — draw a whole page, add, update, move, copy, delete
• Variables — declare, update, delete
• Images and fonts — upload images, list available font families
• Preview — render the pages as images and get a shareable link

Connect a client

Claude (web & desktop)Add Imprime as a custom connector — OAuth, no key to copy.

Claude Code & other clientsConfigure the server with an API key in a JSON config.