This article covers Microsoft 365 Copilot for work accounts. The consumer Copilot app for personal Microsoft accounts doesn't support MCP connections.
The TrueClicks MCP lets you query your TrueClicks data and your linked Google, Microsoft, and Meta Ads accounts from your AI or automation tool. It has built-in Google Ads, Microsoft Ads, and Meta Ads MCPs, so a single connection covers all of them plus your TrueClicks data. For what it is and what data it reaches, see Using the TrueClicks MCP.
The MCP URL is:
https://data.trueclicks.com/mcp/
Everything is read-only: reporting and analysis only, no changes to your accounts or ad platforms.
Microsoft 365 Copilot doesn't let you add a custom connector directly. Instead, you add the TrueClicks MCP as a tool in a Copilot Studio agent, then publish that agent to Microsoft 365 Copilot and Teams. The agent connects via OAuth, so each person logs in with their own TrueClicks account and can access only the accounts their TrueClicks access allows.
Before you start
You need access to Copilot Studio (copilotstudio.microsoft.com) with permission to create and publish agents. Depending on how your Microsoft 365 tenant is set up, an admin may need to approve the agent before others can use it, and your Power Platform data policies need to allow MCP connectors.
Using Copilot Studio agents requires a Microsoft license or Copilot Credits. Both are purchased from Microsoft and billed to your organization. They're separate from your TrueClicks subscription, and you don't pay TrueClicks anything extra to use the MCP with Copilot.
What you need from Microsoft depends on the route you pick below:
Standard agent: a Microsoft 365 Copilot license for each user, or Copilot Credits. The license costs around €27 per user per month and covers standard agents at no extra cost. Your IT admin can order it in the Microsoft 365 admin center (admin.cloud.microsoft).
Agent (GitHub Copilot): a Microsoft 365 Copilot license, plus Copilot Credits for usage. Building, testing, and using the agent all consume credits, billed by Microsoft.
Microsoft regularly updates its pricing and licensing, so check the current terms with your IT admin before you build.
Pick your route
The Copilot Studio homepage gives you two ways to build the agent, and you can't switch an agent between them later:
Other ways to build (standard agent). More predictable, rule-based behavior. If you have a Microsoft 365 Copilot license, using the agent incurs no extra cost. Without one, usage is billed in Microsoft Copilot Credits.
Agent (GitHub Copilot). More capabilities, like skills and memory, and better at reasoning through longer, multi-step questions across several tools. Building, testing, and using the agent consume Copilot Credits, billed by Microsoft.
Despite the name, the GitHub Copilot option has nothing to do with GitHub. It's the name of Copilot Studio's newer agent engine, and your data isn't sent to GitHub Copilot.
Route A: Other ways to build (standard agent)
Route A: Other ways to build (standard agent)
Step 1: Add the TrueClicks MCP
On the Copilot Studio homepage, select Other ways to build, choose the standard agent option, and create a new agent (for example, "TrueClicks").
Go to Tools, select Add a tool, then New tool.
Select Model Context Protocol.
Enter a server name (call it "TrueClicks"), a short description, and the URL:
https://data.trueclicks.com/mcp/
For the description, use something like: "Reads TrueClicks audit results, alerts, pacing, and Google, Microsoft, and Meta Ads performance data." Copilot uses this description to determine when to call the MCP, so keep it specific.
Under Authentication, choose OAuth 2.0 and set the type to Dynamic discovery. Select Create, then Next.
In Add tool, select Create a new connection. Copilot Studio sends you to TrueClicks to log in and approve access.
Select Add to agent.
To check if it works, ask the agent in the test pane something like "List my TrueClicks accounts."
Step 2: Publish to Microsoft 365 Copilot
Select Publish at the top of the agent.
Go to Channels and select Teams and Microsoft 365 Copilot.
Make sure Make agent available in Microsoft 365 Copilot is selected, then select Add channel.
Under Availability options, share the agent with specific people or groups, or submit it for admin approval to make it available to your whole organization.
Route B: Agent (GitHub Copilot)
Route B: Agent (GitHub Copilot)
Step 1: Add the TrueClicks MCP
On the Copilot Studio homepage, select Agent and create a new agent (for example, "TrueClicks"). Give it a name, description, and instructions, since you can't publish without them.
Open the Build tab.
In the components panel on the right, select Tools.
In the Add a tool dialog, select Add next to the search bar, then Model Context Protocol (MCP).
Enter a server name (call it "TrueClicks"), a short description, and the URL:
https://data.trueclicks.com/mcp/
For the description, use something like: "Reads TrueClicks audit results, alerts, pacing, and Google, Microsoft, and Meta Ads performance data." Copilot uses this description to determine when to call the MCP, so keep it specific.
Under Authentication, choose OAuth 2.0.
Select Add. Copilot Studio sends you to TrueClicks to log in and approve access, then lists the TrueClicks MCP tools.
Review the tool list and select Save.
To check if it works, open the Preview tab and ask something like "List my TrueClicks accounts." The activity trace shows which TrueClicks tool the agent called.
Step 2: Publish the agent to Microsoft 365 Copilot
Select the chevron next to Publish.
In the Publish agent dialog, select the Teams and Microsoft 365 Copilot channel and make sure Make agent available in Microsoft 365 Copilot is on.
Select Publish and wait for it to finish.
To give others access, select the Share icon next to Publish. Add specific people or security groups, or under Organization select End user access to make it available to everyone in your organization.
Using the agent
Open the agent in the Microsoft 365 Copilot app or Teams, or @mention it in a chat. The first time you use it, you're asked to log in to TrueClicks with your own account. Because OAuth authenticates each person separately, each person sees only the accounts their own TrueClicks access allows, even though one person set up the agent.
Note: The agent only works in Microsoft 365 Copilot, signed in with your work account. Windows 11 also comes with a Copilot app, and both are called "Copilot," but the built-in one is the consumer version and can't use Copilot Studio agents.
Here's how to tell them apart:
Microsoft 365 Copilot (the one you need): the taskbar icon has a small "M365" label. The bottom left shows a Work badge with your name and your Microsoft 365 Copilot plan, and the left pane has an Agents section.
Consumer Copilot (built into Windows 11): the taskbar icon has no label. It's signed in with a personal Microsoft account, shows an Upgrade button, and has options like Discover and Imagine instead of Agents.
You can open the agent in three places:
The Microsoft 365 Copilot app on your computer
The browser, at https://m365.cloud.microsoft
Teams, by opening Copilot or @mentioning the agent in a chat
In Microsoft 365 Copilot, find the agent under Agents in the left pane. If it's not listed, select More agents and search for it.
Good to know
Not sure which route an existing agent uses? Your Power Platform admin can check in the Power Platform admin center under Manage > Copilot Studio, in the Harness column. "Standard" is Route B, "GitHub Copilot" is Route A.
Changes to the agent only reach users after you publish again. If an admin approved the agent and you change its name, icon, or description, it needs approval again.
Keep the number of MCP servers on one agent small. Each one counts toward the agent's tool limit.
Copilot Studio only supports streamable HTTP for MCP, which is what the TrueClicks MCP uses.