Guides
17 hands-on guides covering onboarding, AI integration, designing for PDF, and operating Transactional at scale. Pick a category, or use the search above.
Getting started
From zero to your first PDF.
AI assistants & MCP
Connect Claude, Cursor, ChatGPT, or Gemini to your templates.
Use Transactional from your AI assistant
Connect Transactional to Claude, Cursor, ChatGPT, or Gemini via MCP so your assistant can read your templates and generate PDFs directly.
Claude Desktop
Connect Transactional to Claude Desktop on macOS or Windows so Claude can read your templates and generate PDFs.
Claude Code (CLI)
Connect Transactional to Claude Code so it can read your templates and generate PDFs from your terminal.
Cursor
Wire Transactional into Cursor's MCP support so you can generate PDFs from inside your editor.
ChatGPT (via Custom GPT Actions)
ChatGPT doesn't speak MCP natively yet — but you can give it the same powers through a Custom GPT pointed at the Transactional REST API.
Gemini Code Assist / Gemini CLI
Connect Transactional to Google's Gemini agents through their MCP support.
MCP tools reference
Every tool the Transactional MCP server exposes, with arguments, return shapes, and a prompt that typically triggers each one.
Integrations
Call /v1/generate from your stack — Node, PHP, Python.
Calling /v1/generate from Node.js & Bun
Production-grade integration using native fetch — retries, error handling, streaming the PDF to your storage.
Calling /v1/generate from PHP & Laravel
cURL extension, Guzzle, or Laravel's HTTP client — render PDFs with retries and proper error handling.
Calling /v1/generate from Python
urllib (stdlib), requests, or httpx with retry — render PDFs from Django, FastAPI, or any Python service.
Operations
Monitor usage, store and serve PDFs at scale.