Document Engine

Programmatic document editing — in the browser, from the terminal, or through SDKs

Document Engine gives you four ways to read and edit .docx files without a visible editor:

Surface	Best for	Runtime
Document API	In-browser editing via editor.doc.*	Browser
SDKs	Backend automation with typed methods	Node / Python
CLI	Scripts and CI pipelines	Any shell
MCP Server	AI agents (Claude Code, Cursor, custom)	Local subprocess

All four sit on the same underlying document capabilities. The browser, SDK, and CLI expose individual operations directly; MCP exposes grouped intent tools such as superdoc_search, superdoc_get_content, and superdoc_edit.

How it works

The Document API defines the canonical operations. The CLI and MCP server wrap them for different consumers. The SDKs manage the CLI process and expose typed methods.

Which surface should I use?

Your setup	Surface	Why
Web app with a visible editor	Document API	Direct access via editor.doc.* — no network round-trips
AI agent (Claude Code, Cursor, Windsurf, custom)	MCP Server	Sessions keep the editor alive across tool calls
Backend automation (Node.js / Python)	SDKs	Typed methods, session management, error handling built in
Shell scripts or CI pipelines	CLI	Stateless one-shot commands — no process to manage
Serverless (Lambda, Vercel, Workers)	CLI or SDKs	Open the file, run the operation, return the result