pagenull/mcp
Related Servers
Alternatives to pagenull/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceTurn HTML or a URL into a pixel-accurate PDF in a single tool call.MIT
- AlicenseNot gradedqualityDmaintenanceEnables PDF and image generation from templates, JSON, HTML, or URLs through the PDF Gen Studio API. Supports rendering, template management, and multiple output formats.8 npm1MIT
- AlicenseNot gradedqualityDmaintenanceProvides tools to capture pixel-perfect website screenshots as images or PDF. Supports configurable viewport, full-page capture, CSS injection, and returns either viewable images or base64-encoded content.MIT

formfeedofficial
AlicenseAqualityBmaintenanceRender PDFs and images from HTML templates (Jinja2, Liquid, Handlebars) or Word and PowerPoint files through the Formfeed API, check data against a template's schema before rendering, and convert Office documents to PDF.101MIT- AlicenseNot gradedqualityDmaintenanceConverts HTML files or HTML content to PDF using Puppeteer's browser rendering engine with support for CSS, JavaScript, custom page formats, margins, and header/footer templates.6MIT

@sheetrender/mcpofficial
AlicenseAqualityBmaintenanceRenders PDFs from HTML templates or saved templates and spreadsheet data, with batch job support and document retrieval.11154 npm1MIT
TDQS
Scored across 6 tools
Most tools are clearly distinct by action and resource, but render_pdf and render_template both produce PDFs and require the agent to distinguish between HTML/URL input versus template/data input. The descriptions make the boundary clear enough, though the overlap is the main source of potential misselection.
The set mostly follows a verb_noun pattern: get_usage, render_pdf, list_templates, render_template, verify_receipt. The only notable deviation is screenshot, which is a single noun/verb rather than verb_noun, but it remains readable and idiomatic.
Six tools is well-scoped for a focused PDF rendering and verification service. Each tool earns its place, and the set avoids unnecessary surface area.
Core workflows are covered: usage, PDF rendering from HTML/URL, screenshots, template listing and rendering, and receipt verification. The main gap is template lifecycle management, since agents can list and render templates but cannot create, update, or delete saved templates through this MCP surface.