Generates deterministic PDF documents from HTML and CSS using a high-performance Rust engine.
Also known as fullbleed-engine/fullbleed-official, fullbleed-official, fullbleed-mcp
- Stars
- 172
- Tools
- 11
- Downloads, 30 days
- 178
- Latest version
- 0.1.1
- Last commit
- Nov 8, 2026
- License
- MIT
What is Fullbleed PDF Engine MCP?
Fullbleed PDF Engine generates deterministic PDF documents from HTML and CSS using a high-performance Rust engine. It exposes 11 tools, such as fullbleed_capabilities, fullbleed_agent_contract, fullbleed_create_project.
Summary generated from the project's README
About Fullbleed PDF Engine MCP server
Fullbleed PDF Engine provides a deterministic way to generate PDF documents from HTML and CSS. It is designed for developers who need to create high-quality invoices, reports, statements, and variable-data print jobs. The engine is built with Rust, ensuring high performance across different programming environments. Users can implement it locally within their own applications using several language integrations.
Developers can choose from multiple language packages including Python, Rust, Node.js, JavaScript, and C#. The Python package includes a complete CLI and the engine itself, while the JavaScript version offers WebAssembly for use in Node.js or browser workers. For .NET developers, the library supports .NET 8, 9, and 10 with native in-process rendering. The engine handles fonts and assets locally, meaning it does not require external accounts or document uploads to function.
What you can do with it
- 1Generate automated business documentsCreate professional invoices and financial reports using HTML and CSS templates.
- 2Integrate PDF rendering into web appsUse WebAssembly to render PDFs directly in a browser or via Node.js workers.
- 3Develop native .NET applicationsPerform in-process PDF rendering within a C# environment without needing a Python runtime.
- 4Build reusable document componentsConstruct complex layouts using typed methods, JSX, or functional components instead of raw HTML strings.
Written from the project's README. Every use case is checked against a quote from it.
How to install Fullbleed PDF Engine MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Fullbleed PDF Engine MCP in Claude Code
$ claude mcp add fullbleed-official -- uvx fullbleed-mcpInstall Fullbleed PDF Engine MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"fullbleed-official": {
"command": "uvx",
"args": [
"fullbleed-mcp"
]
}
}
}Install Fullbleed PDF Engine MCP in VS Code
.vscode/mcp.json
{
"servers": {
"fullbleed-official": {
"type": "stdio",
"command": "uvx",
"args": [
"fullbleed-mcp"
]
}
}
}Install Fullbleed PDF Engine MCP in VS Code CLI
$ code --add-mcp '{"name":"fullbleed-official","type":"stdio","command":"uvx","args":["fullbleed-mcp"]}'Install Fullbleed PDF Engine MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"fullbleed-official": {
"command": "uvx",
"args": [
"fullbleed-mcp"
]
}
}
}Install Fullbleed PDF Engine MCP in Codex
$ codex mcp add fullbleed-official -- uvx fullbleed-mcpInstall Fullbleed PDF Engine MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.fullbleed-official] command = "uvx" args = ["fullbleed-mcp"]
Install Fullbleed PDF Engine MCP in Gemini CLI
$ gemini mcp add -s user fullbleed-official uvx -- fullbleed-mcpInstall Fullbleed PDF Engine MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"fullbleed-official": {
"command": "uvx",
"args": [
"fullbleed-mcp"
]
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for fullbleed-mcp 0.1.1 in an isolated container with no network and no keys. It answered and listed 11 tools.
Fullbleed PDF Engine MCP tools 11
Read from the server with tools/listfullbleed_capabilitiesRead-onlyRead the installed runtime's compact feature map and PDF profile requirements before choosing features. Use fullbleed_agent_contract for command schemas, workflow examples, and detailed limitations.
fullbleed_agent_contractRead-onlyRead the canonical installed contract: version, commands, schemas, capabilities, profiles, examples, limitations, and recommendation boundary.
fullbleed_create_projectActionCreate an agent-ready project or document scaffold in an absent or empty workspace directory; returns generated artifacts and next actions. Use this when starting a project, then render its source with fullbleed_render or fullbleed_render_preview.
fullbleed_renderActionRender static HTML/CSS to a PDF and return output paths and render diagnostics. Supply exactly one of html or html_path. Use fullbleed_render_preview for visual iteration, fullbleed_verify for delivery checks, or fullbleed_compile_vdp for variable records. Does not capture live websites.
fullbleed_render_previewActionRender a PDF plus PNG page previews for visual inspection after document changes; returns their artifact paths. Supply exactly one of html or html_path. Use fullbleed_render for PDF-only output and fullbleed_verify for explicit failure checks.
fullbleed_verifyActionRender HTML/CSS through Fullbleed's validation path and return structured diagnostics and failures before delivery. Supply exactly one of html or html_path and select fail_on checks explicitly. Use fullbleed_inspect for an existing PDF. Internal checks do not establish independent standards conformance.
fullbleed_inspectRead-onlyRead an existing PDF's version, page count, profile claims, warnings, and template-composition compatibility without changing it. Use fullbleed_verify to render and check HTML/CSS source, or fullbleed_assets with action='verify' to check asset package integrity.
fullbleed_assetsActionManage font, CSS, and icon packages with list, info, install, verify, or lock. Returns package details or operation results. Install writes workspace assets and may download supported remote packages. Use fullbleed_inspect for PDFs and fullbleed_verify for document validation.
fullbleed_compileActionCompile inline HTML/CSS and return compile_id plus template statistics for repeated calls to fullbleed_render_compiled. Handles belong to this server process; restart or eviction after 64 retained handles requires recompiling. Use fullbleed_compile_vdp for a single variable-data job without retaining a handle.
fullbleed_render_compiledActionWrite a PDF from compile_id returned by fullbleed_compile in this server session. Choose static copies, fixed geometry, or content reflow; returns the output path, page/record counts, and SHA-256. Use fullbleed_compile_vdp to compile and render a variable-data job in one call.
fullbleed_compile_vdpActionCompile inline HTML/CSS and render columnar variable records into one PDF, returning its path, counts, SHA-256, and compile/render metrics. Releases the temporary handle after rendering. Use fullbleed_compile plus fullbleed_render_compiled when reusing a template across calls.
| fullbleed_capabilities | Read the installed runtime's compact feature map and PDF profile requirements before choosing features. Use fullbleed_agent_contract for command schemas, workflow examples, and detailed limitations. | Read-only |
| fullbleed_agent_contract | Read the canonical installed contract: version, commands, schemas, capabilities, profiles, examples, limitations, and recommendation boundary. | Read-only |
| fullbleed_create_project | Create an agent-ready project or document scaffold in an absent or empty workspace directory; returns generated artifacts and next actions. Use this when starting a project, then render its source with fullbleed_render or fullbleed_render_preview. | Action |
| fullbleed_render | Render static HTML/CSS to a PDF and return output paths and render diagnostics. Supply exactly one of html or html_path. Use fullbleed_render_preview for visual iteration, fullbleed_verify for delivery checks, or fullbleed_compile_vdp for variable records. Does not capture live websites. | Action |
| fullbleed_render_preview | Render a PDF plus PNG page previews for visual inspection after document changes; returns their artifact paths. Supply exactly one of html or html_path. Use fullbleed_render for PDF-only output and fullbleed_verify for explicit failure checks. | Action |
| fullbleed_verify | Render HTML/CSS through Fullbleed's validation path and return structured diagnostics and failures before delivery. Supply exactly one of html or html_path and select fail_on checks explicitly. Use fullbleed_inspect for an existing PDF. Internal checks do not establish independent standards conformance. | Action |
| fullbleed_inspect | Read an existing PDF's version, page count, profile claims, warnings, and template-composition compatibility without changing it. Use fullbleed_verify to render and check HTML/CSS source, or fullbleed_assets with action='verify' to check asset package integrity. | Read-only |
| fullbleed_assets | Manage font, CSS, and icon packages with list, info, install, verify, or lock. Returns package details or operation results. Install writes workspace assets and may download supported remote packages. Use fullbleed_inspect for PDFs and fullbleed_verify for document validation. | Action |
| fullbleed_compile | Compile inline HTML/CSS and return compile_id plus template statistics for repeated calls to fullbleed_render_compiled. Handles belong to this server process; restart or eviction after 64 retained handles requires recompiling. Use fullbleed_compile_vdp for a single variable-data job without retaining a handle. | Action |
| fullbleed_render_compiled | Write a PDF from compile_id returned by fullbleed_compile in this server session. Choose static copies, fixed geometry, or content reflow; returns the output path, page/record counts, and SHA-256. Use fullbleed_compile_vdp to compile and render a variable-data job in one call. | Action |
| fullbleed_compile_vdp | Compile inline HTML/CSS and render columnar variable records into one PDF, returning its path, counts, SHA-256, and compile/render metrics. Releases the temporary handle after rendering. Use fullbleed_compile plus fullbleed_render_compiled when reusing a template across calls. | Action |
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablefullbleed-engine/fullbleed-official is public and reachablegithub.com/fullbleed-engine/fullbleed-official ↗Pass
- Package names this repository as its sourcefullbleed-mcp names fullbleed-engine/fullbleed-official as sourcepypi.org/project/fullbleed-mcp/ ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for fullbleed-mcppypi.org/project/fullbleed-mcp/ ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-08github.com/fullbleed-engine/fullbleed-official ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from fullbleed-mcpPass
- No critical advisory in the package or its dependencies2 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model11 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubFullbleed PDF Engine
Generate PDFs from HTML/CSS in Python, Rust, JavaScript, and C#. MIT licensed.
Build invoices, reports, statements, and variable-data print jobs with a deterministic Rust engine. Use the native Rust API, the Python package, or the optional JavaScript and .NET integrations. The Python wheel includes the engine, fonts, and CLI with no required third-party Python packages or system PDF stack. The JavaScript package includes the WebAssembly engine and fonts for Node.js and browser workers; the .NET package includes native libraries for in-process rendering.
Try your own document · Documentation · Examples · PyPI · crates.io · npm · Release notes · MIT license
Actual Fullbleed output. Open either preview for its PDF, or explore the designed examples with HTML/CSS, data, and font setup.
Compare both designs in HTML/CSS and Python components, with matching page output and runnable source. The component versions use the opt-in 2.6 alpha.
Choose your language
| Language | Install | Start building |
|---|---|---|
| Python | python -m pip install fullbleed |
Python quickstart |
| Rust | cargo add fullbleed |
Native Rust quickstart |
| Node.js / TypeScript | npm install fullbleed |
Node quickstart · Next.js PDF download |
| Browser JavaScript | npm install fullbleed |
PDF components and JSX · React starter · HTML/CSS starter |
| C# / .NET | dotnet add package FullBleed.DotNet |
C# components and styles · NuGet quickstart |
The language packages release independently. The Node quickstart, browser guide and C# quickstart record the tested package and engine versions; downloadable starters pin their dependencies.
JavaScript applications can export styled or unstyled component HTML
and generate PDFs and previews. Import fullbleed in Node or fullbleed/browser
in a web app. Node applications can use a
bounded render queue
and optional process isolation.
FullBleed.DotNet's managed library targets .NET 8 and works with .NET 8, 9, and 10 applications. It includes C# components, native rendering, compiled bindings and previews. Its separate CLI adapter requires the Python CLI. The Python package provides the complete CLI, including compiled variable-data jobs and print profiles; the Rust guide covers the native API.
Your first PDF
Start in the HTML/CSS playground with a designed invoice or report, or choose Open local files to use your own HTML, CSS, images, and fonts. Rendering runs locally in your browser, with no account or document upload.
Download the PDF, or select Python or Node.js under Project language and choose Download project. The ZIP includes your source, assets, fonts, licenses, pinned dependencies, and a script to render the document locally.
Keep the ZIP unchanged, then choose Open saved project in the playground to continue editing on a later visit.
If the output needs work, report a rendering problem with a small example using data and assets you can share publicly. For a guided Python walkthrough, use the notebook in Colab, or start with a local script below.
Python
Python 3.10–3.15 on Windows, macOS, or Linux:
python -m pip install fullbleed
Save this as hello.py, then run python hello.py:
from pathlib import Path
import fullbleed
html = "<h1>Invoice INV-1042</h1><p>Consulting: USD 1,200.00</p>"
css = "@page { size: A4; margin: 20mm; } h1 { color: #175c52; }"
pdf = fullbleed.PdfEngine().render_pdf(html, css)
Path("invoice.pdf").write_bytes(pdf)
Open invoice.pdf. The quickstart adds fonts, previews, and a complete project. The runnable source is in examples/quickstart/hello.py.
Node.js
Use Node.js 22 or newer. Run npm install fullbleed, save this as invoice.mjs, then run node invoice.mjs:
import { writeFile } from 'node:fs/promises';
import { renderPdf } from 'fullbleed';
const result = await renderPdf({
html: '<h1>Invoice INV-1042</h1><p>Consulting: USD 1,200.00</p>',
css: '@page { size: A4; margin: 20mm } h1 { color: #175c52 }',
previewDpi: 96,
});
await writeFile('invoice.pdf', result.pdf);
await writeFile('invoice.png', result.previews[0]);
Open invoice.pdf or its PNG preview. The Node.js quickstart includes a downloadable designed invoice project. The separate Node package supports ESM, CommonJS, and TypeScript. For an application route, use the Next.js starter.
Browser JavaScript
Try the editable browser app to generate an invoice or report, change its HTML/CSS, and download the PDF. Rendering runs locally in a Web Worker; the starter does not upload document inputs to a rendering service.
To build on it, download the complete project.
Extract the ZIP, open a terminal in fullbleed-browser-starter, and use Node.js
22.12 or newer for the development tools:
npm ci
npm run dev
Open the localhost URL printed by Vite. The browser guide
explains adding fullbleed/browser to an existing app, serving its runtime
assets over HTTPS or localhost, cancellation, custom fonts, and static deployment.
This renders supplied static HTML/CSS; it does not capture a live browser page.
Rust
Start with the native Rust quickstart. The fullbleed crate exposes FullBleed::builder() and render_to_buffer(...), with no Python requirement. The guide includes runnable invoice and report examples with explicit fonts and PNG previews, plus the latest hosted Rust API reference.
C# and .NET
Install FullBleed.DotNet in a .NET 8, 9, or 10 project and follow the C# quickstart. Compose documents with ordinary methods, LINQ children and immutable style objects. The component guide explains WithClass, attached stylesheets and inline overrides and includes a complete invoice download with explicit fonts. Existing HTML/CSS templates remain supported. Native rendering runs inside the .NET process on Windows x64, Linux x64, Intel macOS, and Apple Silicon macOS, without a Python or browser runtime.
Author with reusable components
Components are another way to author the same print documents. Use ordinary functions, children and reusable styles instead of writing HTML strings:
- Python components and styling — the stable
fullbleed.uiAPI includes function components,class_nameand document stylesheets. - JavaScript functions and JSX/TSX — try the live invoice or customize the React starter.
- C# components and styles — compose documents with typed methods, LINQ and immutable styles.
Python release channels
| Channel | Install | Component API |
|---|---|---|
| Stable release | python -m pip install fullbleed |
Existing HTML/CSS rendering and fullbleed.ui components |
| Opt-in alpha 2.6.0a14 | python -m pip install --pre "fullbleed==2.6.0a14" |
fullbleed.components: owned styles, named parts, data tables, static Bootstrap helpers, page bands and styled/unstyled HTML export |
The component API remains experimental:
independent-kit integration and independent author feedback still need to be
settled. fullbleed.components is the intended public namespace for the 2.6 API.
Existing fullbleed.ui imports remain supported, and earlier alpha imports from
fullbleed.ui.experimental expose the same objects. See the release-status review and graduation
criteria or
read the current component guide.
The language packages have their own versions and API coverage.
The alpha also adds native PDF links for both HTML and component authors, including internal destinations and wrapped links. This navigation work is separate from the stable 2.5 API and requires alpha 14 rather than an earlier alpha kit.
The complete-document migration guide maps styles, page geometry, metadata, fonts and renderer options from the existing API. Its paired portrait and landscape reports preserve PDF text and rendered output. Both styled and unstyled HTML exports remain available.
Choose your starting point
See generated PDFs and their source →
Why use Fullbleed?
- Simple deployment: prebuilt wheels for 15 platform targets, with no browser or system-font installation needed for the bundled workflow.
- Repeatable documents: explicit assets and metadata, deterministic rendering, and SHA-256 reproducibility checks.
- Document-focused layout: pagination, headers and footers, tables, template overlays, and per-page data.
- Volume workflows: compile a template once, then bind fixed or reflowing records. Measured workloads and limits.
- Inspectable output: PDF inspection, PNG previews, structured diagnostics, and profile verification tooling.
Native previews of unembedded Standard 14 fonts use compact bundled outline
substitutes, so basic Helvetica, Times, Courier, Symbol, and Dingbats text renders
without system fonts. Registered and embedded font programs take precedence.
The font-resolution trace identifies the bundled_substitute outcome; runtime
discovery reports bundled_standard_font_previews. See the
font sources, licenses, and coverage limits.
Fullbleed uses static HTML/CSS as a document layout language. Check the CSS coverage and remaining gaps for your templates. Use a browser when JavaScript or live website behavior is part of the required result.
Profile selection alone does not establish standards conformance. The release evidence records the checks performed and their limits.
Get help and contribute
Ask usage questions and share documents in Discussions. For a reproducible bug or feature proposal, open an issue. The contributor guide covers local setup, tests, and where to make changes.
If Fullbleed is useful to you, support its maintenance through sponsorship, documentation, or a useful example. Sponsorship is optional; Fullbleed remains MIT licensed and free to use.
Agent discovery and integrations
An agent does not need release-specific Fullbleed knowledge. The installed binary generates one canonical contract containing its actual version, selection boundary, capabilities, parser-derived CLI surface, result schemas, PDF profiles, examples, limitations, Agent Skill metadata, MCP tools, and acceptance tasks:
fullbleed agent-manifest --json
# Equivalent canonical form:
fullbleed agent-contract --format json
The committed fullbleed-agent-contract.json, cli_schema.md, and llms.txt are generated from the built wheel. CI rejects version, command, schema, profile, or capability drift. Runtime introspection remains authoritative.
The first-party, versionless skills/fullbleed/SKILL.md teaches tool selection and the render/preview/diagnose/verify loop without duplicating the manual. It is bundled in the wheel and can be exported into any absent or empty agent-skill directory:
fullbleed agent skill-path --json
fullbleed agent export-skill .agents/skills/fullbleed --json
You can also install the Skill directly from a pinned GitHub release with gh skill. The guide shows how to check its source and version; the Python package supplies the rendering engine.
For tool-calling agents, install the separately versioned adapter so the core package remains dependency-free:
python -m pip install fullbleed-mcp
fullbleed-mcp --root .
The stdio server confines document paths to the selected workspace and delegates every engine operation to the installed Fullbleed runtime. It exposes semantic discovery, project creation, render/preview, inspect, verify, assets, and fixed/reflow compiled VDP tools. The dependency-free core also provides fullbleed mcp --root ..
Use Fullbleed when the requested artifact is a deterministic print document built from structured content. Use a browser when the requested artifact is a screenshot or interactive state of an arbitrary live website. Use a general PDF editor when existing page content itself must be rewritten.
Cold-agent testing is available through fullbleed agent-acceptance; compact copyable workflows live in examples/agent_workflows, and the approach-neutral benchmark scaffold lives in agentdocbench.
This README is the canonical usage guide for:
fullbleedCLI (human workflows + machine/agent automation)fullbleedPython bindings (PdfEngine,AssetBundle, batch APIs)
Additional focused references are in docs/:
docs/install-non-technical.md(step-by-step setup for non-technical users)docs/css-coverage.md(validated CSS coverage, parity status, and active gaps)docs/README.mddocs/engine.mddocs/performance-architecture.mddocs/performance-pass-2026-08-04.mddocs/python-api.mddocs/ui-accessibility.mddocs/cli.mddocs/pdf-templates.md
What You Get
- No headless browser requirement for PDF generation.
- Deterministic render pipeline with optional SHA256 output hashing.
- Reproducibility workflow via
--repro-recordand--repro-check. - PDF
1.7as the production-stable default target. - Rust-native PDF template composition for VDP/transactional overlays.
- Native Rust image emission for overlay and finalized compose outputs (
--emit-image) without external PDF raster runtime dependencies. - Feature-driven page-to-template binding with per-page deterministic compose plans.
- Structured JSON result schemas for CI and AI agents.
- Offline-first asset model with explicit remote opt-in.
- Remote project template registry workflows (
new list,new search,new remote). - Python-first extension surface for hackability and custom workflows.
- Python render calls release the GIL while Rust rendering executes.
- Ordered standard-library worker pools for batch rendering and selected internal workloads.
- A deliberately small, license-audited Rust dependency graph and no required third-party Python runtime or build packages.
Concurrency Model
- Python binding render methods release the GIL during Rust execution through the Stable ABI bridge.
- Parallel batch APIs use Fullbleed's ordered standard-library worker pool (
render_pdf_batch_parallel(...)and parallel-to-file variants). - The same bounded worker implementation serves selected internal hotspots such as table layout and JIT paint paths.
- Do not assume every single-document render path will fully saturate all cores end-to-end.
Fullbleed PDF Engine MCP questions
How do I add Fullbleed PDF Engine MCP to Claude Code?
Run claude mcp add fullbleed-official -- uvx fullbleed-mcp in your terminal. Add --scope user to make it available in every project.
How do I add Fullbleed PDF Engine MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Fullbleed PDF Engine MCP provide?
It exposes 11 tools, including fullbleed_capabilities, fullbleed_agent_contract, fullbleed_create_project, fullbleed_render, fullbleed_render_preview.
What languages are supported for generating PDFs?
The engine supports Python, Rust, JavaScript (Node.js and browser), and C# (.NET).
Does the Python package require external system dependencies?
No, the Python wheel includes the engine, fonts, and CLI without requiring third-party Python packages or a system PDF stack.
Can I use Fullbleed in a web browser?
Yes, the JavaScript package includes a WebAssembly engine and fonts for use in Node.js and browser workers.