Connect Claude
Add the AdCopilot plugin to Claude on the web or desktop. Add, Connect, Approve, then say "Get me started with AdCopilot". Works on Claude's Free plan.
Claude on the web and the Claude desktop app take AdCopilot as a plugin from Claude's plugin directory: AdCopilot — Google Ads, Analytics, Search Console & Tag Manager. The plugin brings the AdCopilot connector with it, so there is nothing to type or paste: you add the plugin, connect its connector and approve it. It takes about two minutes, and it worked on Claude's Free plan when we checked.
Every label below is Claude's own, checked click by click on claude.ai on 3 October 2026. The Claude desktop app has the same Customize screens.
Before you start, connect Google Ads (and any other Google product) at app.adcopilot.cloud. See Connect Google Ads.
1. Open the AdCopilot plugin
This link opens the plugin's page in Claude. If you are signed out, Claude asks you to sign in first.
Open the AdCopilot plugin in Claude
To find it yourself, in Claude or the desktop app: in the sidebar choose
Customize, then Plugins, and search for AdCopilot. The first result
is AdCopilot — Google Ads, Analytics, Search Console & Tag Manager, from
Anthropic Directory.

2. Add the plugin
On the plugin's page, press Add.

The screenshots on this page are of an earlier version of the plugin, so its tabs may count differently from what you see.
Claude asks the same question for every plugin: the plugin may include components that run code, a red box warns that installing will grant access to everything available to Cowork, so only enable plugins from people you trust. Press Continue. AdCopilot's plugin is its skills, commands and agent, written as instructions for Claude, and one connector. Its source is public: AtromxIntelligence/adcopilot-claude-plugin.

Claude then says the plugin is installed and ready to use, and its switch is on. One step is left: its connector.
3. Connect the connector
Open the plugin's Connectors · 1 tab. It lists adcopilot as Not added. Press Connect.

Claude opens its Add custom connector box, already filled in by the
plugin: the name adcopilot and the URL https://mcp.adcopilot.cloud/mcp.
You can't edit them, and you don't need to. Press Continue.

The next screen shows Claude's sign-in settings. Sign in now and Use Claude's published identity are already selected and marked Detected. Don't change them. Scroll down and press Add.

4. Approve AdCopilot
If Claude first shows the connector's own page, You're not connected to adcopilot yet, press Connect there.
Our page opens, Let Claude use your AdCopilot?, and lists what Claude will be able to do. If you belong to more than one workspace, you pick one here. Press Approve. If Google Ads isn't connected yet, the page also offers Connect Google Ads first; you can just as well approve now and connect it afterwards, from Claude or from your dashboard.

You land back in Claude, and the plugin's Connectors tab shows adcopilot as Connected.

Added AdCopilot as a custom connector before? You don't need a second connector. The plugin's connector has the same URL, so Claude links it to the one you already have, and may not show AdCopilot's page at all. Carry on with step 5.
5. Let reads run without asking
In Claude, open Customize → Connectors and choose adcopilot. Under Tool permissions, Claude sorts AdCopilot's tools into Read-only tools and Write/delete tools, each on Needs approval to begin with. That is why Claude stops to ask ("Claude wants to use …") the first time each report runs.
Open the menu beside Read-only tools and choose Always allow. Leave Write/delete tools on Needs approval.


Reports and audits then run without a prompt each time. Claude still asks before every change while Write/delete tools stay on Needs approval: that prompt is Claude's, not AdCopilot's, so keep it. AdCopilot proposes each change in the chat first, and it can never delete. See Approval-gated writes.
6. Say hello
Start a new chat and send:
Get me started with AdCopilot

You don't need an @ in Claude: it picks AdCopilot on its own. With the plugin, Claude first reads its get-started skill, then asks AdCopilot what is connected and where you are, and tells you where you stand and what to do next. Claude's steps list that call as AdCopilot: workspace context (records visit). In the AdCopilot dashboard, Connect your AI shows Connected once Claude has made its first call.

Came here from an AdCopilot email or the audit page? Once AdCopilot shows as Connected, press that button again: it opens a new chat with your question already written, and a plugin added in the middle of a chat may only show up in a new one.
What the plugin adds
The connector is the same one every assistant uses. The plugin adds what a connector can't carry by itself: skills Claude uses on its own, and commands you type. The tables list the plugin's current version, the one in its repository. If Claude installed an earlier one, its Skills and Commands tabs list fewer.
The get-started skill, and the others
| Skill | Claude uses it when you | What it does |
|---|---|---|
adcopilot-connect | say "Get me started with AdCopilot", ask what is connected, or ask to connect or link Google Ads, Analytics, Tag Manager or Search Console | Says where you stand, then connects your Google products and links them to each other in the order that works. |
adcopilot-review | ask how your ads are doing, what they cost, what is wasting money, or what to pause, fix or do next | Reads the account and says what happened, what it cost, what is wasting money and what to change, then proposes each change before making it. |
adcopilot-launch | ask to build a campaign or start advertising, or ask how a new campaign is doing | Builds a first Search campaign switched off, checks the settings that leak money, and hands you the switch to turn it on. |
adcopilot-measure | ask to set up conversion tracking, or ask why Google Ads shows no conversions | Sets up conversion tracking end to end, finishing with one Primary conversion, proven by a real click. |
adcopilot-daily | set up a morning check, or when a scheduled morning check runs | The read-only morning check a Claude scheduled task runs with nobody there to answer, and the steps to set that schedule up. |
adcopilot-fix-checks | send the question from a Fix … in Claude button on an AdCopilot audit page or email, such as Fix all three in Claude or Fix this in Claude, or ask to fix or go through the checks an audit found | Fixes the checks an audit flagged one at a time: it says first what the fixes cost in today's operations, proposes each fix as one yes or no question, and reads each change back with how to undo it. |
adcopilot-seo | ask about Search Console, indexing, sitemaps, rankings or organic traffic | Answers what Google search makes of your site through Search Console, and says plainly what Search Console cannot show. |
adcopilot-docs | ask what AdCopilot can do, about plans, limits, privacy or safety, or when a call fails | Answers questions about AdCopilot itself from your live workspace rather than from memory. |
adcopilot-meta | ask about Meta, Facebook or Instagram ads, or about Meta and Google together | AdCopilot has no Meta integration. The skill looks for Meta's own connector in the conversation, says how to add it when it is not there, and keeps each platform's figures labelled with where they came from. |
Commands
| Command | What it does |
|---|---|
/setup | Checks the AdCopilot connector is connected and signed in, and says what each connected Google product unlocks. |
/measure | Conversion tracking end to end, through adcopilot-measure. |
/launch | A first Search campaign, built switched off, through adcopilot-launch. |
/daily | The daily check-in: this month's pacing, the last seven days' searches that cost money and brought nothing, any ad Google has stopped, and what changed since yesterday, as far as your plan's daily operations allow. |
/weekly | Last Monday to Sunday against the week before: spend, conversions and cost per conversion, the three biggest changes, and three things to do this week. |
/negatives | The last seven days' searches that cost money and brought nothing, grouped by theme, with the negative keywords that would block them, each proposed before it is added. |
/audit | The full audit and this month's budget pacing, with findings that only mean the account is new kept apart from the real ones. |
The plugin's Commands tab lists them with Claude's own descriptions. The screenshot below is of an earlier version, with fewer commands.

In Claude Code the same commands are /adcopilot:setup, /adcopilot:audit
and so on. See The Claude Code plugin.
The / menu
Type / in a chat. Claude's menu has a section named AdCopilot — Google
Ads, Analytics, Search Console & Tag Manager with the plugin's skills and
commands. Keep typing to narrow it.

An example: /audit
Type /aud, choose audit, and send it.

Claude reads the command's instructions, then runs AdCopilot's full audit and this month's budget pacing.

It answers with a score, the budget pacing and the real findings, kept apart from the failures that only mean the account is new. These screenshots are from AdCopilot's own account, with the spend figures blurred.

It ends with the one thing to fix first.
The audit only reads. To apply a fix, ask for it: Claude asks before the change runs while Write/delete tools stay on Needs approval.
Fallback: add AdCopilot as a custom connector
Use this only when you can't add the plugin: for example, your organisation doesn't allow plugins. It reaches the same connector, without the plugin's skills and commands. If you added AdCopilot this way before, it keeps working.
Open Add custom connector
This link opens Claude's Add custom connector box straight away:
Open Add custom connector in Claude
To get there yourself: in Claude's sidebar choose Customize, then Connectors, press + Add at the top right, and choose Add custom connector. In a Team or Enterprise organisation, an owner may need to add custom connectors for you.


Fill in the form
| Field | Value |
|---|---|
| Name | AdCopilot |
| MCP server URL | the URL below |
https://mcp.adcopilot.cloud/mcpPress Continue. If Chrome's autofill list covers the URL box, press Esc to close it.

Leave the sign-in settings as they are
Sign in now and Use Claude's published identity are already selected and marked Detected. Don't change them. Scroll down and press Add.

Connect, then finish as above
Claude opens the connector's page: You're not connected to AdCopilot yet. Press Connect.

Then carry on from step 4: press Approve on AdCopilot's page, set Read-only tools to Always allow under Tool permissions, and say "Get me started with AdCopilot". The connector is named AdCopilot here, as you typed it.
If something goes wrong
See Connecting Claude for: a plugin that is added but not connected, no AdCopilot page to approve, Claude asking permission before every report, no Customize in the sidebar, an organisation that restricts plugins or custom connectors, and Chrome's autofill covering the URL box.
Picking up new tools
Claude keeps the tool list it was given when you approved it. After an AdCopilot release adds tools, open Customize → Connectors, choose adcopilot (or AdCopilot, if you added it by hand), press Disconnect, then Connect again. AdCopilot tells you in the chat when this is needed. Connecting another Google product needs nothing here, unless Connect your AI marks Claude Re-authorization needed. See Reconnecting.
Disconnecting
Press Disconnect on AdCopilot's connector under Customize → Connectors, or Revoke Claude under Connected assistants in the AdCopilot dashboard. To remove the plugin's skills and commands too, switch the plugin off on its page under Customize → Plugins.
Connect ChatGPT
Add AdCopilot from ChatGPT's plugin directory. Install the plugin, connect it, approve it on AdCopilot's page, then ask in a new chat.
Connect Claude Code and Codex
In Claude Code, install the AdCopilot plugin or add the connector with one command. Codex takes one command. Approve in your browser, then ask.