formfeed
OfficialRelated Servers
Alternatives to formfeed
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceRenders PDFs from HTML templates or saved templates and spreadsheet data, with batch job support and document retrieval.11835 npm1MIT- 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.11 npm1MIT

DocuQueue MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables creating professional documents (invoices, contracts, certificates, proposals, reports) via the DocuQueue API, with tools for template management, filling, previewing, and PDF generation.1MIT- AlicenseNot gradedqualityDmaintenanceEnables Word document generation from templates using Jinja2 syntax and parsing of DOCX, PDF, and Excel files to extract structured content, metadata, and text.10 npm1MIT

docjet-mcpofficial
AlicenseAqualityCmaintenanceRender branded PDF documents (invoices, reports, certificates) and PNG social images directly from any MCP client using DocJet templates or raw HTML with JSON data.319 npmMIT- AlicenseAqualityAmaintenanceMCP server for Office documents — create, edit, fill templates, convert, and extract Word/Excel/PowerPoint. LaTeX-style markup, math formulas, PDF export, template loops, and document diff. stdio / SSE / Streamable HTTP with auth and rate limiting.12Apache 2.0
TDQS
Scored across 7 tools
Each tool has a distinct resource+action: list_templates, get_template_schema, validate_template, render, convert_to_pdf, get_render, get_workspace. The descriptions explicitly disambiguate the closest pair (render vs convert_to_pdf, render vs get_render), leaving no realistic misselection.
Six of seven names follow a clean verb_noun pattern (get_workspace, list_templates, get_template_schema, validate_template, convert_to_pdf, get_render). Only the bare verb 'render' deviates, which is a minor but noticeable break in the otherwise consistent scheme.
Seven tools is well-scoped for a template rendering service: discovery (list_templates, get_template_schema, get_workspace), validation (validate_template), and execution (render, convert_to_pdf, get_render) each earn their place with no filler.
The core lifecycle — find template, inspect schema, validate, render/convert, poll status — is fully covered with no dead ends. Minor gaps remain (no template upload/create, no list of prior renders or cancel operation), but agents can work around them via the returned download_url and render_id.