Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/z1w2r3/doc-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/z1w2r3/doc-mcp/docxtpl-mcp)<a href="https://agentmods.dev/mcp/z1w2r3/doc-mcp/docxtpl-mcp"><img src="https://agentmods.dev/badge/mcp/z1w2r3/doc-mcp/docxtpl-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/z1w2r3/doc-mcp/docxtpl-mcp"><img src="https://agentmods.dev/badge/mcp/z1w2r3/doc-mcp/docxtpl-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
docxtpl-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "docxtpl-mcp": { "command": "npx", "args": [ "-y", "docxtpl-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 9 lines scan A 694d5b8432c7
docxtpl-mcp is an MCP server published in the GitHub repository z1w2r3/doc-mcp (1 stars, last pushed 10mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
carbone-mcp
Generate PDF/DOCX/XLSX/PPTX from templates+JSON. Convert Office/HTML/MD to PDF. Universal templating. Runs locally from the carbone-mcp npm package. Needs 2 environment variables to run.
sheetrender-mcp
MCP server for SheetRender: render PDFs from HTML templates and spreadsheet data. Runs locally from the @sheetrender/mcp npm package. Needs 2 environment variables to run.
docgen-mcp-server
Render HTML/markdown to PDF, export rows to xlsx, and fill AcroForm PDFs. Runs locally from the @cyanheads/docgen-mcp-server npm package. Needs 6 environment variables to run.
parse
Deterministic DOCX/PPTX/XLSX/PDF parser: track changes, comments, headers, footers, merged cells. Runs locally from the @ailang/parse npm package. Needs 2 environment variables to run.
groupdocs-conversion-mcp
MCP server "groupdocs-conversion-mcp" as configured in groupdocs-conversion/GroupDocs.Conversion.Mcp. Launched with GroupDocs.Conversion.Mcp. Needs 3 environment variables to run.
justfill
Fill existing PDF forms from JSON or Excel with MCP agents; review fields and reuse templates. Runs locally from the justfill-mcp Python package. Needs 1 environment variable to run.