Connect Cursor
Add AdCopilot to Cursor with one link, sign in with Google and press Approve. How approvals work in Cursor, why a copy from cursor.directory may be listed as "server", and how to reconnect.
Cursor adds AdCopilot from one link. Your Google products are connected in the dashboard at app.adcopilot.cloud, not in Cursor. See Connect Google Ads.
Add it
The link opens Cursor's install screen for a server named adcopilot at
https://mcp.adcopilot.cloud/mcp. Install it there. The Add to Cursor
button on the dashboard's AI assistants page does the same.
Or add it by hand: put this in ~/.cursor/mcp.json for every project, or in
.cursor/mcp.json inside one project.
{
"mcpServers": {
"adcopilot": {
"url": "https://mcp.adcopilot.cloud/mcp"
}
}
}Sign in
Cursor then opens AdCopilot's sign-in in your browser: sign in with Google and press Approve on Let Cursor use your AdCopilot?. There is no API key to paste. You can withdraw the access from Connections in the dashboard at any time.
If Approve did nothing on an earlier try, remove AdCopilot in Cursor, add it again and press Approve once. See Approve does nothing.
Then ask
In Cursor's agent chat:
Get me started with AdCopilot
Installed from cursor.directory
AdCopilot is also listed on cursor.directory, with the plugin's commands. Its Add to Cursor installs the same connector, but Cursor may list it as server rather than adcopilot. Look for that name in Cursor's MCP list and on its approval cards. The link above names it adcopilot. Keep one of the two: if you have both, remove one.
Approvals in Cursor
AdCopilot proposes each change first. For a hard stop, set Cursor's run mode to Allowlist and keep AdCopilot's write tools off the allowlist (Cursor's cloud agents never ask).
Cursor has no Needs approval setting like Claude's. Its run mode, under Settings → Agents → Approvals & Execution, decides whether it stops before a tool runs:
- Allowlist: only the tools on the allowlist run unasked. Add AdCopilot's read tools if you like, and keep its write tools off it.
- Auto-review, Cursor's default: allowlisted tools run at once and a classifier decides about the rest, so a write can run without anyone being asked.
- Run Everything: no tool waits.
- Cloud agents: Cursor's cloud agents never ask.
Whatever Cursor allows, the limits on AdCopilot's server hold: it deletes nothing but negative keywords (see It can never delete), it will not switch on the first campaign it builds for you, it refuses spending past your monthly cap, and it never publishes a Tag Manager container. See Approval-gated writes.
Reconnect
Cursor keeps the tool list it loaded when it connected. After an AdCopilot release adds tools, switch AdCopilot (or server) off and on again in Cursor's MCP list. If a tool is still missing, remove it and add it again with the link above. Or Revoke Cursor under Connections in the dashboard, and it re-approves with the full set next time.
Connecting another Google product needs nothing in Cursor, unless Connections marks it Re-authorization needed. See A tool is missing or out of date.
The Claude Code plugin
For developers on Claude Code. The AdCopilot plugin registers the connector for you and adds three skills and five commands. What it contains, how to install it, and what to do if you added the connector by hand first.
Connect Gemini CLI
Add AdCopilot to Gemini CLI with one command over HTTP, sign in, and ask from the terminal.