Home · Setup · VS Code

MCP Docx in VS Code

Real Word documents from chat: proposals, contracts, quotes. It writes .docx files from sections or from markdown, generates priced proposals and freelance service agreements with reference numbers that never repeat, reads an existing Word file back as text and outline, and fills {{placeholders}} in a template while keeping its styles.

doc_to_html is the PDF route, and VS Code is the client where that is least awkward: the HTML lands in the Explorer, opens in a preview, and prints from the browser with the print stylesheet applied.

What you get in VS Code

You say	Tool
Write a proposal for Beta Corp: checkout rebuild, 4,500 EUR, three phases.	`proposal_create`
Fill my NDA template with this client's details.	`doc_fill_template`
What does this proposal.docx actually say?	`doc_read`

The worked proposal issued PROP-2026-0001 at EUR 4,500.00 with a timeline table and a signature block. Template filling substitutes on the joined paragraph text, so a placeholder Word split into three runs is still replaced.

Install it in VS Code

The file is .vscode/mcp.json, and the key inside it is servers.

Scope	Path
This workspace	`<workspace>/.vscode/mcp.json`
Every workspace	`the user profile mcp.json, opened by the MCP: Open User Configuration command`

// .vscode/mcp.json  (the key is "servers")
{
  "servers": {
    "docx": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-docx"]
    }
  }
}

Or from a terminal:

code --add-mcp '{"name":"docx","command":"npx","args":["-y","@theluckystrike/mcp-docx"]}'

VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.

The npm publish of @theluckystrike/mcp-docx is pending; until then use the .mcpb bundle or a clone and build from the latest release.

No install: the hosted endpoint

There is no hosted endpoint for this one yet. MCP Docx runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Three of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP: time-tracker, price-tracker and invoice.

VS Code notes worth knowing first

The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.

Free: unlimited create, convert and read; 3 proposals or contracts per calendar month; templates up to 10 placeholders. Pro is $19 once, verified offline.

Questions

Why does my mcp.json do nothing?

The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.

Do I have to edit the file at all?

No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.

Where do the MCP Docx tools show up?

In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.

MCP Docx in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs