Productivity · Remote MCP server
pdfrender
HTML and CSS to PDF MCP server with page headers, footers and page numbers. No headless browser.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.pdfrender/pdfrender- Version
- 1.0.1
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- dev.pdfrender
- Namespace
- Namespace verified by the MCP Registry via the domain pdfrender.dev · how
- Listed under
- PDF MCP servers, Browser automation MCP servers
- Website
- pdfrender.dev
- Repository
- github.com/pdfrender-dev/pdfrender
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.pdfrender.dev/mcp/ | X-API-Key (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- pdfrender 1 · protocol 2025-06-18
- Tools discovered
- 1:
render_html_to_pdf - Checked on
- 2026-10-05
How to connect pdfrender
pdfrender is a remote MCP server: there is nothing to install. Its endpoint is https://api.pdfrender.dev/mcp/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-API-Key (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| PDFMakerAPITurn a description into a shareable, editable PDF - invoices, certificates, reports, resumes. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| pdfmuxPDF-to-Markdown extraction that audits its own output and flags any extractor's silent drops. | Local · stdio |
| pdfnative MCP - PDF/A & PDF/X-4 generation, PAdES signing & introspectionPDF MCP: generate PDF/A & PDF/X-4, sign & verify PAdES (LTV), forms, merge, split, encrypt. 28 tools. | Local · stdio |
| Pdfops MCPDeterministic PDF tools for AI agents: inspect fields, fill forms, merge PDFs, invoices. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| pdfs.buildDesign, publish and render PDF templates with Typst. Full template lifecycle over MCP. | Remote · HTTPLive check: sign-in required |
| PDFSpark MCPConvert HTML or URLs to PDF documents powered by Playwright. | Local · stdio |
| pdfzenRender PDFs from 45 starter templates or raw HTML. Pay-per-render with USDC via x402. | Remote · HTTPLive check: ✓ handshake |
| PencilManage tasks, projects, roadmaps, files, meetings, and team workflows with AI tools. | Remote · HTTPLive check: sign-in required |