Skip to main content
Document Engine is in alpha and subject to breaking changes while the contract and adapters continue to evolve.
Document Engine is the programmatic surface of SuperDoc. It gives you four ways to read and edit .docx files without a visible editor:
SurfaceUse caseRuntime
Document APIIn-browser editing via editor.doc.* methodsBrowser (ProseMirror)
SDKsNode.js and Python wrappers for backend automationNode / Python
CLITerminal commands for scripting and CI pipelinesAny shell
MCP ServerAI agent access via the Model Context ProtocolLocal subprocess
All four surfaces share the same operation set. An operation like find is available as editor.doc.find() in the browser, superdoc.doc.find() in the SDK, superdoc find in the CLI, and superdoc_find in MCP.

​
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. 
Document API (source of truth)
  → CLI (terminal interface)
  → MCP Server (AI agent interface)
  → Node SDK / Python SDK (typed wrappers over CLI)

​
Where to start

  • Building a web editor? Start with the Document API.
  • Automating documents from a backend? Start with the SDKs.
  • Scripting from the terminal or CI? Start with the CLI.
  • Connecting AI agents (Claude, Cursor, Windsurf)? Start with the MCP Server.