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.
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. Cursor has a page of its own, with a link that adds it: Connect Cursor. Found AdCopilot in a directory instead? See Add AdCopilot to your agent.
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. VS Code uses its own shape; see Connecting Cursor and other clients, which also covers Cursor and Microsoft Copilot Studio.
{
"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.
In Cursor, if Approve did nothing on an earlier try, remove AdCopilot, add it again and press Approve once. See Approve does nothing and Connect Cursor.
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 Connected assistants in the dashboard, and it re-approves with the full set next time. Connecting another Google product needs nothing in the client, unless Connect your AI marks it Re-authorization needed. See A tool is missing or out of date.