Skip to main content
Glama
fullbleed-engine

Fullbleed PDF Engine

by fullbleed-engine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to Fullbleed PDF Engine

No user-submitted related servers found.

    Related Servers

    • Imprint PDF

      263311487-ux
      A
      license
      Not graded
      quality
      B
      maintenance
      Local Markdown-to-PDF MCP server with four tools to list themes, render a document, validate an existing PDF, and create a document from a template. Requires Python, Pango/GLib, and fonts; its 0–100 report is heuristic, not print or accessibility certification.
      MIT

    • inclusio-mcp

      sebastienrousseau
      A
      license
      A
      quality
      A
      maintenance
      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.
      4
      65 PyPI
      Apache 2.0

    • oxidize-pdf

      bzsanti
      A
      license
      A
      quality
      A
      maintenance
      Rust-powered PDF toolkit over MCP: create, read, and analyze PDFs; extract text and entities for RAG; convert to Markdown; split/merge/rotate/reorder pages; manage form fields and annotations; encrypt documents. Runs locally via uvx oxidize-mcp.
      12
      687 PyPI
      6
      MIT

    • deliverable-mcp

      Diski7
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to render Markdown to HTML, estimate page counts, verify document delivery constraints, and atomically ship documents through a zero-dependency JSON-RPC stdio server.
      4
      MIT

    • pdf-automation

      Feynman520
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that drives PDFium and pypdf to perform comprehensive PDF operations including inspection, assembly, page editing, watermarking, rendering, extraction, form filling, encryption, compression, attachments, bookmarks, and metadata management.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct purposes, but several rendering-related tools (fullbleed_render, fullbleed_render_preview, fullbleed_verify) all accept HTML/CSS and produce PDFs or diagnostics, requiring careful reading to choose correctly. Similarly, fullbleed_capabilities and fullbleed_agent_contract both provide reference metadata, though one is compact and the other detailed. Overall, descriptions mitigate confusion but some overlap remains.

    Naming Consistency4/5

    All tools use the fullbleed_ prefix and snake_case, with a mostly consistent verb_noun or noun phrase pattern. Minor deviations exist: some names are noun-only (fullbleed_capabilities, fullbleed_assets, fullbleed_agent_contract) while others are verb-led. Still predictable and readable.

    Tool Count5/5

    11 tools is well within the ideal range for a PDF engine, covering scaffolding, rendering, compilation, verification, asset management, and introspection without obvious redundancy. Each tool has a clear role, and the count feels appropriately scoped.

    Completeness4/5

    Core PDF rendering workflows are well-covered: project creation, static and preview rendering, verification, compiled rendering, variable data, and asset management. Minor gaps include asset removal/uninstall operations and broader PDF manipulation (e.g., merge/split/extract), but these may be outside the stated scope. Agents can complete primary tasks without dead ends.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources