Pdfco
Hook PDF.co into your agent so you can extract, convert, edit, and OCR-parse PDFs while building features that ingest contracts, invoices, or spec PDFs.
Overview
com.mcparmory/pdfco is an MCP server for the Build phase that extracts, edits, converts, and AI-parses PDF documents through PDF.co.
What is this MCP server?
- Extract structured data from PDFs with OCR and AI-assisted parsing
- Convert and edit PDF documents via MCP tools
- stdio server 1.0.2 installable through uvx mcparmory-pdfco or Docker
- Supports agent-driven document pipelines without custom PDF SDK glue
- Pairs with backends that accept uploads or generate downloadable reports
- Server version 1.0.2
- 2 distribution channels: PyPI uvx and OCI Docker
- Transport: stdio
Community signal: 25 GitHub stars.
What problem does it solve?
Building PDF ingest or export means writing brittle scripts and juggling PDF.co docs while your agent could handle transforms if it had MCP access.
Who is it for?
Indie SaaS builders integrating PDF uploads, OCR, or report generation who already use or plan to use PDF.co.
Skip if: Projects with no PDF processing needs or teams that require fully offline, air-gapped document handling only.
What do I get? / Deliverables
After you add the server, your agent can run PDF.co extract, convert, edit, and OCR operations inside your development workflow.
- MCP tools for PDF extract, convert, edit, and parse workflows
- Faster agent-assisted document feature prototyping
- Reduced custom scripting against PDF.co REST endpoints
Recommended MCP Servers
Journey fit
Build is canonical because PDF manipulation usually appears when implementing document pipelines or parsing user-uploaded files, not during pure ideation or post-launch growth. Docs subphase covers document-centric product work—parsing specs, generating PDFs, and transforming files agents and users depend on.
How it compares
PDF.co document MCP integration, not a local open-source PDF library skill or a generic file-storage connector.
Common Questions / FAQ
Who is com.mcparmory/pdfco for?
It is for developers building document features who want MCP agents to call PDF.co for extract, convert, edit, and OCR tasks.
When should I use com.mcparmory/pdfco?
Use it during Build when you implement PDF pipelines, parse uploaded documents, or generate PDF outputs via your agent.
How do I add com.mcparmory/pdfco to my agent?
Register stdio MCP with uvx mcparmory-pdfco or the ghcr.io/mcparmory/pdfco image and set your PDF.co API key in the client environment.