Any MCP client
Cursor, Windsurf, Microsoft Copilot or any client that speaks the Model Context Protocol — add the connector URL, approve it, and ask.
AdCopilot is a remote MCP server over streamable HTTP, with OAuth sign-in. Any client that can add a remote server by URL can use it.
https://mcp.adcopilot.cloud/mcpClients that read a JSON configuration file
Most accept this shape. Where the file lives is up to your client; check its documentation for the path.
{
"mcpServers": {
"adcopilot": {
"url": "https://mcp.adcopilot.cloud/mcp"
}
}
}Clients with a connector settings screen
Add a custom connector (or "remote MCP server") and paste the URL. Microsoft Copilot works this way.
Sign in
The first time the client connects, it opens AdCopilot's page asking you to let it use your AdCopilot. Press Approve. There is no API key to paste.
Then ask
Get me started with AdCopilot
Picking up new tools
Clients cache the tool list from when they connected. After an AdCopilot release adds tools, reconnect AdCopilot in the client's connector settings, or remove it and add it again. Or Revoke the app under Connections in the dashboard, and it re-approves with the full set next time. Connecting another Google product needs nothing in the client, unless Connections marks it Re-authorization needed. See A tool is missing or out of date.
Connect Gemini CLI
Add AdCopilot to Gemini CLI with one command over HTTP, sign in, and ask from the terminal.
Approval-gated writes
AdCopilot reads freely and changes things only when you ask. Approval is your AI client's own tool-permission prompt, and a set of limits holds on AdCopilot's server whatever the client allows.