Oxidize Pdf MCP Server
Let your agent generate, merge, split, and parse PDFs for specs, invoices, and deliverables without leaving the MCP session.
Overview
io.github.bzsanti/oxidize-pdf-mcp is an MCP server for the Build phase that generates and manipulates PDFs through oxidize-pdf tools.
What is this MCP server?
- oxidize-pdf MCP server v0.8.0 via PyPI oxidize-pdf with uvx runtime hint
- PDF generation, parsing, splitting, merging, and broader manipulation
- stdio transport; positional argument oxidize-mcp entrypoint
- Rust-backed oxidize-pdf stack exposed to agents for repeatable document workflows
- Server and package version: 0.8.0
- PyPI identifier: oxidize-pdf
- Runtime hint: uvx
What problem does it solve?
Agents cannot reliably produce or refactor PDF deliverables when document work is stuck outside the MCP toolchain.
Who is it for?
Solo builders automating invoices, spec exports, and internal PDF utilities while building SaaS or content products.
Skip if: Teams that need interactive PDF editors, legally binding e-signatures, or enterprise OCR-only pipelines without oxidize-pdf.
What do I get? / Deliverables
Your agent can merge, split, parse, and generate PDFs inside the same session where it writes the product code and docs.
- Agent-accessible PDF create, parse, split, and merge operations
- Repeatable document transforms tied to build and docs tasks
- Versioned oxidize-pdf MCP server at catalog 0.8.0
Recommended MCP Servers
Journey fit
How it compares
MCP PDF manipulation server, not a LaTeX or Google Docs authoring skill.
Common Questions / FAQ
Who is io.github.bzsanti/oxidize-pdf-mcp for?
Developers using MCP clients who want oxidize-pdf-powered PDF create and transform tools beside their codebase.
When should I use io.github.bzsanti/oxidize-pdf-mcp?
Use it during Build docs and backend work when you need generated, split, or merged PDFs as part of features or exports.
How do I add io.github.bzsanti/oxidize-pdf-mcp to my agent?
Register the oxidize-pdf PyPI package with uvx, stdio transport, and the oxidize-mcp positional entry as documented in server.json.