Docx Forge vs Kordoc
A side-by-side look at the Docx Forge and Kordoc MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Docx Forge for workplace & productivity work as a local process; choose Kordoc for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Docx Forge when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You want tools like
create_document, read_document, add_section.
Choose Kordoc when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 47/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2,740 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Docx Forge | View Kordoc |
Tools & capabilities
Docx Forge tools 8
create_documentCreate a new `.docx` from a title and markdown contentread_documentExtract text, headings, paragraphs, and metadata from a `.docxadd_sectionAppend a new section (heading + body) to an existing `.docxreplace_textFind and replace text — ideal for template variable substitutionadd_tableInsert a formatted table with bold headers into a `.docxmerge_documentsCombine multiple `.docx` files into oneexport_to_pdfConvert `.docx` to PDF via LibreOffice or pandocget_document_statsGet word count, page estimate, section count, table count
Kordoc tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Docx Forge
{
"mcpServers": {
"docx-forge": {
"command": "npx",
"args": [
"docx-forge-mcp"
]
}
}
}
Kordoc
{
"mcpServers": {
"kordoc": {
"command": "npx",
"args": [
"-y",
"kordoc"
]
}
}
}
Frequently asked questions
Docx Forge is categorized under Workplace & Productivity and uses a local stdio subprocess. Kordoc belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Docx Forge for workplace & productivity work and Kordoc for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Docx Forge has no declared pricing — check the project's own site. Kordoc is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add docx-forge and kordoc as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Docx Forge has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Kordoc has 49/100 (Fair) with 2 views, 0 installs and 2,740 GitHub stars.