inclusio-mcp
Accessibility-first LaTeX publishing engine with an embedded MCP server. Tools to list registered documents, render template-driven documents, and audit built PDFs for PDF/UA-2 / WTPDF / PDF/A-4f conformance with veraPDF. MIT-licensed.
README
<p align="center"> <img src="https://cloudcdn.pro/inclusio/v1/logos/inclusio.svg" alt="Inclusio logo" width="128" /> </p>
<h1 align="center">Inclusio</h1>
<p align="center"> <strong>Publishing that includes everyone.</strong> </p>
<p align="center"> Accessibility-first publishing engine for LaTeX, packaged as a Python CLI. PDF/UA-2 + WTPDF + PDF/A-4f triple-conformance, C2PA + PAdES + SLSA provenance, multi-format emission (HTML5 / JATS / EPUB3), LLM-augmented judges, and an MCP server for agent integration. </p>
<p align="center"> <a href="https://github.com/sebastienrousseau/inclusio/actions/workflows/engine-validation.yml"><img src="https://img.shields.io/github/actions/workflow/status/sebastienrousseau/inclusio/engine-validation.yml?style=for-the-badge&logo=github&label=CI" alt="Engine Validation" /></a> <a href="https://github.com/sebastienrousseau/inclusio/actions/workflows/verapdf.yml"><img src="https://img.shields.io/github/actions/workflow/status/sebastienrousseau/inclusio/verapdf.yml?style=for-the-badge&logo=github&label=veraPDF" alt="veraPDF Audit" /></a> <a href="https://github.com/sebastienrousseau/inclusio"><img src="https://img.shields.io/badge/Python-%3E%3D3.11-3776AB?style=for-the-badge&logo=python&logoColor=white" alt="Python >= 3.11" /></a> <a href="https://github.com/sebastienrousseau/inclusio"><img src="https://img.shields.io/badge/PDF%2FUA--2%20%7C%20WTPDF%20%7C%20PDF%2FA--4f-blue?style=for-the-badge" alt="PDF/UA-2 · WTPDF · PDF/A-4f" /></a> <a href="https://github.com/sebastienrousseau/inclusio/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-MIT-black?style=for-the-badge" alt="MIT licence" /></a> </p>
Contents
- Install —
pip, optional extras, source - Quick Start — first tagged PDF in 60 seconds
- Features — what the engine ships
- Usage — common Python + CLI recipes
- Architecture — the engine's package layout
- Examples — six runnable scenarios
- Documentation — quickstart, tutorials, reference
- Publishing against an external content tree
- Development — local validation gate
- Security — signed commits, provenance, audit
- License
Install
pip install inclusio # engine + CLI
pip install 'inclusio[mcp]' # + FastMCP server
pip install 'inclusio[provenance]' # + pyhanko (PAdES)
pip install 'inclusio[dev]' # + pytest, ruff, sphinx, interrogate
Requires Python ≥ 3.11 and a LuaLaTeX toolchain on PATH. Linux, macOS, and WSL are supported (native Windows works for the Python surface; the LaTeX gate needs WSL or a TeX Live install).
| Optional tool | Adds | Install |
|---|---|---|
verapdf |
The strict EAA / accessibility audit gate | verapdf.org/install |
pandoc (≥ 3.0) |
HTML5 / JATS XML / EPUB3 multi-format emission | brew install pandoc · apt install pandoc |
c2patool |
C2PA Content Credentials | contentauth/c2patool releases |
pyhanko (via [provenance]) |
PAdES B-T / B-LT / B-LTA signing | Pulled by the extra |
Build from source
git clone https://github.com/sebastienrousseau/inclusio.git
cd inclusio
./bin/setup # check toolchain + install dev extras
make test # smoke suite
make coverage # full suite (gate: 97 %)
Quick Start
A complete worked example you can paste into a fresh directory:
pip install inclusio
# Grab the minimal example, build + audit + emit + judge:
git clone --depth=1 https://github.com/sebastienrousseau/inclusio
cd inclusio/examples/01-hello-world && make
That single make produces build/hello.pdf (PDF/UA-2 + WTPDF +
PDF/A-4f triple-conformance), runs veraPDF over it, and exits
non-zero if any flavour fails.
Drive the same surface from Python:
# quickstart.py
import subprocess
from pathlib import Path
# 1. Render + build the bundled "hello" fixture — the CLI is the
# canonical entry point for the LaTeX step.
subprocess.run(
["python", "-m", "inclusio.cli.build", "build", "--doc", "hello"],
cwd="examples/01-hello-world",
check=True,
)
# 2. Audit the produced PDF in-process — pure-Python, no subprocess.
from inclusio.cli import audit
pdfs = audit.collect_pdfs(
target=Path("examples/01-hello-world/build"),
build_dir=Path("examples/01-hello-world/build"),
registry_stems={"hello"},
)
report = audit.audit(pdfs)
assert report["summary"]["fail"] == 0, "veraPDF reported a failure"
print(f' PASS {report["summary"]["pdfs"]} PDF(s), '
f'{report["summary"]["pass"]}/{report["summary"]["total"]} checks')
# → PASS 1 PDF(s), 3/3 checks
Features
- Tagged PDF, by default. Every build emits a PDF/UA-2 +
WTPDF + PDF/A-4f triple-conforming artefact via the LaTeX
kernel's
tagpdfintegration. The veraPDF audit gate is wired into CI and exits non-zero on any FAIL. - Multi-format emission. The same LaTeX source produces HTML5 (WCAG-clean), JATS XML (1.3, JATS4R-ready), and EPUB3 via Pandoc.
- LLM-augmented judges. ATS (Workday / Greenhouse / Lever
heuristic), citation grounding, and JD-to-CV fit — local
llama.cppor BYO-key cloud (Anthropic / OpenAI), with heuristic-only fallback when the LLM is unreachable. - Content provenance. C2PA Content Credentials (via
c2patool), PAdES B-T / B-LT / B-LTA signatures (viapyhanko), and SLSA L3 build attestation (viaactions/attest-build-provenance). - MCP server.
inclusio-mcpexposeslist_docs,audit_pdf,render, anddoc_countso Claude Code, Cursor, Continue, or any other MCP client can drive the engine. - JSON Resume importer.
inclusio import-resumeconverts a jsonresume.org v1 document into the engine's CV YAML schema. - Brief-driven CV tailoring. ATS-clean variants tailored against a job description with British-English cleanup and consistency lint.
Usage
Build, audit, judge a registered document
inclusio build --doc cv --mode draft # → build/cv.pdf
inclusio audit --strict # → veraPDF, non-zero on FAIL
inclusio judge --doc cv --judge ats # → grade + findings
Score a CV against a job description
# score_cv.py — fully runnable: drop into a directory with brief.txt + cv.txt
from pathlib import Path
from inclusio.judge import jd_fit
jd_text = Path("brief.txt").read_text(encoding="utf-8")
cv_text = Path("cv.txt").read_text(encoding="utf-8")
report = jd_fit.score_jd_fit(jd_text, cv_text)
print(f"score: {report.score}/100 grade: {report.grade}")
print(f"missing: {sorted(report.metrics['missing_required'])[:5]}")
# → score: 78/100 grade: B
# → missing: ['opentelemetry', 'rust']
Drive the engine over MCP
inclusio-mcp # stdio (Claude Code default)
inclusio-mcp --http --port 8765 # Streamable HTTP
Wire into Claude Code via ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"inclusio": {
"command": "inclusio-mcp",
"env": { "INCLUSIO_CONTENT_DIR": "/absolute/path/to/content" }
}
}
}
Embed C2PA Content Credentials
inclusio provenance --doc cv \
--cert /path/to/cert.pem \
--key /path/to/key.pem \
--output build/cv.c2pa.pdf
Architecture
inclusio/ # Python package
cli/ # build · audit · render · tailor · judge · emit · provenance · …
judge/ # ats · citations · jd_fit · local_llm · cloud_llm
emit/ # pandoc (HTML5 / JATS XML / EPUB3)
provenance/ # c2pa (c2patool) · pades (pyhanko)
mcp/ # FastMCP server
tools/ # fix_semantic · stamp_pdfs · overlay
core/ # LaTeX classes (.cls) and styles (.sty)
templates/ # Jinja2 templates for the template-driven docs
benches/ # pytest-benchmark micro-benchmarks
examples/ # Six self-contained runnable scenarios
docs/ # Sphinx documentation
External consumers supply their own content tree (LaTeX sources,
YAML metadata, brand assets) and point the engine at it through
INCLUSIO_CONTENT_DIR or --content-dir. The repo's own src/
and data/ directories double as the public-engine self-test
fixtures.
Examples
| # | Folder | What it teaches |
|---|---|---|
| 1 | 01-hello-world/ |
Tagged-PDF build with the audit gate |
| 2 | 02-cv-from-jsonresume/ |
JSON Resume → CV → ATS + JD-fit scoring |
| 3 | 03-paper-with-citations/ |
Paper → PDF + HTML + JATS + EPUB + citation judge |
| 4 | 04-mcp-agent/ |
inclusio-mcp + Claude Code skill |
| 5 | 05-c2pa-sign/ |
C2PA Content Credentials |
| 6 | 06-pades-sign/ |
PAdES B-T eIDAS signature |
Each folder has its own Makefile (make help lists targets) and
a README.md with the why + the how.
Documentation
- Quickstart — five-minute walkthrough.
- Tutorials — four end-to-end walkthroughs paired 1 : 1 with the examples.
- Architecture — public-engine vs content-repo boundary, sprint history, decision log.
- Tagged PDF — the conformance stack.
- Multi-format — HTML / JATS / EPUB.
- Judges — ATS, citations, JD-fit, LLM rerank contract.
- Provenance — C2PA, PAdES, SLSA.
- MCP server — tool + resource surface.
Publishing against an external content tree
make publish CONTENT_DIR=/absolute/path/to/your-content-repo
The content repo supplies its own data/meta.yaml (document
registry) and src/**.tex (LaTeX sources). The engine reads no
state from outside INCLUSIO_CONTENT_DIR once it's set.
Development
make test # smoke (≤ 20 s)
make coverage # full suite + 97 % gate (~3 min)
make docstrings # 100 % interrogate gate
make benchmark # pytest-benchmark micro-budgets
make audit-strict # veraPDF, exits non-zero on any FAIL
make docs # Sphinx
All commits to main are squash-merged via PR. Branch protection
requires Lint (ruff) + Public Engine Checks (py3.11 / 3.12 / 3.13) + the Signed-commit gate to pass. See
CONTRIBUTING.md.
Security
- SSH-signed commits. Every commit on
mainis GitHub-verified. - Signed tags. Release tags are ED25519-signed.
- SLSA L3 build provenance (gated on the repo being public or on a paid GitHub plan).
- PyPI Trusted Publishing wiring (
pypa/gh-action-pypi-publish) inrelease.yml; flipvars.PYPI_TRUSTED_PUBLISHING=trueonce the PyPI publisher is configured. - Cloud LLM keys are env-var only —
inclusionever auto- discovers credentials from disk.
Report vulnerabilities per SECURITY.md.
Related MCP Servers
Sibling MCP servers by the same author — each targets a different agent workflow:
| Server | Purpose |
|---|---|
noyalib-mcp |
Lossless YAML 1.2 parsing, formatting & validation (Rust) |
rlg-mcp |
RustLogs log streams for on-call / SRE agent workflows |
pain001-mcp |
Generate & validate ISO 20022 pain.001 payment initiation files |
bankstatementparser-mcp |
Parse bank statements (BAI2, MT940/MT942, CAMT.053, OFX, CSV) |
camt053-mcp |
Parse & reconcile ISO 20022 camt.053 bank-to-customer statements |
acmt001-mcp |
Generate & validate ISO 20022 acmt.001 account management messages |
MCP Registry
mcp-name: io.github.sebastienrousseau/inclusio-mcp
Install the MCP server with pip install 'inclusio[mcp]' (the mcp extra pulls in mcp[cli]>=1.27.0). Run with inclusio-mcp — stdio transport, exposes accessibility-publishing tools to Claude Desktop, Cursor, and other MCP clients.
License
MIT. © 2026 Sebastien Rousseau.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。