Pdf Toolkit Mcp
Let agents merge, split, compress, OCR, convert, watermark, and protect PDFs through iLoveAPI without bolting on separate CLI scripts.
Overview
pdf-toolkit-mcp is a MCP server for the Build phase that exposes merge, split, compress, OCR, convert, watermark, and protect PDF operations through the iLoveAPI.
What is this MCP server?
- Broad PDF ops: merge, split, compress, OCR, convert, watermark, protect, and related toolkit actions via iLoveAPI
- Requires iLoveAPI project public and secret keys; secret signs short-lived JWTs locally
- Optional ILOVEAPI_SANDBOX_ROOT confines all file I/O to one directory
- npm package pdf-toolkit-mcp v0.1.2 with stdio transport
- Unofficial community bridge—not a first-party iLovePDF MCP
- Version 0.1.2
- stdio npm package pdf-toolkit-mcp
- 2 required secret env vars for iLoveAPI project keys
What problem does it solve?
Agents and solo builders keep reimplementing PDF utilities or manual iLoveAPI calls instead of standardized MCP tools with optional path sandboxing.
Who is it for?
Builders shipping document-heavy SaaS, internal ops tools, or content pipelines who already use or can adopt iLoveAPI credits.
Skip if: Teams that need official vendor support only, zero third-party PDF cloud processing, or simple static PDF hosting with no manipulation.
What do I get? / Deliverables
Your agent can run iLoveAPI-backed PDF transformations from the repo with keys configured once and optional filesystem sandboxing.
- Agent-callable PDF merge, split, compress, OCR, convert, watermark, and protect flows
- Optional sandboxed file I/O under ILOVEAPI_SANDBOX_ROOT
- JWT-signed iLoveAPI requests without embedding long-lived tokens in prompts
Recommended MCP Servers
Journey fit
Document PDF pipelines are built into products and agent workflows during implementation, not during initial idea research. Integrations fits because the server wraps iLoveAPI as MCP tools your agent calls from the dev environment.
How it compares
iLoveAPI-powered PDF MCP tools, not an in-repo Pandoc skill or browser-only PDF viewer.
Common Questions / FAQ
Who is io.github.EigenCharlie/pdf-toolkit-mcp for?
Solo builders who want Claude Code or Cursor agents to manipulate PDFs via iLoveAPI through a local stdio MCP server.
When should I use io.github.EigenCharlie/pdf-toolkit-mcp?
During Build when your product or agent workflow needs automated merge, OCR, compression, or protection of PDFs on developer machines or CI-adjacent flows.
How do I add io.github.EigenCharlie/pdf-toolkit-mcp to my agent?
Install pdf-toolkit-mcp from npm, set ILOVEAPI_PROJECT_PUBLIC_KEY and ILOVEAPI_PROJECT_SECRET_KEY, optionally ILOVEAPI_SANDBOX_ROOT, and register the stdio server in your MCP client.