mcpField
P
pdfrender

pdfrender

Remote
pdfrender.devProductivity0Updated 4w ago

About pdfrender

pdfrender converts HTML and CSS to PDF for developers and agents that need document rendering. It uses WeasyPrint for layout, with page settings controlled through CSS; it runs no JavaScript and fetches no URLs.

Key features

  1. 01Render HTML and CSS as PDF
  2. 02Set page layout through CSS
  3. 03Add headers, footers, and page numbers
  4. 04REST API and hosted endpoint

Use cases

  1. 01Create reports with page numbers
  2. 02Render documents with headers and footers
  3. 03Generate PDFs in MCP workflows
  4. 04Convert HTML through the REST API

MCP support

It provides a Streamable HTTP MCP endpoint for clients to render HTML as PDF. Anonymous calls are supported, and an API key raises the limits.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.pdfrender.dev/mcp/
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://api.pdfrender.dev/mcp/Auth required

Tools

Details

From the project README

pdfrender

smithery badge

HTML and CSS to PDF API and MCP server. WeasyPrint with page headers, footers and page numbers, no headless browser. Hosted in Germany.

pdfrender turns HTML and CSS into PDF over a REST API and an MCP server. WeasyPrint 70 lays out the pages, with paper size, margins, headers, footers and page numbers set in CSS. It runs no JavaScript and fetches no URLs, so images and fonts go in as data: URIs. Limits are 2 MB of HTML and 50 pages per render. The servers are in Germany. The free plan has 100 credits a month and needs no card.

Quickstart

Render HTML to a PDF in one call. The anonymous tier needs no key; add -H "X-API-Key: $PDFRENDER_API_KEY" for your plan's limits.

curl -X POST https://api.pdfrender.dev/v1/render \
  -H 'content-type: application/json' \
  -d '{"html":"<h1>Hello</h1>"}' -o hello.pdf

The response is the PDF itself (content-type: application/pdf), saved as hello.pdf. Page size, margins, headers, footers and page numbers are set in the HTML's print CSS.

Use it from

MCP server

Streamable-HTTP endpoint: https://api.pdfrender.dev/mcp/ — the anonymous tier works without a key; an API key raises the limits.

Claude Code:

claude mcp add --transport http pdfrender https://api.pdfrender.dev/mcp/

Claude Code: /plugin marketplace add pdfrender-dev/pdfrender then /plugin install pdfrender@pdfrender (set PDFRENDER_API_KEY for your key).

Cursor / Windsurf / Cline / Claude Desktop:

{
  "mcpServers": {
    "pdfrender": {
      "url": "https://api.pdfrender.dev/mcp/"
    }
  }
}

One-click installs for every client: https://pdfrender.dev/connect

Integrations (n8n, Zapier, Make, Dify, SDKs and templates): https://github.com/pdfrender-dev/pdfrender-integrations

Templates

Ready-made workflows: https://pdfrender.dev/templates

Links

API

Base URL https://api.pdfrender.dev/ — authenticate with an X-API-Key header; anonymous calls work at a lower rate limit.

About the files here

  • .claude-plugin/ — Claude Code plugin, with this repo as its own marketplace.
  • .mcp.json — the MCP server the Claude Code plugin connects to.
  • gemini-extension.json — Gemini CLI extension manifest.
  • glama.json — Glama server claim (names the maintainer).
  • mcp.json — Agent Plugins 1.0 MCP server config.
  • plugin.json — Agent Plugins 1.0 plugin manifest.
  • server.json — the entry in the official MCP Registry.
  • skills/ — an Agent Skill (agentskills.io SKILL.md) for skill galleries.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.