
Mcp Server
- Updated July 12, 2026
- TemplateFoxPDF/mcp-server
TemplateFox MCP is a MCP server that generates PDFs from TemplateFox templates via the hosted API for AI assistants.
About
TemplateFox MCP is a stdio Model Context Protocol server that lets Claude Code, Cursor, and similar agents create PDFs through the TemplateFox hosted API using predefined templates. developers adopt it when contracts, reports, onboarding packets, or customer PDFs must be produced programmatically during development without maintaining a custom LaTeX or headless Chrome pipeline. The server is versioned at 1.9.7 in the MCP registry schema and wraps the @templatefox/mcp-server npm identifier with a mandatory TEMPLATEFOX_API_KEY. It complements frontend work by moving repeatable document fills to agent-invoked tools. Expect API quotas and template design on the TemplateFox side; the MCP layer focuses on reliable tool exposure for generation requests.
- Bridges TemplateFox PDF generation API to MCP clients
- npm package @templatefox/mcp-server (schema v1.9.7)
- Requires TEMPLATEFOX_API_KEY for authenticated generation
- stdio transport for local agent configuration
- GitHub: TemplateFoxPDF/mcp-server
Mcp Server by the numbers
- Data as of Jul 13, 2026 (Skillselion catalog sync)
claude mcp add --env TEMPLATEFOX_API_KEY=YOUR_TEMPLATEFOX_API_KEY mcp-server -- npx -y @templatefox/mcp-serverAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | @templatefox/mcp-server |
|---|---|
| Transport | STDIO |
| Auth | Required |
| Last updated | July 12, 2026 |
| Repository | TemplateFoxPDF/mcp-server ↗ |
What it does
Generate PDFs from TemplateFox templates inside the agent for proposals, invoices, or user-facing downloads.
Who is it for?
Best when you already use TemplateFox templates and want PDF generation as MCP tools in Claude Code or Cursor.
Skip if: Skip if you need fully offline PDF rendering, arbitrary HTML-to-PDF without TemplateFox, or no API budget.
What you get
Your agent can trigger TemplateFox template renders so PDF deliverables ship with the rest of the build workflow.
- PDF files generated from TemplateFox templates on agent request
- Automated document step in build or ops runbooks
By the numbers
- Registry server schema version 1.9.7
- npm identifier @templatefox/mcp-server
README.md
TemplateFox 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
Recommended MCP Servers
How it compares
Template API bridge over MCP, not a local Pandoc or browser-print skill.
FAQ
Who is TemplateFox MCP for?
Developers who generate customer or internal PDFs from TemplateFox templates through their coding agent.
When should I use TemplateFox MCP?
Use it during Build docs work when proposals, invoices, or export PDFs should be created via API tools mid-session.
How do I add TemplateFox MCP to my agent?
Install @templatefox/mcp-server, register stdio MCP in your client, and set TEMPLATEFOX_API_KEY.