A
licenseNot graded
qualityB
maintenanceEnables AI assistants to generate PDFs from templates using dynamic data, manage async PDF jobs, list templates, and check account credits and transaction history through natural language.
22 npm
MIT
@docmake/mcp
Officialby docmake-io
Related Servers
Alternatives to @docmake/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to generate format-stable, editable Word DOCX documents from structured content and reusable templates, with document type recognition, schema retrieval, template rendering, validation, and conservative fixes.MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to create, edit, and extract data from Microsoft Word documents programmatically, supporting document creation, content editing, table manipulation, parameter extraction, and template 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.11 npm1MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to create and manipulate Microsoft Word documents programmatically with support for rich text formatting, tables, lists, headings, and find-and-replace operations.1012 npmMIT
documenteroofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to list Documentero templates, inspect their field schemas, and generate Word/PDF/Excel documents via the Documentero API.32 npmMIT
TDQS
A4.4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool maps to a distinct operation: listing, fetching metadata, rendering, creating from schema, importing from docx, and checking usage. The two creation tools are clearly differentiated by input format and described use cases.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern such as list_templates, get_template, and render_document. Minor differences in noun choice are understandable and do not create confusion.
Tool Count5/5
Six tools is well-scoped for a template management and rendering server. Each tool serves a distinct, necessary purpose and none feels redundant or superficial.
Completeness3/5
The server covers list, get, create, import, and render, which handles the core workflow, but it lacks update_template and delete_template operations. This is a notable gap for template lifecycle management and limits autonomous agent workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues