# Fullbleed PDF Engine [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/fullbleed-engine/fullbleed-official  
**GitHub Stars:** 170  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/fullbleed-pdf-engine

## Description
Create, preview, inspect, verify, and compile deterministic PDF documents with Fullbleed.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "fullbleed-pdf-engine": {
    "command": "uvx",
    "args": ["fullbleed"]
  }
}
```

## Documentation

## What Fullbleed PDF Engine does

The Fullbleed PDF Engine MCP server exposes a document-generation workflow built around the Fullbleed PDF engine. The listed capabilities are creating, previewing, inspecting, verifying, and compiling PDF documents. Fullbleed renders HTML and CSS into PDF output and is designed for documents where repeatable layout and output checks matter.

Typical document types include invoices, reports, statements, notices, and variable-data print jobs. The underlying engine is implemented in Rust, while Fullbleed provides language packages and integrations for Python, Rust, Node.js, browser JavaScript, and C#/.NET.

## How it works

An agent supplies document content and styling to the Fullbleed workflow. HTML provides the document structure, while CSS controls layout and print presentation, including page settings such as paper size and margins. The engine produces PDF bytes and can also produce page previews; the Node.js example writes both a PDF and a PNG preview.

Rendering is deterministic according to the project description, making the server suitable for workflows that need to compare output or check changes. The repository also includes examples for PDF regression checks, verification, watch-mode rebuilding, reports from tabular data, and web application downloads.

## Setup and configuration

Python projects can install `fullbleed` with pip; Rust projects can add the `fullbleed` crate; Node.js and TypeScript projects can install the `fullbleed` npm package; browser applications use `fullbleed/browser`; and .NET applications can add `FullBleed.DotNet`.

The Python package includes the engine, fonts, and CLI without required third-party Python packages or a system PDF stack. The JavaScript package includes the WebAssembly engine and fonts. The .NET package includes native libraries for in-process rendering. The documented Python range is 3.10–3.14, Node.js examples require Node.js 22 or newer, and the .NET package targets .NET 8 while supporting .NET 8, 9, and 10 applications.

Browser rendering runs locally in a Web Worker and uses supplied static HTML and CSS; it is not described as capturing a live browser page.

## Tools and capabilities

The Fullbleed PDF Engine MCP server is described as supporting:

- Creating PDFs from HTML and CSS.
- Generating page previews for rendered documents.
- Inspecting and verifying PDF output.
- Compiling documents and variable-data jobs.
- Working with deterministic document output.
- Supporting print profiles through the Python CLI.

The engine can run in Python, Rust, Node.js, browser workers, and .NET integrations. Browser and Node.js usage can render ordinary PDFs and previews, while the Python package provides the complete CLI, including compiled variable-data jobs and print profiles.

## Limitations and notes

Those details should be confirmed before deployment. Browser usage renders supplied static HTML and CSS rather than capturing a live page. The .NET CLI adapter has a separate requirement for the Python CLI, even though in-process native rendering does not require a Python or browser runtime.

_Full upstream README: https://allmcps.com/mcp/fullbleed-pdf-engine/readme_