WeasyPrint by pagespool

com.pagespoolPublished by pagespool.comOfficial publisherv1.0.0Updated Nov 4, 2026

Hosted WeasyPrint: render HTML and print CSS to PDF, with PDF/A output on the paid plans.

The publisher's own server: Docling by pagespool

VerifiedStreamable HTTPWeb executableFiles & StorageDeveloper Tools

Overview

AI-generated overview

Hosted WeasyPrint service that lets an assistant turn HTML and print CSS into a PDF and hand back a temporary download link.

What you can do
  • Render HTML (up to 256 KB) to PDF with WeasyPrint
  • Return a download link, page count, file size and expiry for each render
  • Produce PDF/A output on paid plans
When to use it
Useful when you want an assistant to generate a PDF from HTML or print CSS without installing WeasyPrint locally, for example invoices, reports or printable pages.
Requirements
A remote MCP endpoint at api.pagespool.com over streamable HTTP. Authentication uses an X-API-Key header, or OAuth sign-in instead. No local runtime or packages are needed.
Before you install
The HTML you submit is sent to a third-party hosted service. The returned download link expires after 15 minutes, so it must be used or re-rendered promptly. PDF/A output requires a paid plan, which may involve payment.

Installation

In SourceWeft

  1. Open WeasyPrint by pagespool in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.pagespool%2Fweasyprint/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "weasyprint-by-pagespool": {
      "type": "http",
      "url": "https://api.pagespool.com/mcp/weasyprint/"
    }
  }
}

Tools

1

render_pdf

Render an HTML document to a PDF

Render up to 256 KB of HTML to a PDF with WeasyPrint. Returns a download link. Give the user the `download_url` so they can open the PDF. The link works for 15 minutes; after that, render again. The result is `{"download_url": "<link>", "pages": <page count>, "size_bytes": <PDF size>, "expires_in_minutes": 15}`. Only HTML and CSS are rendered; JavaScript is not run. For documents larger than 256 KB, use the REST API (`POST /v1/weasyprint/render`). Credits: 1 per call.

Parametershtmlrequiredpdf_variant

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Pagespool integrations