AdCopilot docsby Atromx
Connect your assistant

The Claude Code plugin

The AdCopilot plugin for Claude Code registers the connector and adds skills, commands and an agent. What it holds, how to install it, what to type first.

View as Markdown
Open inClaudePerplexity

The AdCopilot plugin for Claude Code is public and MIT-licensed: AtromxIntelligence/adcopilot-claude-plugin. This page describes version 0.2.16; the repository's README says what each version changed. It does two things:

  • It registers the connector for you. There is no claude mcp add step. The plugin points Claude Code at https://mcp.adcopilot.cloud/mcp, the same connector every other assistant uses.
  • It adds skills, commands and an agent for the steps the connector cannot take for you: what to click in Google's own screens, and the traps that are easy to fall into.

The same plugin is in Claude's plugin directory for Claude on the web and the desktop app, where you add it from Customize → Plugins and its commands are /setup, /audit and so on. See Connect Claude. In Codex, Gemini CLI or any other client, add the connector by URL. See Connect your assistant.

Install

In Claude Code:

/plugin marketplace add AtromxIntelligence/adcopilot-claude-plugin
/plugin install adcopilot@adcopilot-claude-plugin

Then run /mcp, choose adcopilot and sign in.

Then type

Open Claude Code and type: Get me started with AdCopilot

It reads what your workspace has connected and says the next step. Claude Code also lists the same start in its / menu: as /plugin:adcopilot:adcopilot:get-started (MCP) with the plugin, and as /adcopilot:get-started (MCP) when you added the connector by hand.

You need an AdCopilot account. Google Ads and your other Google products are connected in your browser, on Google's own consent screen, never in the terminal: when one is not connected yet, Claude Code gives you AdCopilot's link to it, or you press Connect Google Ads in the dashboard at app.adcopilot.cloud. Claude Code never sees your Google sign-in. See Connect Google Ads.

Sign-in is unchanged

The plugin changes nothing about how you sign in. The first time Claude Code connects, your browser opens AdCopilot's page asking you to let Claude Code use your AdCopilot. You sign in with your own Google account and press Approve, exactly as you would after claude mcp add. The plugin itself holds no key or token, and you can withdraw the access under Connected assistants on the dashboard's Connect your AI at any time.

What is in it

What Claude Code loads from the plugin is markdown and one connector registration: skills, commands and an agent, all written in markdown. It has no hooks and starts no local server, so nothing from it runs on your machine. The repository also holds the eval suite used to test the skills; Claude Code does not run it.

Skills

Claude uses a skill on its own when the conversation calls for it.

SkillClaude uses it when youWhat it does
adcopilot-connectinstall AdCopilot, ask to get started, ask what is connected, ask to connect or link Google Ads, Analytics, Tag Manager or Search Console, or ask why a tool or product is missingConnects your Google products and links them to each other in the order that works, saying what each step bought you.
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, launch ads or start advertising, or ask how a new campaign is doing in its first weeks or why it is not showingBuilds a first Search campaign switched off, checks the settings that leak money by reading the campaign back, hands you the switch to turn it on, and runs the first week's checks.
adcopilot-measureask to set up conversion tracking or count sign-ups, ask about Analytics or Tag Manager for tracking, or ask why Google Ads shows no conversionsSets up conversion tracking end to end: the Analytics property and data stream, the Tag Manager tag, the key event, the link to Google Ads and the import. It finishes with exactly 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 Code routine or 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

You type these.

CommandWhat it does
/adcopilot:setupChecks the connector is connected and signed in, says what each connected product unlocks, and catches a copy of the connector you added by hand.
/adcopilot:launchA first Search campaign, through adcopilot-launch.
/adcopilot:measureConversion tracking, through adcopilot-measure.
/adcopilot: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.
/adcopilot: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.
/adcopilot: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.
/adcopilot: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 agent

Claude hands a job to it when it is too big for the conversation.

AgentWhat it does
adcopilot-auditorA full account audit end to end, returned as a written report with the numbers behind each finding and the changes worth making. It holds read tools only, so it cannot apply a change; the conversation that asked for it takes your yes.

The plugin works through the same connector, so the same rules hold: every change is proposed first, new campaigns are built paused, and it can never delete. The yes before a change is Claude Code's own permission prompt. An allowlist entry or auto mode skips it, so leave AdCopilot's write tools off your allowlist. See Approval-gated writes.

Already added the connector by hand?

If you ran claude mcp add before installing the plugin, Claude Code keeps your copy and silently ignores the plugin's. claude mcp list shows the sign: a bare adcopilot: line and no plugin:adcopilot:adcopilot line.

Remove your copy from every scope it is in. One claude mcp remove is not always enough, because the same name can be registered in more than one scope at once:

claude mcp remove adcopilot -s user

Then, from the directory you added it in:

claude mcp remove adcopilot -s local

A local registration belongs to the directory you ran claude mcp add in, and is invisible from anywhere else. If you added it in more than one project, repeat this in each. If a project's .mcp.json lists it, that one is -s project, run from that project.

Run claude mcp list again until only plugin:adcopilot:adcopilot remains, then /mcp to sign in. /adcopilot:setup checks for this too.

Rather not install a plugin?

Add the connector by hand instead. Use one or the other, not both:

claude mcp add --scope user --transport http adcopilot https://mcp.adcopilot.cloud/mcp

See Connect Claude Code and Codex.

Scripts and allowed tools

Claude Code names a plugin's tools after the plugin. With the plugin, AdCopilot's tools are mcp__plugin_adcopilot_adcopilot__<tool>; added by hand as adcopilot, they are mcp__adcopilot__<tool>. Use the right prefix in --allowedTools for a claude -p script, and take the exact names from /mcp.

Updating and removing

New AdCopilot tools. Run /mcp, choose adcopilot and reconnect. See A tool is missing or out of date.

A new plugin version. Refresh the marketplace, update the plugin, then restart Claude Code:

claude plugin marketplace update adcopilot-claude-plugin
claude plugin update adcopilot@adcopilot-claude-plugin

Remove it:

claude plugin uninstall adcopilot@adcopilot-claude-plugin

How the skills are tested

The plugin's repository carries its eval suite. Its README sets the rule a skill must meet to stay: on the same cases, it has to beat a copy of the plugin whose skills are cut to their descriptions, which leaves the connector to do the work alone.

Support

On this page