AdCopilot docsby Atromx
Connect your assistant

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.

View as Markdown
Open inClaudePerplexity

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.

Claude's Customize page on the Plugins tab, searched for AdCopilot. The first result is AdCopilot — Google Ads, Analytics, Search Console & Tag Manager, from Anthropic Directory, with an Add button.

2. Add the plugin

On the plugin's page, press Add.

The AdCopilot plugin's page in Claude (version 0.2.2 shown): from Anthropic Directory, with the tabs Overview, Contents, Skills, Commands and Connectors, and an Add button.

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's prompt before adding the plugin: it may include components that run code, a red warning that installing will grant access to everything available to Cowork, and only enable plugins from people you trust, with Cancel and Continue.

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.

The plugin's Connectors tab: adcopilot, Not added, with a Connect button.

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.

Claude's Add custom connector box, filled in by the plugin with adcopilot and https://mcp.adcopilot.cloud/mcp, with Cancel and 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.

Claude's sign-in settings for adcopilot: Sign in now and Use Claude's published identity selected and marked Detected, with Back and Add at the bottom.

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.

AdCopilot's page asking Let Claude use your AdCopilot?, listing what Claude will be able to do, with Approve and Cancel.

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

The plugin's Connectors tab after approving: adcopilot, Connected · Custom.

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.

adcopilot's Tool permissions in Claude, with the menu beside Read-only tools open: Always allow, Needs approval, Blocked and Custom.

Read-only tools set to Always allow, with each read-only tool on the allow setting.

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

A new Claude chat with Get me started with AdCopilot typed in the message box.

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.

Claude's working steps for that message: it reads the AdCopilot connect skill for the get-started flow (SKILL.md), finds get_org_context, and calls it. In this picture the call's step reads “AdCopilot: what is connected and where you are”, the title it had before it became “AdCopilot: workspace context (records visit)”.

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

SkillClaude uses it when youWhat it does
adcopilot-connectsay "Get me started with AdCopilot", ask what is connected, or ask to connect or link Google Ads, Analytics, Tag Manager or Search ConsoleSays where you stand, then connects your Google products and links them to each other in the order that works.
adcopilot-reviewask how your ads are doing, what they cost, what is wasting money, or what to pause, fix or do nextReads 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-launchask to build a campaign or start advertising, or ask how a new campaign is doingBuilds a first Search campaign switched off, checks the settings that leak money, and hands you the switch to turn it on.
adcopilot-measureask to set up conversion tracking, or ask why Google Ads shows no conversionsSets up conversion tracking end to end, finishing with one Primary conversion, proven by a real click.
adcopilot-dailyset up a morning check, or when a scheduled morning check runsThe read-only morning check a Claude scheduled task runs with nobody there to answer, and the steps to set that schedule up.
adcopilot-fix-checkssend 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 foundFixes 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-seoask about Search Console, indexing, sitemaps, rankings or organic trafficAnswers what Google search makes of your site through Search Console, and says plainly what Search Console cannot show.
adcopilot-docsask what AdCopilot can do, about plans, limits, privacy or safety, or when a call failsAnswers questions about AdCopilot itself from your live workspace rather than from memory.
adcopilot-metaask about Meta, Facebook or Instagram ads, or about Meta and Google togetherAdCopilot 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

CommandWhat it does
/setupChecks the AdCopilot connector is connected and signed in, and says what each connected Google product unlocks.
/measureConversion tracking end to end, through adcopilot-measure.
/launchA first Search campaign, built switched off, through adcopilot-launch.
/dailyThe 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.
/weeklyLast Monday to Sunday against the week before: spend, conversions and cost per conversion, the three biggest changes, and three things to do this week.
/negativesThe 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.
/auditThe 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.

The plugin's Commands tab: /setup, /measure, /launch, /daily and /audit, each with its description.

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.

Claude's / menu with its AdCopilot — Google Ads, Analytics, Search Console & Tag Manager section, listing adcopilot-connect, adcopilot-launch, adcopilot-measure and setup.

An example: /audit

Type /aud, choose audit, and send it.

Claude's message box with /aud typed. The menu offers audit, described as: Audit the account — the connector's full check list, then this month's budget pacing — and keep what is only newness out of the findings.

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

Claude working on /audit: Read the audit skill instructions before running the audit.

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.

The start of Claude's answer: an audit score of 69/100 (C), with the failures that come from the account being only 12 days old split out; Budget pacing is fine, its figures blurred; then the heading Real findings.

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.

Claude's Connectors page with the + Add menu open, offering Add custom connector.

The Add custom connector box, with empty Name and MCP server URL fields.

Fill in the form

FieldValue
NameAdCopilot
MCP server URLthe URL below
https://mcp.adcopilot.cloud/mcp

Press Continue. If Chrome's autofill list covers the URL box, press Esc to close it.

The form filled in: Name AdCopilot, MCP server URL https://mcp.adcopilot.cloud/mcp, and Continue ready to press.

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.

Claude's sign-in settings for AdCopilot: Sign in now and Use Claude's published identity selected and marked Detected, with Back and Add at the bottom.

Connect, then finish as above

Claude opens the connector's page: You're not connected to AdCopilot yet. Press Connect.

AdCopilot's connector page in Claude, with the Connect button.

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.

On this page