Set up DoDomain in Cursor

Connect the MCP server

1. 1. Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project only). If the file exists, merge the dodomain entry into its mcpServers object.

   File: ~/.cursor/mcp.json

   {
     "mcpServers": {
       "dodomain": {
         "url": "https://app.dodomain.io/api/mcp"
       }
     }
   }

   Copy

Sign in. Cursor discovers the OAuth endpoints from the URL. When dodomain shows as needing login in Cursor Settings under MCP, click it to open the DoDomain sign-in and consent page. No API key is involved: the MCP server uses OAuth and refuses secret keys by design.

What you get

• The DoDomain MCP server at https://app.dodomain.io/api/mcp, with OAuth sign-in and 68 tools that cover every dashboard action.
• The SDK for your stack: @dodomain/node, dodomain-sdk, @dodomain/connect, @dodomain/react, with the secret key read from DODOMAIN_SECRET_KEY.
• A verified setup: the agent calls list_apps and the REST API before it reports back.

Install the SDK

Server code uses a secret key from DODOMAIN_SECRET_KEY. Create an app at https://app.dodomain.io/dashboard and copy the secret key from its API keys card. It is shown once.

• @dodomain/node (Node.js 20+ server)

  Create connect sessions, manage connections, verify signed webhooks.

  npm install @dodomain/node

  Copy

• dodomain-sdk (Python 3.10+ server)

  The same server surface as @dodomain/node, sync and async.

  pip install dodomain-sdk

  Copy

• @dodomain/connect (Browser)

  Opens the hosted connect flow as a sheet inside your own UI, driven by a session token your server minted.

  npm install @dodomain/connect

  Copy

• @dodomain/react (React)

  The widget as a useDoDomainConnect hook.

  npm install @dodomain/react

  Copy

Verify

After signing in, ask the agent to call the list_apps tool: it lists the apps on your team. To check a secret key, run:

curl -s https://app.dodomain.io/api/v1/apps -H "Authorization: Bearer $DODOMAIN_SECRET_KEY"

Success is HTTP 200 with a JSON body of the form {"apps": [...]}: a secret key sees exactly its own app, with its id, name and publishable key.