Connect an AI client

AdCue exposes Google Ads tools over the Model Context Protocol (MCP) so AI clients can call them with your connected account.

Endpoint

https://mcp.adcue.app/mcp

In-app client guide: adcue.app/app/setup. Prerequisites:

Create an account
Connect Google Ads
Ensure your account has MCP / agent access for the clients you use

ChatGPT

Open the AdCue invitation or listing provided for your account (private beta rollout is staggered).
Sign in to AdCue when ChatGPT prompts you.
Connect Google Ads if you have not already (website or chat prompt).
Verify with a read prompt: “List my connected Google Ads accounts” or “Check my Google Ads connection.”
For writes, approve each mutation the client proposes.

One-click ChatGPT access may roll out after website connection. You can always connect Google Ads on the website first; both paths share the same connection.

Claude (Desktop / Code / Cowork)

Remote MCP URL

Add AdCue as a remote MCP server using the production URL above. Exact menus vary by Claude surface (directory install, Connectors, or manual MCP config). Typical remote config shape (client-specific fields may differ):

{
  "mcpServers": {
    "adcue": {
      "url": "https://mcp.adcue.app/mcp"
    }
  }
}

Auth

Complete AdCue OAuth / sign-in when the client prompts you.
If your plan uses API keys, create one at adcue.app/app/keys and paste it only into the client’s secret field — never into chat or tickets.

Claude directory / Cowork install flows may show Install → Manage → Connectors → Connect → Authorize. Prefer the in-app Setup screenshots when available.

Cursor

Open Cursor Settings → MCP (or the equivalent MCP servers panel).
Add a server named adcue with URL https://mcp.adcue.app/mcp.
Supply auth (OAuth or API key) as required by your account.
Restart MCP / reload the window if tools do not appear.
Test with a read tool via the agent (list campaigns or connection status).

Example mcp.json style entry:

{
  "mcpServers": {
    "adcue": {
      "url": "https://mcp.adcue.app/mcp"
    }
  }
}

Other MCP clients

Windsurf, Gemini CLI, Codex, and other MCP-compatible hosts follow the same pattern:

Register https://mcp.adcue.app/mcp as a Streamable HTTP / remote MCP server.
Authenticate as your AdCue user.
Confirm tools appear (search_tools, google_ads, connection helpers).
Start with read-only calls.

First prompts that stay safe

List my connected Google Ads accounts.
Show campaigns for customer 1234567890 (read only).
Search tools related to wasted spend.

Avoid create/remove tools until you have read Safety model.

API keys

Topic	Detail
Keys UI	adcue.app/app/keys
Format	`sk_live_…` personal access tokens
Create	Generate on Keys; copy once (full secret is never shown again)
Revoke	Revoke on Keys; revoked keys fail closed for MCP/API
Limits	Active key caps follow your plan (Free 2, higher on paid)

Treat keys like passwords. Rotate or revoke compromised keys from the Keys page. Do not commit keys to git or paste them into public issues.

Troubleshooting

Problem	What to try
Tools not listed	Reload MCP config; confirm URL path ends with `/mcp`; re-auth
No ad accounts	Complete Connect Google Ads first
ChatGPT unavailable	Invitation may not be active; use Claude/Cursor or wait for beta invite
Auth loops	Clear client MCP credentials, sign in again at adcue.app, retry
Writes rejected	Check plan entitlements and destructive confirm flags

Get started

Connect

Product

MCP & tools

Knowledge

Connect an AI client

Connect an AI client

Endpoint

ChatGPT

Claude (Desktop / Code / Cowork)

Remote MCP URL

Auth

Cursor

Other MCP clients

First prompts that stay safe

API keys

Troubleshooting

Next

​Connect an AI client

​Endpoint

​ChatGPT

​Claude (Desktop / Code / Cowork)

​Remote MCP URL

​Auth

​Cursor

​Other MCP clients

​First prompts that stay safe

​API keys

​Troubleshooting

​Next

Connect an AI client

Endpoint

ChatGPT

Claude (Desktop / Code / Cowork)

Remote MCP URL

Auth

Cursor

Other MCP clients

First prompts that stay safe

API keys

Troubleshooting

Next