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.
The AdCopilot plugin for Claude Code is public and MIT-licensed: AtromxIntelligence/adcopilot-claude-plugin, version 0.1.0. It does two things:
- It registers the connector for you. There is no
claude mcp addstep. The plugin points Claude Code athttps://mcp.adcopilot.cloud/mcp, the same connector every other assistant uses. - It adds three skills and five commands 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.
This is a Claude Code plugin. 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-pluginThen run /mcp, choose adcopilot and sign in.
You need an AdCopilot account, and your Google products are connected in the dashboard at app.adcopilot.cloud, not in Claude Code. 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 from Connections in
the dashboard at any time.
What is in it
What Claude Code loads from the plugin is markdown and one connector registration. 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.
Three skills
Claude uses a skill on its own when the conversation calls for it.
| Skill | Claude uses it when you | What it does |
|---|---|---|
adcopilot-connect | install 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 missing | Connects your Google products and links them to each other in the order that works, saying what each step bought you. |
adcopilot-launch | ask 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 showing | Builds 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-measure | ask to set up conversion tracking or count sign-ups, ask about Analytics or Tag Manager for tracking, or ask why Google Ads shows no conversions | Sets 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. |
Five commands
You type these.
| Command | What it does |
|---|---|
/adcopilot:setup | Checks 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:launch | A first Search campaign, through adcopilot-launch. |
/adcopilot:measure | Conversion tracking, through adcopilot-measure. |
/adcopilot:daily | The daily check-in: what was spent since yesterday, the searches the ads showed for, and what changed in the account, as far as your plan's daily operations allow. |
/adcopilot: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 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 userThen, from the directory you added it in:
claude mcp remove adcopilot -s localA 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/mcpSee 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-pluginRemove it:
claude plugin uninstall adcopilot@adcopilot-claude-pluginHow 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
- A command, a skill or the plugin's README is wrong: open an issue on the plugin repository.
- Sign-in, a tool call or your account: [email protected].
Connect Claude Code and Codex
In Claude Code, install the AdCopilot plugin or add the connector with one command. In Codex, one command. Then approve it in your browser and ask from the terminal.
Connect Gemini CLI
Add AdCopilot to Gemini CLI with one command over HTTP, sign in, and ask from the terminal.