Claude Code
The fastest way to connect SuperDocs to Claude Code is the official plugin — it bundles the MCP server (38 tools), the 4 workflow prompts, and the auto-loading skill in one install. Manual MCP config also works as a fallback.Install via plugin (recommended)
In a Claude Code session, add the SuperDocs marketplace, then install the plugin from it:plugin-name@marketplace-name (superdocs@superdocs-plugin), not the GitHub repo path. Passing the repo path to install directly (claude plugin install superdocsapp/superdocs-plugin) fails with “doesn’t exist in marketplace”. That repo path is only valid for marketplace add.
You’ll be prompted for your SuperDocs API key (sk_…). It’s stored securely in your OS keychain — never in plaintext config. Get a key from use.superdocs.app → Settings → API Keys → Create. Free plan includes 500 AI operations per month.
After install:
- All 38 MCP tools are available
- 4 workflow prompts appear in your
/slash menu (/superdocs:draft_from_outline,/superdocs:edit_styled_docx,/superdocs:convert_format,/superdocs:review_contract_for_redflags) - The SuperDocs skill auto-loads when you ask document-editing questions
Manual setup (advanced)
If you prefer to configure the MCP server directly without the plugin (e.g., to share a.mcp.json across a team via project scope), run:
/mcp and /mcp/ are accepted; the trailing-slash form is the canonical spelling.
That installs only the MCP server (38 tools). To get the 4 prompts and the skill, you’d need to set those up separately — the plugin install above does all three in one shot.
Verify the connection
✗ Failed to connect, restart Claude Code (Ctrl+C then claude in a new shell). MCP servers load at session startup, so a fresh session is required after claude mcp add.
Test it
Example usage
Once connected, you can ask Claude Code to:- “Create a technical specification document using SuperDocs”
- “Edit my SuperDocs session and update the introduction”
- “Upload this file as an attachment to my SuperDocs session”