About TemplateFoxPDF
TemplateFoxPDF connects AI assistants to the TemplateFox PDF generation API, letting them create PDFs from templates and dynamic data. Its tools also cover template fields, asynchronous jobs, and account credits.
Key features
- 01Generate PDFs from templates
- 02Queue asynchronous PDF jobs
- 03Check and list PDF jobs
- 04List templates and inspect fields
- 05View account credits and transactions
Use cases
- 01Create a PDF using template data
- 02Check the status of queued PDF generation
MCP support
Exposes TemplateFox API operations as MCP tools, including PDF generation, template discovery, job tracking, and account information. Supports stdio configuration and Streamable HTTP connections.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @templatefox/mcp-serverTEMPLATEFOX_API_KEYSecretYour TemplateFox API keyLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
8Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| data | object | Yes | Key-value data to render in the template. Keys must match template variables. |
| filename | string | No | Custom filename for the PDF (without .pdf extension). If not provided, defaults to 'document'. Only applies to `url` export type. |
| store_s3 | boolean | No | Upload to your configured S3 bucket instead of CDN |
| s3_bucket | string | No | Override the default bucket configured in your S3 integration. |
| expiration | integer | No | URL expiration in seconds. Min: 60 (1 min), Max: 604800 (7 days). Only applies to `url` export type. |
| export_type | enum | No | Export format: `url` uploads to CDN and returns URL, `binary` returns raw PDF bytesurl | binary |
| pdf_variant | enum | No | Generate a standards-compliant PDF variant. Use `pdf/a-3b` for archival compliance (most common). Use `pdf/a-3b` if you need file attachments (e.g. Factur-X). When not set, a standard PDF is generated.pdf/a-1b | pdf/a-2b | pdf/a-3b |
| s3_filepath | string | No | Custom path prefix in your S3 bucket. Uses default prefix if not provided. |
| template_id | string | Yes | Template short ID (12 characters) |
Details
From the project READMETemplateFox MCP Server
MCP (Model Context Protocol) server for the TemplateFox PDF generation API. Generate PDFs from templates directly through AI assistants like Claude, Cursor, and Windsurf.
Installation
Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"templatefox": {
"command": "npx",
"args": ["-y", "@templatefox/mcp-server"],
"env": {
"TEMPLATEFOX_API_KEY": "sk_your_api_key_here"
}
}
}
}
Claude Code
claude mcp add templatefox -- npx -y @templatefox/mcp-server
Then set the environment variable TEMPLATEFOX_API_KEY in your shell.
Cursor / Windsurf
Use the same npx -y @templatefox/mcp-server command in your MCP server configuration, with TEMPLATEFOX_API_KEY in the environment.
Global Install (alternative)
npm install -g @templatefox/mcp-server
Then use templatefox-mcp-server as the command instead of npx.
Configuration
| Environment Variable | Required | Description |
|---|---|---|
TEMPLATEFOX_API_KEY | Yes | Your API key (starts with sk_). Get one at app.templatefox.com/dashboard/api-keys |
TEMPLATEFOX_BASE_URL | No | Override API base URL (default: https://api.templatefox.com) |
Available Tools
| Tool | Description |
|---|---|
generate_pdf | Generate a PDF from a template with dynamic data (1 credit) |
generate_pdf_async | Queue async PDF generation with optional webhook (1 credit) |
get_pdf_job_status | Check the status of an async PDF job |
list_pdf_jobs | List async PDF generation jobs |
list_templates | List all available templates |
get_template_fields | Get the fields/variables for a template |
get_account_info | Check remaining credits and account info |
list_transactions | View credit transaction history |
Remote Server (HTTP)
The MCP server also supports HTTP transport via Streamable HTTP, suitable for remote and cloud deployments.
Connect via URL
https://mcp-server-599407781746.us-central1.run.app/mcp
MCP clients must pass the API key via HTTP header:
Authorization: Bearer sk_your_api_key_here
or:
x-api-key: sk_your_api_key_here
Self-host
Run the server in HTTP mode by setting the PORT environment variable:
PORT=8080 TEMPLATEFOX_API_KEY=sk_your_key node dist/index.js
Or with Docker:
docker build -t templatefox-mcp .
docker run -p 8080:8080 templatefox-mcp
The MCP endpoint is available at http://localhost:8080/mcp and a health check at http://localhost:8080/health.
Example Usage
Once configured, you can ask your AI assistant:
"List my PDF templates and generate an invoice using the Invoice Template with customer name 'John Doe' and amount 150.00"
The assistant will:
- Call
list_templatesto find available templates - Call
get_template_fieldsto discover required fields - Call
generate_pdfwith the template ID and data - Return the PDF download URL
Links
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.