Mcp Pdf
Let your coding agent create PDFs on demand—reports, invoices, or export artifacts—without leaving the chat.
Overview
io.github.kmalakoff/mcp-pdf is a MCP server for the Build phase that generates PDF files for agents using PDFKit over stdio.
What is this MCP server?
- MCP server wrapping PDFKit for programmatic PDF generation
- Stdio transport for local Claude Code, Cursor, and Codex configs
- Published on npm as @mcp-z/mcp-pdf (registry v1.0.3)
- Lightweight integration—no browser or cloud PDF SaaS required
- Fits agent workflows that need receipts, specs, or one-off PDF exports
- Server version 1.0.3
- npm package @mcp-z/mcp-pdf
- Transport: stdio
Community signal: 1 GitHub stars.
What problem does it solve?
Agents can draft content easily but often cannot hand you a real PDF file without extra scripts or manual export steps.
Who is it for?
Indie builders automating invoices, one-pagers, or export PDFs from agent workflows during build and docs work.
Skip if: Teams that need collaborative WYSIWYG PDF design, e-signatures, or enterprise print pipelines without agent involvement.
What do I get? / Deliverables
After you add the server, your agent can call MCP tools to produce PDF artifacts you can save, email, or attach to releases.
- Binary PDF files produced via agent tool calls
- Repeatable PDF export step inside build or docs automation
- Fewer one-off Node scripts for simple PDF generation
Recommended MCP Servers
Journey fit
How it compares
MCP PDF generator integration, not a hosted document SaaS or a generic writing skill.
Common Questions / FAQ
Who is io.github.kmalakoff/mcp-pdf for?
Solo and indie builders using Claude Code, Cursor, or similar agents who need programmatic PDF output from chat-driven workflows.
When should I use io.github.kmalakoff/mcp-pdf?
Use it when you are in Build or docs work and want the agent to emit finished PDF files—not just markdown—without a separate export tool.
How do I add io.github.kmalakoff/mcp-pdf to my agent?
Install @mcp-z/mcp-pdf from npm, add an MCP stdio server entry pointing at the package binary, restart the agent, and confirm PDF tools appear in the tool list.