Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Generate DOCX and PDF documents from your DocMake templates
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
DOCMAKE_API_KEY, DOCMAKE_OUTPUT_DIR, DOCMAKE_API_BASEValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"docmake": {
"command": "npx",
"args": [
"-y",
"@docmake/mcp"
],
"env": {
"DOCMAKE_API_KEY": "your-value",
"DOCMAKE_OUTPUT_DIR": "your-value",
"DOCMAKE_API_BASE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add docmake --env DOCMAKE_API_KEY=your-value --env DOCMAKE_OUTPUT_DIR=your-value --env DOCMAKE_API_BASE=your-value -- npx -y @docmake/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"docmake": {
"command": "npx",
"args": [
"-y",
"@docmake/mcp"
],
"env": {
"DOCMAKE_API_KEY": "your-value",
"DOCMAKE_OUTPUT_DIR": "your-value",
"DOCMAKE_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"docmake": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@docmake/mcp"
],
"env": {
"DOCMAKE_API_KEY": "your-value",
"DOCMAKE_OUTPUT_DIR": "your-value",
"DOCMAKE_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
DOCMAKE_OUTPUT_DIR envDOCMAKE_API_BASE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain docmake.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: DOCMAKE_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Official Model Context Protocol server for DocMake, the AI-native document generation platform. It lets AI assistants like Claude generate DOCX and PDF documents from your DocMake templates: no glue code, just a conversation.
"Generate the invoice for Acme Corp: 10 hours of consulting at 100 EUR, due in 14 days."
The assistant picks your invoice template, fills in the data, renders a PDF through the DocMake API, and hands you the file path.
You need a DocMake API key. Create one at app.docmake.io under Settings > API Keys (free plan works).
Add to claude_desktop_config.json (Settings > Developer > Edit Config):
{
"mcpServers": { "docmake": { "command": "npx", "args": ["-y", "@docmake/mcp@latest"], "env": { "DOCMAKE_API_KEY": "dm_your_key_here" } } } }
claude mcp add docmake --env DOCMAKE_API_KEY=dm_your_key_here -- npx -y @docmake/mcp@latest
Any client that supports stdio MCP servers works with the same command: npx -y @docmake/mcp@latest with DOCMAKE_API_KEY in the environment.
DocMake also hosts the same six tools over streamable HTTP, so a client that speaks remote MCP needs nothing installed:
{
"mcpServers": { "docmake": { "url": "https://app.docmake.io/mcp/v1", "headers": { "Authorization": "Bearer dm_your_key_here" } } } }
Two differences from this package. render_document returns a short-lived download link instead of writing the file to your machine, and import_docx takes the document as base64 rather than a path, because the server runs remotely and cannot read your disk. Everything else, including strict rendering, behaves the same.
| Variable | Required | Default | Purpose |
|---|---|---|---|
DOCMAKE_API_KEY | yes | API key from app.docmake.io, Settings > API Keys | |
DOCMAKE_OUTPUT_DIR | no | ~/Downloads/DocMake | Where rendered documents are saved |
DOCMAKE_API_BASE | no | https://app.docmake.io/api/v1 | API base URL, override for self-hosted setups |
| 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 render 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 JSON |
import_docx | Import a local .docx file as a new template (base64 on the remote server) |
get_usage | Plan, render quota, and rate limits for the current billing period |
The server also exposes your templates as MCP resources and ships a generate-document prompt for a guided render flow.
render_document is strict by default: if any template variable has no value in data, the render fails and returns the list of missing keys, so the assistant can ask you for the values instead of producing an incomplete document. Pass strict: false to render with each variable's fallback text instead.
Variables can declare a default value in the template editor. A defaulted variable never counts as missing: omit it from data and the default is rendered, even in strict mode. get_template shows each field's default (and example, a preview-only sample that is never rendered).
Rendered files are saved to DOCMAKE_OUTPUT_DIR and never overwrite an existing file.
Full policy: https://docmake.io/privacy
What this server collects. Nothing of its own. It has no telemetry and no analytics, and it never reads your chat history, memory, or files other than a .docx you explicitly pass to import_docx.
What it sends, and where. Every tool call is a request to the DocMake API at https://app.docmake.io/api/v1 over HTTPS, authenticated with your API key. Those requests carry only what the call needs: a template id, the data you asked to render, or the .docx you asked to import. DocMake processes that data to render your document.
Storage and retention. Your templates and account data live in your DocMake workspace and are retained until you delete them or close the account. Rendered documents are written to your own machine, under DOCMAKE_OUTPUT_DIR (~/Downloads/DocMake by default), and are never uploaded anywhere else. Your API key stays on your machine: the desktop extension keeps it in your operating system keychain, and a manual setup keeps it in your MCP client's config file.
Third-party sharing. Render data is not sold, and it is not shared with third parties beyond the subprocessors DocMake needs to run the service, listed in the full policy.
Contact. support@docmake.io for privacy questions, data export, or deletion.
MIT