
TemplateFoxPDF
io.github.TemplateFoxPDFPublished by GitHub account TemplateFoxPDFv1.9.7Updated Oct 24, 2026
MCP server for TemplateFox PDF generation API - Generate PDFs from templates via AI assistants
Overview
TemplateFox PDF server that lets an AI assistant list templates, fill them with data and generate PDFs through the TemplateFox API.
- What you can do
- List available templates and inspect the fields each template requires before filling it in. Generate a PDF from a template with dynamic data, or queue an asynchronous generation job with an optional webhook. Check the status of async jobs and list past PDF generation jobs. Review account information, remaining credits and credit transaction history.
- When to use it
- Useful when you want an assistant to produce documents such as invoices or reports from existing TemplateFox templates without leaving the chat, or to check credits and job history for PDF generation.
- Requirements
- Runs locally as an npm package via npx or a global install, so Node.js is needed. Requires a TemplateFox account and the TEMPLATEFOX_API_KEY environment variable. An optional TEMPLATEFOX_BASE_URL can override the API endpoint. Network access to the TemplateFox API is required.
Installation
In SourceWeft
- Open TemplateFoxPDF in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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):
Claude Code
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)
Then use templatefox-mcp-server as the command instead of npx.
Configuration
Available Tools
Remote Server (HTTP)
The MCP server also supports HTTP transport via Streamable HTTP, suitable for remote and cloud deployments.
Connect via URL
MCP clients must pass the API key via HTTP header:
or:
Self-host
Run the server in HTTP mode by setting the PORT environment variable:
Or with Docker:
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
Source: README.md at commit 856fc82
Tools
0Version history
1- v1.9.7LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts