Pdf MCP Server

Pdf MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Renders letters as print ready PDFs, DIN 5008 compliant for German window envelopes.

What you get

Local MCP server (stdio) that turns structured letter data into a print ready PDF. One fixed layout, the everyday German letter, with the recipient address positioned per DIN 5008 so it sits exactly in the window of DL and C6/C5 window envelopes. No web service, no external API, everything runs offline on your machine.

• One layout, no variants: return address line, recipient, right aligned "place, date", bold subject block with references below it, salutation, body, closing, signature, enclosures
• Address field 45 mm high ending at 105 mm from the left, with return address line, remark zone (Einschreiben, Nicht nachsenden) and address zone
• Return address, remarks and recipient are balanced inside the address field, so the block sits evenly in the envelope window and further address lines still fit. addressLayout: "din" switches back to the fixed zone boundaries
• Page breaks keep closing, signature image, name and enclosures together, follow-up pages carry recipient, date and page number
• Subject 33 mm below the address field, place and date three lines above it
• Fold marks at 105 mm and 210 mm, punch mark at 148.5 mm

What the assistant can call

Once Pdf is connected, these are the calls the assistant has available:

• create_letter — Renders the letter and writes the PDF. Returns path, page count, layout metrics and warnings
• preview_letter — Same rendering without writing a file, for checking the layout
• prepare_signature — Cleans a scanned signature (crop, transparent background, ink colour) and writes a PNG
• get_din5008_spec — Returns the millimetre geometry of a form
• list_locales — Lists the supported languages and their fixed texts
• list_fonts — Lists built-in families and resolves a font name against the installed system fonts
• Signature — 1. Pass the file directly: signature.path plus trim and removeBackground. The scan is cleaned on every render. 2. Clean it once with

Configuration and credentials

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

Setting it up

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pdf's toolset — create_letter, preview_letter, prepare_signature and 4 more — is a fair guide to whether it matches your workflow. It is maintained by bitterdev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the pdf mcp server does with a few real requests.