Add DocRocket to Cursor

Add DocRocket as an MCP server in Cursor and generate branded documents directly from the AI chat. Two ways: via Settings UI or by editing mcp.json.

Need a DocRocket account?

Sign up at app.docrocket.ai — email only, no credit card.

Sign up free →

Option 1: Via Cursor Settings UI

    1

    Open MCP Settings

    In Cursor: Settings → MCP (or use the command palette: Cursor: Open MCP Settings).

    2

    Add new MCP server

    Click Add new MCP server and enter:

    Name: Docrocket
URL:  https://mcp.docrocket.ai/v1/mcp-tools/docrocket-control/mcp
    3

    OAuth on first use

    The first time Cursor calls a DocRocket tool, it will trigger the OAuth flow — sign in to your DocRocket account when prompted. Cursor caches the token after that.

Option 2: Edit mcp.json directly

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "Docrocket": {
      "url": "https://mcp.docrocket.ai/v1/mcp-tools/docrocket-control/mcp"
    }
  }
}

Restart Cursor after editing the file. OAuth will be triggered on the first tool call.

Why use DocRocket in Cursor?

Cursor is popular with developers building products that include document generation. Adding DocRocket to Cursor lets you:

  • Test document generation output directly in your development environment before deploying
  • Generate documents to review designs and template layouts while building
  • Use Cursor Agent to prototype document generation workflows quickly
  • Get your DocRocket brand IDs and template slugs from the agent chat, which you then hardcode in your product's code

Connect other AI tools

→ Connect Claude → Connect ChatGPT → Custom agent guide

Frequently asked questions

What can DocRocket do in Cursor?

In Cursor Agent mode, DocRocket can extract brand from any URL, generate branded proposals and documents, list saved brands and templates, and return PDF and web URLs. Useful for developers building products where document generation is a feature — you can test the full pipeline directly in your editor.

Do I need an API key?

No. Cursor handles the OAuth handshake the first time a DocRocket tool is called. After that, the token is cached and reused automatically.