beautiful-pdf-mcp
MCP server that lets AI agents produce print-ready, typographically correct PDFs using Typst, with a page-as-canvas engine, multiple templates, and per-page layout quality control.
README
<div align="center"> <img src="assets/banner.png" alt="beautiful-pdf-mcp — print-ready PDFs for AI agents" width="100%" /> </div>
📄 beautiful-pdf-mcp
MCP server that lets AI agents produce print-ready, typographically correct PDFs — magazine spreads, GOST lab reports, books, resumes — compiled by Typst, not an HTML export dressed up as a document.
🧠 The idea: the page is the unit of design
Most generated documents are built the lazy way: stack blocks on a canvas and let them fall where they may. The result is familiar — a heading stranded at the bottom of a page, an image floating in a half-empty sheet, a paragraph that trails off into nothing.
This engine thinks the way a magazine make-up editor does, one page at a time:
- Budget first. Before any text is written,
estimate_page_budgetmeasures how many words fit one page of the chosen template — so content is written to size, not trimmed after the fact. - Fill the page like a block. Every page inside a continuous flow is composed to the bottom of the type area. The leftover text carries to the next page as plain prose — mid-sentence, even mid-hyphen, exactly like a printed book. Tails are normal; holes are not.
- Verify, then ship. Every compile returns a per-page
layout_report(fill %, holes, defects). The agent inspects rendered pages as PNGs and fixes problems before the user ever sees them.strict_layout: truerefuses to produce a defective PDF at all. - Two-pass image placement. The compiler tracks the position of every paragraph, computes where each image actually lands, and recompiles with explicit placements — so a photo never tears the layout or strands itself on an empty page.
📸 Showcase
<div align="center"> <img src="docs/showcase_journal.png" alt="Journal template — editorial spread with wrapped images" width="760" /> <p><em>Journal: text wraps around photos, justified type with no rivers, the article flows page to page</em></p> </div>
<div align="center"> <img src="docs/showcase_book.png" alt="Book template — A5, Van de Graaf margins" width="620" /> <p><em>Book: A5, mirrored Van de Graaf margins, chapter typography, illustrations interleaved into the story</em></p> </div>
Two of eight templates shown — run the test suite to render them all.
✨ Features
- 📐 Page-as-canvas engine — budget → compose → per-page QC → two-pass image placement. Every sheet is a finished block, not an accident.
- 🖼️ Magazine spreads — two photos placed diagonally with one continuous text threading around both, powered by meander; single photos get true side-wrap via wrap-it.
- 📏 Auto-fit single-page documents — a short resume or letter measures itself and scales typography up until the sheet is gracefully full.
- 🎓 GOST 7.32 compliance — sections on fresh pages, figures after first mention, full-width tables with captions above: Russian academic standards enforced structurally. Works in English and Russian (
language: "en"switches Figure/Table/Contents labels). - ✂️ No rivers, ever — justified text uses aggressive hyphenation costs so lines pack tight instead of stretching into word gaps.
- 🔁 Deterministic re-rendering — the document state lives in JSON; every edit re-lays-out the whole document by the rules, so nothing ever "drifts apart".
🚀 Quick Start
Prerequisites
- Python 3.10+
- Typst —
brew install typst(or download a release)
Installation
git clone https://github.com/Kreminskaya/beautiful-pdf-mcp.git
cd beautiful-pdf-mcp
pip install -r requirements.txt
Connect to your agent
Add to your MCP client config (Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json, Cursor: ~/.cursor/mcp.json — same JSON for any stdio MCP client):
{
"mcpServers": {
"beautiful-pdf": {
"command": "python3",
"args": ["/absolute/path/to/beautiful-pdf-mcp/src/server.py"]
}
}
}
Restart the client — tools appear as beautiful-pdf__*. Then just ask your agent:
"Make me a magazine-style PDF article from these three photos and this text."
📚 Templates
| Template | Use case | Format | Body font |
|---|---|---|---|
report |
Business report, analytics | A4 | Source Serif 4 |
academic_ru |
Thesis, lab report (GOST 7.32, en/ru) | A4 | PT Serif 14pt |
book |
Long-form, fiction & non-fiction | A5 | PT Serif |
technical |
API docs, developer guides | A4 | IBM Plex Sans |
portfolio |
Portfolio, showcase | A4 | Noto Sans |
letter |
Official correspondence | A4 | Source Sans 3 |
journal |
Magazine / editorial layout | A4 | Lora + Cormorant |
resume |
Modern two-column CV | A4 | IBM Plex Sans |
All 21 fonts ship with the repo — output is identical on every machine.
🛠️ How agents use it
budget = estimate_page_budget(template="journal", language="en")
# → words_per_page, lines_per_page: write the article TO BUDGET
doc = create_document(title="Between Rock and Sky", template="journal",
language="en", preset_overrides={"accent_color": "#c4a35a"})
sid = add_section(doc_id, "On Restraint", ARTICLE_WRITTEN_TO_BUDGET, level=1)["section_id"]
add_image(doc_id, sid, "photo1.png") # photos embed into the running text
add_image(doc_id, sid, "photo2.png") # second photo → diagonal spread
result = compile_preview(doc_id, pages="1-3")
# → PNG per page + layout_report: fill % and defects for every page
compile_pdf(doc_id, "article.pdf", strict_layout=True)
# refuses to ship a PDF with underfilled pages or layout holes
The loop is the point: budget → compose → look → fix → ship. The agent reads
the layout_report numbers (words to add, lines short), inspects the rendered
pages, and iterates until every page is a clean block.
<details> <summary>🧰 Full tool list (16 tools)</summary>
| Tool | Description |
|---|---|
estimate_page_budget |
Words/lines that fit one page of a template — call before writing |
create_document |
Create a document, returns doc_id |
add_section |
Add a section (Markdown content) |
update_section |
Update a section's title or text |
remove_section |
Remove a section |
add_image |
Image with optional caption, width, position (auto, after:N, wraps, top) |
add_gallery |
Grid of images |
add_table |
Table with headers and rows |
add_code_block |
Syntax-highlighted code |
add_callout |
Callout box (info / warning / tip / danger / quote) |
compile_preview |
Render pages to PNG + per-page layout_report QC |
compile_pdf |
Final PDF; strict_layout=True fails on layout defects |
save_document / load_document |
Persist / restore document state as JSON |
get_document_state / list_documents |
Inspect session state |
</details>
<details> <summary>🎛️ Per-document style overrides</summary>
Any preset key can be overridden per document via preset_overrides:
create_document(..., preset_overrides={
"accent_color": "#2a9d8f", # brand colour
"page_num_position": "bottom-center", # or top-left … bottom-right, none
"header_rule": False, # drop the thin running-header line
"show_header_footer": False, # no furniture at all
"body_font": "PT Serif",
"margin_left": "3.5cm",
})
</details>
<details> <summary>📐 How the page engine works</summary>
Each template declares a page contract (data/styles.json): what a finished
page looks like for that genre — fill thresholds, tolerated underfill, whether a
final chapter page may end early (a book chapter can; a hole mid-article cannot).
Compilation is two-pass: pass 1 renders the document with invisible
per-paragraph position marks, the server queries where every paragraph and image
actually landed, computes optimal after:N anchors for position: "auto"
images, and pass 2 recompiles with explicit placements. The QC
(src/layout_qc.py) then grades every page against the contract and reports
exact numbers — "page 3: 6 lines short, add ~40 words" — so the agent can fix
layout arithmetically instead of guessing.
The full specification lives in docs/SPEC_PAGE_FILL.md (in Russian — the project's design constitution is CONCEPT.md).
</details>
🧪 Testing
python3 tests/render_all.py # render every template to PNG + page QC
python3 tests/render_all.py journal # one template
python3 tests/render_all.py showcase # hand-finished showcase documents
Every page of every template is rendered to tests/output/ and graded by the
page-fill QC — the test fails if any page violates its template's contract.
🗺️ Roadmap
- [x] 8 templates with shipped fonts
- [x] Page-as-canvas layout engine (meander spreads, auto-fit, GOST structure)
- [x] Page budget + per-page fill QC +
strict_layout - [x] Two-pass compilation with automatic image placement
- [ ] Bibliography tool with GOST citation style (
gost-r-705-2008-numeric) - [ ] Typst 0.15 upgrade (multiple bibliographies, variable fonts)
- [ ] Decorative drop caps for the book template
- [ ] More CV layouts (single-column, photo-left)
🧱 Tech Stack
| Layer | Technology |
|---|---|
| Typesetting | Typst 0.14+, meander, wrap-it |
| Server | Python, FastMCP |
| Layout QC | typst query position marks + per-page fill grading |
| Imaging | Pillow (aspect detection, preview pipeline) |
| Fonts | PT, IBM Plex, Source, Noto, Lora, Cormorant — bundled |
📄 License
MIT — see LICENSE.
⭐️ If this saves you from one more ugly AI-generated PDF — star the repo!
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。