DicePDF
Merge, split, extract, render, and compress PDFs from your agent with DicePDF’s local-first MCP—files never leave the machine.
Overview
DicePDF is a MCP server for the Build phase that provides local-first merge, split, extract, render, and compress tools for PDF files via agents.
What is this MCP server?
- npm package @dicepdf/mcp v0.1.0 with stdio transport
- Local-first pipeline: merge, split, extract, render, compress without cloud upload
- Suited to confidential contracts, invoices, and pitch PDFs on a solo laptop
- Monorepo subfolder packages/mcp; marketing site dicepdf.com
- Privacy posture: processing stays on-device per server description
- Version 0.1.0 npm identifier @dicepdf/mcp
- Five advertised capabilities: merge, split, extract, render, compress
- stdio transport; repository subfolder packages/mcp on github.com/ishan-maheshwari/free-pdf
What problem does it solve?
Builders waste time leaving the IDE to merge, split, or compress PDFs—and cloud tools leak sensitive client documents.
Who is it for?
Solo builders automating PDF prep for proposals, docs, or content pipelines who require on-device processing.
Skip if: Teams needing collaborative cloud PDF editors, OCR-at-scale SaaS, or server-side batch farms without a local agent host.
What do I get? / Deliverables
After registration, your agent manipulates PDFs on disk locally while you stay in one privacy-preserving workflow.
- Merged, split, extracted, rendered, or compressed PDF outputs on local filesystem
- Agent-repeatable PDF workflows without cloud transfer
- Stdio MCP registration for DicePDF tools
Recommended MCP Servers
Journey fit
Document manipulation is part of building deliverables—contracts, exports, onboarding packets—while you wire agent workflows. Agent-tooling is the right shelf because the value is MCP tools that extend what your coding agent can do to PDFs on disk.
How it compares
Local PDF toolkit MCP—not a hosted DocuSign or Notion export integration.
Common Questions / FAQ
Who is DicePDF for?
Indie developers and content builders who want their AI agent to handle PDF merge, split, extract, render, and compress locally.
When should I use DicePDF?
Use it while building docs, onboarding kits, or downloadable assets when files must stay on your machine and you want agent-driven batch steps.
How do I add DicePDF to my agent?
Install @dicepdf/mcp from npm (0.1.0), add a stdio MCP server entry in Claude Code, Cursor, or Codex, and grant the agent access to PDF paths on disk.