CASOON Open Source

Typst in, PDF out.

typstgen compiles .typ files to PDF with the Typst engine built in: no typst binary, no subprocess, and templates found through a config file instead of hardcoded paths. From the shell, from Rust, in the browser or from your AI agent.

cargolibraryMCP

cargo install typstgen

cargo add typstgen --no-default-features

claude mcp add typstgen -- typstgen mcp --root .

Terminal: grep template_paths typstgen.toml prints template_paths = ["templates"]. typstgen compile letter.typ prints letter.pdf. typstgen compile missing-import.typ fails with 'error: typst compilation failed: missing-import.typ:2:9: error: file not found (searched at /footer.typ)', and echo $? prints 1.

The top of letter.pdf as compiled: the sender line of the letterhead, the recipient Ada Example, the date 14 September 2026, the subject 'Your quote request' and a price table with a total of € 1,800. — letter.pdf, page 1

MITcrates.io 0.6.2Rust 1.92+Typst 0.15

Who it is for

Teams generating letters, invoices and reports
Your layouts live in Typst templates. typstgen compiles each document against them, the same way on a laptop and in CI.
Rust developers who need PDFs
Add the crate and get the PDF as bytes from one function call. No typst install on the server, no temporary files.
Anyone writing documents with an AI agent
Over MCP the agent checks the document, looks at a page and compiles it, and reads Typst’s errors with file, line and column.

typst binaries or subprocesses needed: 0
ways in: CLI, Rust library, Wasm, MCP server: 4
MCP tools, from check and preview to e-invoices: 9
bundled font files, also in Wasm: 17

How it works

You run typstgen compile, or your AI agent calls the MCP server. Either way the document goes to the Typst engine that is compiled into typstgen.

Imports are looked up next to the document first, then in the template directories listed in typstgen.toml. You get a PDF, or Typst’s error with its exact position and exit code 1.

Templates and imports AI agents over MCP typstgen.toml →

What you get

The same PDF on every machine
Typst’s fallback fonts are always bundled. Switch off system fonts, pin the creation date, and the same input gives the same bytes.
PDF/A, PDF/UA and e-invoices
Enforce PDF/A-2b or PDF/UA-1. Embed ZUGFeRD / Factur-X data in the PDF, or write XRechnung and Peppol XML.
Archives you can prove
A manifest records each build; typstgen verify later shows that every PDF is unchanged and rebuilds byte for byte.

Invoices

One invoice JSON, every format

The invoice template of the Typst package business-templates renders the PDF from an invoice JSON. typstgen reads the same file for the machine-readable versions, so the PDF and the XML cannot disagree.

ZUGFeRD / Factur-X: --zugferd invoice.json embeds the EN 16931 data in a PDF/A-3b.
XRechnung 3.0 and Peppol BIS Billing 3.0: typstgen e-invoice writes UBL 2.1 XML.
Your own tax rules: prepare-invoice calculates line amounts, tax groups and totals from your configuration, VAT or sales tax.
Clear errors: every problem names the JSON field to fix. Nothing is sent; validation and transmission stay separate steps.

E-invoices →Invoice configuration →

Terminal: typstgen e-invoice --format xrechnung-3.0 --company company.json invoice.json prints 'wrote invoice.xml (xrechnung-3.0, UBL 2.1)' and the checks: arithmetic and required fields passed, XML schema, EN 16931, XRechnung and transmission not run. The same command on incomplete.json fails and names the missing fields recipient.electronic_address and metadata.buyer_reference (the Leitweg-ID for public buyers).

Quickstart

From a .typ file to a PDF in three steps. Every PDF on this page was compiled by typstgen from the files in examples/.

Install the CLI with cargo install typstgen.
List your template directories in typstgen.toml, for example template_paths = ["templates"].
Run typstgen compile letter.typ. The PDF lands next to it.

Read the documentation