Skip to main content
The SuperDoc MCP server lets AI agents open, read, edit, and save .docx files. It exposes the same operations as the Document API through the Model Context Protocol — the open standard for connecting AI tools to agents.
The MCP server is in alpha. Tools and output formats may change.

Setup

Install once. Your MCP client spawns the server automatically on each conversation.

Workflow

Every interaction follows the same pattern: open, read or edit, save, close.
  1. superdoc_open loads a .docx file and returns a session_id
  2. superdoc_find locates content and returns target addresses
  3. Edit tools (superdoc_insert, superdoc_replace, superdoc_delete, superdoc_format) use those addresses
  4. superdoc_save writes changes to disk
  5. superdoc_close releases the session

Tools

23 tools in eight groups. All tools take a session_id from superdoc_open.

Lifecycle

Query

Mutation

All mutation tools accept suggest? — set to true to make the edit a tracked change instead of a direct edit.

Format

Create

Track changes

Review and resolve tracked changes (suggestions) in the document.

Comments

Add and manage comments anchored to text ranges.

Lists

Suggesting mode

Set suggest=true on any mutation, format, or create tool to make edits appear as tracked changes. The document stays unchanged until someone accepts the suggestions — in Word, in SuperDoc’s browser editor, or programmatically via the track changes tools.

How it works

The MCP server runs as a local subprocess, communicating over stdio. It manages document sessions in memory — each superdoc_open creates an Editor instance, and all subsequent operations run against that in-memory state until you superdoc_save.
Your documents never leave your machine. The server runs locally, reads files from disk, and writes back to disk.

Debugging

Test the server directly with the MCP Inspector:
This opens a browser UI where you can call each tool manually and inspect the raw JSON-RPC messages.
  • LLM Tools — build custom LLM integrations with the SDK
  • CLI — edit documents from the terminal
  • SDKs — typed Node.js and Python wrappers
  • Document API — the in-browser API that defines the operation set
  • AI Agents — headless mode for server-side AI workflows