Connect Cursor.

Connect Cursor to Ad Superpowers so its agent can answer questions using your advertising data. Start with OAuth; no API key is required.

Before you begin

• Cursor installed, with access to its agent and MCP connections.
• An Ad Superpowers account with an active trial or paid access; see pricing.
• A platform connected in the intended workspace under Integrations.

1. Add the server

Open or create ~/.cursor/mcp.json in your home directory. For a connection limited to one project, use that project's .cursor/mcp.json instead.

Add the following configuration. If the file already contains servers, add only the ad-superpowers entry inside its existing mcpServers object.

{
  "mcpServers": {
    "ad-superpowers": {
      "url": "https://mcp.adsuperpowers.ai/v1"
    }
  }
}

Save the file. The URL connects to the hosted service; there is no local server to install. The configuration locations and HTTP transport are documented in Cursor's MCP guide.

2. Sign in

Open Customize in Cursor's sidebar, find ad-superpowers among the MCP servers and enable it. Complete the offered OAuth sign-in in your browser.

On the Ad Superpowers authorization screen, choose the workspace containing your connected platform and approve access. Return to Cursor and check that the server's tools are available.

3. Check the result

In an agent conversation, ask:

Use Ad Superpowers to show my connected workspace and list the
advertising accounts I can access. Include account names and IDs.
Do not change anything.

Review any tool request before running it. Confirm that the response names the expected workspace and account. Then ask:

For [account name and ID], show campaign spend for the last 7 days.
Include the date range and currency. Do not change any campaigns.

Compare the account, dates and currency with the platform. Cursor must return an Ad Superpowers tool result for this check to count.

If something goes wrong

• Server is missing: check the JSON syntax and file location, then reopen Cursor. Avoid a second entry with the same name in your project configuration.
• Authentication fails: retry browser sign-in from the server controls. Check that the URL exactly matches the example.
• No tools are available: enable the server in Customize. Inspect Output → MCP Logs for the connection error; organization policy may require an administrator to allow the server.
• Wrong workspace: reconnect and select the intended workspace on the Ad Superpowers consent screen. Switching in the dashboard does not retarget an existing OAuth connection.
• Missing accounts or access denied: check the workspace's Integrations, your platform permissions and active trial or paid access. See troubleshooting for the next check.

Next steps

Try an example question or find supported operations in the tool reference.

Official sources

Client instructions checked on 18 September 2026 against Cursor's MCP documentation. It covers configuration, OAuth, server controls and connection logs.