Superdocs MCP Server

If you already use Superdocs, the superdocs mcp server is the piece that lets your assistant work with it directly. Edit, draft, summarize, export styled .docx/PDF/HTML/MD/RTF via 21 MCP tools + 4 prompts.

What the server does

Edit, draft, search, summarize, and export styled documents (.docx / PDF / HTML / Markdown / plain text) directly from Claude Code via the SuperDocs MCP server.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Auto — loading skill** — Claude reaches for SuperDocs proactively when you ask to edit, draft, or export documents
• Component — What
• Skill — skills/superdocs/SKILL.md — auto-loads when you ask document work
• Client — Tools
• Cursor — ✅ (via MCP or the bundled .cursor-plugin/ install)

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Superdocs's toolset — Auto, Component, Skill and 2 more — is a fair guide to whether it matches your workflow. It is maintained by app.superdocs; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.