Mcp Server
Generate PDFs from TemplateFox templates inside the agent for proposals, invoices, or user-facing downloads.
Overview
TemplateFox MCP is a Build-phase MCP server that generates PDFs from TemplateFox templates via the hosted API for AI assistants.
What is this MCP server?
- 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
- Registry server schema version 1.9.7
- npm identifier @templatefox/mcp-server
What problem does it solve?
Hand-rolling PDF pipelines slows shipping when you only need template-filled documents from the agent.
Who is it for?
Indie SaaS builders who already use TemplateFox templates and want PDF generation as MCP tools in Claude Code or Cursor.
Skip if: Teams needing fully offline PDF rendering, arbitrary HTML-to-PDF without TemplateFox, or no API budget.
What do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
How it compares
Template API bridge over MCP, not a local Pandoc or browser-print skill.
Common Questions / FAQ
Who is TemplateFox MCP for?
Solo builders 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.