DocMake

Your documents, generated by your AI assistant.

The official DocMake server for the Model Context Protocol. Ask Claude for an invoice in plain language; it picks the template, fills in the data, and hands you the finished PDF.

It ships on npm as @docmake/mcp and runs locally through npx, so the only requirements are Node.js 18 or newer and a DocMake API key. It works on the free plan, and it gives an assistant six tools: list templates, inspect a template's fields, render a document, create a template, import a DOCX, and check usage. The source is on GitHub under the MIT license, and the same six tools are also hosted at app.docmake.io/mcp/v1 if you would rather install nothing.

A conversation, not an integration

MCP is the open standard that lets AI assistants use external tools. With the DocMake server installed, your assistant gains six document tools and uses them on its own: it finds the right template, asks you for any missing values, and saves the rendered file to your Downloads folder.

Renders are strict by default. If a variable has no value, the assistant gets the exact list of missing fields instead of a half-empty document, so it asks you rather than inventing numbers.

Templates stay in DocMake: design them once in the visual editor or start from the gallery, then render them from anywhere.

Claude

Generate the invoice for Acme Corp: 10 hours of consulting at 100 EUR, due in 14 days.

tool list_templates → Invoice (tmpl_ZjqIJk...)
tool get_template → client_name, items[], due_date...
tool render_document → invoice-acme.pdf

Done. Your invoice for Acme Corp (1,000.00 EUR, due August 23) is saved at ~/Downloads/DocMake/invoice-acme.pdf.

Setup

1. 01 Create a free DocMake account and add a template: start from the gallery, import a DOCX, or design your own.
2. 02 Create an API key in Settings → API Keys.
3. 03 Add the server to your AI tool with the config on the right. Node.js 18+ is the only requirement.

Rendered files are saved to ~/Downloads/DocMake by default; set DOCMAKE_OUTPUT_DIR to change it.

{
  "mcpServers": {
    "docmake": {
      "command": "npx",
      "args": ["-y", "@docmake/mcp@latest"],
      "env": {
        "DOCMAKE_API_KEY": "dm_your_api_key"
      }
    }
  }
}

Settings > Developer > Edit Config, then restart Claude Desktop.

Remote, nothing to install

The same six tools, hosted

DocMake also runs the server for you at https://app.docmake.io/mcp/v1, spoken over streamable HTTP. A client that supports remote MCP needs no package and no Node.js: just the URL and one header, Authorization: Bearer dm_..., carrying the same API key the REST API uses.

Two things differ from the local package, because the server runs on our side rather than on your machine. render_document returns a short-lived download link instead of writing the file to disk, and import_docx takes the document as base64 rather than a path. Strict rendering, workspace scoping and the plan rate limits behave as they do over REST, where one MCP message counts as one request.

Claude.ai and ChatGPT add remote servers as custom connectors, and those are documented around an OAuth flow rather than a static key, so this setup does not reach them yet. For Claude Desktop, use the npx configuration above.

claude mcp add --transport http docmake \
  https://app.docmake.io/mcp/v1 \
  --header "Authorization: Bearer dm_your_api_key"

Adds the server to the current project. Pass --scope user to make it available everywhere.

Six tools, the full document loop

Everything an assistant needs to go from request to rendered file, including creating and importing templates without leaving the conversation.

Tool	What it does
list_templates	List the templates in your workspace, with search and pagination
get_template	A template’s field tree: every variable it expects, ready to map to data
render_document	Render a template to PDF or DOCX and save the file locally
create_template	Create a new template from a document schema
import_docx	Import a local Word file as a new template
get_usage	Plan, render quota, and rate limits for the billing period

Prefer raw HTTP? The same capabilities are available over the REST API.

Source and listings

The local server is open source, published on npm, and listed in the official Model Context Protocol registry, so you can read the code before you run it.

[

Source

docmake-io/mcp

Open source under the MIT license, tagged v0.1.1.

](https://github.com/docmake-io/mcp)[

Package

@docmake/mcp

Version 0.1.1 on npm, run with npx, no global install.

](https://www.npmjs.com/package/@docmake/mcp)[

Registry

io.docmake/mcp

Listed in the official Model Context Protocol registry.

](https://registry.modelcontextprotocol.io/v0/servers?search=io.docmake/mcp)

Questions

What is the DocMake MCP server?

An open-source npm package (@docmake/mcp) that connects AI assistants to your DocMake account through the Model Context Protocol. Once installed, assistants like Claude can list your templates, check which fields they need, and render finished PDF or DOCX documents from a plain conversation.

Which AI tools work with it?

Any MCP client: Claude Desktop, Claude Code, Cursor, Zed, Windsurf, and others. Configuration is the same everywhere: run @docmake/mcp via npx with your API key in the environment. Claude Code, Cursor and VS Code can also point at the hosted server instead, with the API key sent as an Authorization header.

Is it open source?

Yes. The server is published at github.com/docmake-io/mcp under the MIT license, the package is @docmake/mcp on npm, and it is listed in the official Model Context Protocol registry as io.docmake/mcp.

Can I use it without installing anything?

Yes. DocMake hosts the same six tools at https://app.docmake.io/mcp/v1 over streamable HTTP. Point a client that supports remote MCP at that URL and send your API key as an Authorization: Bearer dm_... header. Rendered documents come back as short-lived download links rather than local files, and import_docx takes base64 instead of a file path.

Does it need a paid plan?

No. The free plan includes API access, so the MCP server works from the moment you sign up. Paid plans raise the monthly document volume and remove the footer branding.

Is my data safe?

The local server runs on your machine and talks only to the DocMake API over HTTPS with your API key. Rendered documents are saved to a folder you control. The hosted server runs inside DocMake and handles your data the same way the REST API does, under the same privacy policy. Nothing is sent to any third party either way.