Setup

Connect DocExport to Claude Desktop

Add DocExport as a custom connector, sign in once with OAuth, and Claude can generate branded PDF and DOCX documents from your Word templates — no JSON to edit, no API key to paste.

1

Open Connectors in Claude Desktop

DocExport is a remote MCP server, so you add it to Claude as a custom connector — no files to edit and nothing to install on your machine.

  • In Claude Desktop, open Settings.
  • Go to the Connectors section.
  • Click Add custom connector.
Note: Don't see "Add custom connector"? Update Claude Desktop to the latest version — custom connectors for remote MCP servers are a recent addition. Older builds only support the JSON config file (see the last step).
2

Paste the DocExport endpoint

In the dialog, give the connector a name (e.g. DocExport) and paste the DocExport MCP URL, then click Add:

  • Name: DocExport (anything you like).
  • URL: https://app.docexport.ai/mcp
  • Leave any advanced/auth fields blank — DocExport uses OAuth, which Claude discovers automatically.
https://app.docexport.ai/mcp
3

Sign in on the first tool call

The first time Claude uses a DocExport tool, a browser window pops open to sign in to your DocExport account. This is the OAuth 2.1 flow — DocExport never sees a long-lived key, and nothing sensitive is written to your machine.

  • Approve the sign-in in the browser window that opens.
  • Claude caches the short-lived token and reuses it automatically afterward.
  • Don't have an account yet? Sign up free at app.docexport.ai (25 documents/month on the free tier).
4

Confirm the four tools are connected

Open a new chat. You should see DocExport's four tools available to Claude:

  • list_templates — Claude reads each template's description to pick the right one.
  • get_template_schema — the full placeholder list with descriptions, examples, and required flags.
  • preview_generate — a dry run that reports missing or unresolved fields so Claude can self-correct.
  • generate_document — renders the final PDF or DOCX and returns a short-lived download link.
Tip: Ready to generate something? The sales-quote walkthrough takes you from a Word template to a Claude-generated PDF end to end.
5

Alternatives (optional)

The custom connector above is the recommended path. Two alternatives exist if you need them:

  • Static API key / headless use — if you want a dxp_* bearer key instead of OAuth (handy for CI), the Web UI's API-keys page generates a ready-to-paste Claude Desktop config snippet. Paste it into Settings → Developer → Edit Config (claude_desktop_config.json) and restart Claude. This path needs Node.js 20+ for the mcp-remote bridge.
  • One-click .mcpb bundle — a double-click installer is available at docexport.mcpb. It wraps the same connection, but the custom connector above is more reliable, so reach for the bundle only if you prefer a downloadable installer.
{
  "mcpServers": {
    "docexport": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://app.docexport.ai/mcp",
        "--header",
        "Authorization: Bearer dxp_<prefix>_<secret>"
      ]
    }
  }
}
Tip: Drop the --header line from the snippet to use OAuth instead of a static bearer token — the same flow the custom connector uses.
?

Troubleshooting

There's no "Add custom connector" option in my Settings.
Update Claude Desktop to the latest version (claude.ai/download) — custom connectors for remote MCP servers are a recent feature. On older builds, use the JSON config snippet in the "Alternatives" step instead.
The sign-in browser window never opens.
It only opens on the first tool call, so ask Claude to do something that uses DocExport — e.g. "list my DocExport templates." If a popup blocker swallowed it, allow popups for the sign-in domain and retry.
The tools don't show up after adding the connector.
Fully quit and reopen Claude Desktop (not just close the window), then open a new chat. Double-check the URL is exactly https://app.docexport.ai/mcp with no trailing slash or typo.
Can I use an API key instead of signing in each time?
Yes — mint a dxp_* key on the API-keys page in the web app and use the JSON config snippet with the --header line (see the "Alternatives" step). Treat the key like a password; revoke and re-mint it if it leaks.

Still stuck?

Email [email protected] with your template and the prompt you're trying to run — we usually reply same day.