@docmake/mcp

MCPcommunity
v0.1.1UnknownMITUpdated 23d agonpmGitHub

Model Context Protocol server for DocMake - lets AI assistants generate DOCX and PDF documents from your templates.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
12Downloads/wk
23d agoLast update
Needs 1 credential before it runs
  • DOCMAKE_API_KEYAPI keyrequired

    DocMake API key, created at app.docmake.io under Settings > API Keys

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version0.1.1
Sourcenpm+mcp-registry
npm@docmake/mcp
GitHubdocmake-io/mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv0.1.1 · 22d agoHow well does this scan work?
EvalsNone
IndexedSep 1, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagev0.1.1 · 22d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_templatesList the DocMake templates in the connected workspace. Returns each template's id, name,

List the DocMake templates in the connected workspace. Returns each template's id, name,

No input schema was published for this tool.

get_templateGet a template's metadata and its field tree: every variable the template expects, as dotted

Get a template's metadata and its field tree: every variable the template expects, as dotted

No input schema was published for this tool.

render_documentRender a DocMake template to PDF or DOCX with the given data and save the file locally.

Render a DocMake template to PDF or DOCX with the given data and save the file locally.

No input schema was published for this tool.

create_templateCreate a new DocMake template from a document schema JSON. The schema is DocMake's

Create a new DocMake template from a document schema JSON. The schema is DocMake's

No input schema was published for this tool.

import_docxImport a local .docx file as a new DocMake template. The document's structure (headings,

Import a local .docx file as a new DocMake template. The document's structure (headings,

No input schema was published for this tool.

get_usageGet the workspace's plan, renders used vs. limit for the current billing period, template

Get the workspace's plan, renders used vs. limit for the current billing period, template

No input schema was published for this tool.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Model Context Protocol server for DocMake - lets AI assistants generate DOCX and PDF documents from your templates.

Keywords
mcpmodel-context-protocoldocmakedocument-generationdocxpdftemplatesai
Alternatives
Comparing tool surfaces…

Tools exposed

6 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-01 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in documents & pdfs