Pdfnative MCP Server

PDF native MCP server: generate, validate, sign PAdES, embed, extract. AI-powered. The pdfnative mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

pdfnative-mcp exposes 24 production-grade tools to any MCP host:

• Zero runtime dependencies — — pure JavaScript, no native bindings
• ISO 32000-1 (PDF 1.7) — compliant output
• PDF/A-1b/2b/3b — , AES-128/256 encryption, AcroForm, digital signatures
• 16 Unicode scripts — with built-in BiDi reordering, Arabic positional shaping, Thai/Devanagari/Bengali/Tamil OpenType shaping
• Tree-shakeable ESM build

Its toolset

Everything the assistant can do here goes through one of these:

• verbosity — 'summary' — returns a compact scalar-only verdict (drops the heavy arrays / full text). E.g. verify_pdf → { signatureCount, allValid, invalid
• fields — ['a', 'b.c'] — projects the structured result to named dot-paths; composes after verbosity. Unknown paths are omitted leniently
• Tree — shakeable ESM build
• generate_basic_pdf — Multi-page A4 documents from structured blocks (headings, paragraphs, lists, page breaks). Embedded newlines auto-split into paragraphs. Optional
• add_barcode — QR Code, Code 128, EAN-13, Data Matrix, PDF417 — embedded in a single-page PDF
• add_international_text — 24 scripts (incl. Latin & COLRv1 colour emoji) with BiDi & OpenType shaping; multi-lang per document
• add_table — Tabular reports with smart fields (wrap, repeatHeader, zebra, caption, minRowHeight, cellPadding)
• add_form — Create a new interactive AcroForm PDF with text fields, checkboxes, radio buttons, dropdowns
• embed_image — Embed a JPEG or PNG image (base64) into a titled PDF document
• prepare_signature_placeholder — Step 1 of the two-step sign workflow — create a PDF with a /Sig AcroForm placeholder
• sign_pdf — Apply a PAdES-compatible CMS signature (RSA-SHA256 / ECDSA-SHA256 P-256). Auto-injects a placeholder when needed
• verify_pdf — Verify every PAdES signature in a PDF (integrity + signature value + optional chain trust)

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need one environment variable: PDFNATIVE_MCP_OUTPUT_DIR. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pdfnative's toolset — verbosity, fields, Tree and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Nizoka; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Pdfnative.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the pdfnative mcp server does with a few real requests.