Kordoc vs Word

A side-by-side look at the Kordoc and Word MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Kordoc logoKordocWorkplace & Productivity · Local subprocess (stdio)Parse Korean documents (HWP, HWPX, PDF, XLSX, DOCX, PPTX) to Markdown; fill forms, diff, render.49FairAuth: no auth requiredWord logoWordWorkplace & Productivity · Local subprocess (stdio)Microsoft Word automation for AI assistants. Requires Word for Windows.44FairAuth: not declared

Verdict: choose Kordoc for workplace & productivity work as a local process; choose Word 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?

Kordoc logoChoose 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.
Explore Kordoc

Word logoChoose Word when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: WORDMCP_SERVICE_MODE.
Explore Word

Feature & specification comparison

Rows where the two servers differ are marked.

SpecKordoc logoKordocWord logoWord
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal49/100 · Fair44/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedWORDMCP_SERVICE_MODE
Verified ownerCommunity listingCommunity listing
GitHub stars2,7402
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Kordoc tools

No tool names declared yet. Check the project README from the listing page.

Word 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.

Kordoc

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kordoc": {
      "command": "npx",
      "args": [
        "-y",
        "kordoc"
      ]
    }
  }
}

Word

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "word": {
      "command": "npx",
      "args": [
        "-y",
        "@vscode/vsce"
      ],
      "env": {
        "WORDMCP_SERVICE_MODE": "YOUR_WORDMCP_SERVICE_MODE_HERE"
      }
    }
  }
}

Frequently asked questions

Kordoc is categorized under Workplace & Productivity and uses a local stdio subprocess. Word belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Kordoc for workplace & productivity work and Word 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.

Kordoc is listed as free. Auth: no auth required. Word has no declared pricing — check the project's own site. 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 kordoc and word as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Kordoc has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 2,740 GitHub stars. Word has 44/100 (Fair) with 0 views, 0 installs and 2 GitHub stars.