Add AdCopilot to your agent
Three MCP directories that list AdCopilot (the Official MCP Registry, Glama and MCP Market), and how to add it to your AI assistant from one of them.
Several public directories list AdCopilot. A directory is a catalogue: it shows what AdCopilot is and where it lives, and your AI assistant does the adding. This page covers three MCP directories, the Official MCP Registry, Glama and MCP Market. Each of the three shows the same connector address:
https://mcp.adcopilot.cloud/mcpWe opened each of these three listings and checked it on 10 November 2026.
AdCopilot is also on cursor.directory and in Claude's plugin directory. Those have steps of their own: see Installed from cursor.directory and Connect Claude.
Add it from a listing
Connect your Google products in the dashboard first (see Connect Google Ads). Then:
- Open one of the listings below and find the connector address. It is the one above.
- Add AdCopilot to your AI assistant. In Claude, add the AdCopilot plugin rather than the address: the plugin brings the connector with it. See Connect Claude for Claude on the web and desktop, and Claude Code and Codex for Claude Code. In any other assistant, add the address as a remote MCP server. The steps for Codex, Cursor and any other MCP client are on their own pages.
- Your assistant opens AdCopilot's page asking you to let it use your AdCopilot. Sign in with Google if it asks, then press Approve.
- Start a new chat and say:
Get me started with AdCopilot
The three listings
| Directory | Listing | What the listing shows |
|---|---|---|
| Official MCP Registry | cloud.adcopilot/adcopilot | A remote server over streamable HTTP, at the connector address |
| Glama | AdCopilot | An MCP connector at the connector address, signed in with OAuth |
| MCP Market | AdCopilot | A remote MCP server at the connector address |
Official MCP Registry
The Official MCP Registry
lists AdCopilot as cloud.adcopilot/adcopilot. The link opens the registry's
entry as data, not as a web page: its remotes field holds the connector
address.
A client that can add a server from the registry can add it by that name. For any other client, copy the address and follow the steps above.
Glama
AdCopilot on Glama shows the connector address, that it is reached over streamable HTTP, and that it signs in with OAuth. Copy the address from the listing and follow the steps above.
If Glama's search shows a second AdCopilot, it is a duplicate that Glama marks as deprecated. Use the one linked here.
MCP Market
AdCopilot on MCP Market shows the connector address. Copy it and follow the steps above.
MCP Market also has a second AdCopilot entry, which links our public GitHub repository. It does not show the connector address, so use the one above.
When a listing and these docs differ
A directory is run by someone else, and its copy can be older than this page. If a listing says something different about AdCopilot, go by these docs. The address above is the one to add.
Without these directories
You don't need any of the directories on this page to add AdCopilot. Connect your assistant has the steps for each assistant.
Any MCP client
Windsurf, Microsoft Copilot or any client that speaks the Model Context Protocol — add the connector URL, approve it, and ask. Cursor has its own page.
Approval-gated writes
AdCopilot reads freely and proposes each change first. Approval is your AI client's own permission prompt, backed by limits on AdCopilot's server.