MCP Integration
The Model Context Protocol (MCP) lets AI tools connect to external services. SuperDocs exposes an MCP server with 21 tools and 4 user-invocable workflow prompts for document editing, session management, attachments, and more — all on a single endpoint athttps://api.superdocs.app/mcp.
When connected, SuperDocs tools appear natively in your AI tool — no API client code needed.
Where to find SuperDocs
You can install SuperDocs from any of these public channels (most users only need one):| Channel | What it gives you | Install |
|---|---|---|
| Claude Code plugin (recommended for Claude Code) | MCP server + 4 workflow prompts + auto-loading skill in one command | claude plugin marketplace add superdocsapp/superdocs-plugin && claude plugin install superdocs@superdocs-plugin |
| Official MCP Registry | Streamable HTTP endpoint discovered automatically by VS Code Copilot @mcp search, GitHub MCP Registry, Goose Extensions, PulseMCP, Glama and other MCP-aware tools | Auto-pulled — no action needed in supported clients (search superdocs in your tool’s MCP catalog) |
| skills.sh (cross-agent skill registry) | Auto-loading skill that works with Cursor, GitHub Copilot, Gemini CLI, Cline, Codex, Continue, Goose, Windsurf, Amp, and more | npx skills add superdocsapp/superdocs-plugin |
| Manual MCP config (any MCP client) | Direct endpoint connection via your tool’s MCP config file | See per-client setup below |
instructions field returned during the protocol handshake.
Prerequisites
- A SuperDocs account (sign up free)
- An API key (see API Keys or MCP Setup)
Connection details
| Field | Value |
|---|---|
| Endpoint | https://api.superdocs.app/mcp |
| Transport | Streamable HTTP |
| Auth header | Authorization: Bearer sk_YOUR_API_KEY |
Supported clients
Claude Code
One install command — plugin bundles tools + prompts + skill
Claude Desktop
Add to claude_desktop_config.json
Cursor & VS Code
Add to .cursor/mcp.json or VS Code settings
Quick test
After connecting, ask your AI tool:“Use the SuperDocs health tool to check the API status”If the connection is working, you’ll get back
{"status": "healthy"}.
Troubleshooting
Tools panel says “Loading tools” forever — restart your AI tool. MCP servers load at startup, so a fresh session is required after adding the server. Connection fails or times out — verify your API key works:200 response (with a JSON list of your sessions, possibly empty) confirms the key is valid. A 401 means the key is wrong, revoked, or the Authorization header didn’t reach the server.
