Connect Google Ads, Meta and LinkedIn Ads to Microsoft Copilot Studio
Add PaidSync to a Copilot Studio agent as a Model Context Protocol tool at https://mcp.paidsync.ai/mcp with OAuth 2.0 and Dynamic discovery. The agent can then read spend, budgets and results across Google Ads, Meta Ads and LinkedIn Ads, and propose changes such as pausing a campaign or moving budget. Every change is held for your approval before it runs. Nothing moves on its own.
Work or school account. 460+ tools across 14 platforms. Free plan, no credit card.
Short answer
Copilot Studio accepts any Model Context Protocol server over Streamable HTTP. PaidSync is one server that sits in front of Google Ads, Meta Ads, LinkedIn Ads and eleven more platforms. You connect each ad account to PaidSync once, with the platform's own OAuth sign-in. Then you add PaidSync to your agent in Copilot Studio with a single URL and an OAuth 2.0 sign-in. That takes about ten minutes.
From there the agent works in plain language. Ask for last week's spend by platform. Ask which Google Ads campaigns missed their target CPA. Ask it to move budget from the weakest LinkedIn campaign to the strongest. Reads come back straight away. Writes are held as an approval, with a preview of the exact change, and run only after a person says yes. Google Ads is a 149-tool platform in PaidSync, Meta Ads is 81 tools and LinkedIn Ads is 25.
Copilot Studio, Microsoft 365 Copilot or Copilot chat
Microsoft sells several things called Copilot. Only one of them lets you add a custom MCP server, so it helps to know which one you are looking at.
| Product | Who uses it | PaidSync |
|---|---|---|
| Copilot Studio | The person who builds agents. Needs a work or school account. Included with Microsoft 365 Copilot licences, or standalone, or a 30-day trial. | Yes. Add PaidSync as a Model Context Protocol tool. This is the page for it. |
| Microsoft 365 Copilot | Everyone in Teams, Word and Outlook. | Through a published Copilot Studio agent. Build it, publish to the Microsoft 365 Copilot channel, admin approves. |
| Copilot chat (consumer app and copilot.com) | Personal Microsoft accounts. | No. The consumer Copilot app does not accept custom MCP servers. |
| GitHub Copilot in VS Code | Developers. | A different product with its own MCP setup. It is covered in the full Copilot guide, not here. |
Add PaidSync in five steps
Create a PaidSync account
Go to paidsync.ai/signup. Google or email sign-in. The free plan is 15 tasks per month at $0, with no credit card. That is enough to test the whole agent before anyone pays.
Connect Google Ads with OAuth
In the PaidSync dashboard click Connect Google Ads. Sign in with the Google account that owns your ads and pick the accounts the agent may see. PaidSync stores the token encrypted at rest with AES-256-GCM. Your password never touches PaidSync.
Connect Meta Ads and LinkedIn Ads with OAuth
Click Connect Meta Ads. Sign in with the Facebook account that manages your ad accounts, then choose the ad account the agent should work in. Click Connect LinkedIn Ads. Sign in with the LinkedIn account that has Campaign Manager access. Each platform gets its own sign-in, so one agent can cover all three without sharing credentials between them.
Add PaidSync to a Copilot Studio agent
In Copilot Studio open your agent, then Tools, Add a tool, New tool, Model Context Protocol. Server name PaidSync, a short description, and the server URL:
https://mcp.paidsync.ai/mcpAuthentication: OAuth 2.0, then Dynamic discovery. PaidSync publishes the OAuth discovery metadata and supports dynamic client registration, so no client ID is typed. If your tenant blocks that, choose API key as a Query parameter named api_key with your ps_ key. Transport is Streamable HTTP; SSE is not supported by Copilot Studio.
Click Create, then Add to agent. Test in the studio, then publish to the Microsoft 365 Copilot channel. Tenant DLP policies on Power Platform connectors govern the connection, and most tenants need an admin to approve the published agent.
Copilot Studio needs a work or school account. It is included with Microsoft 365 Copilot licences and available as a standalone subscription or 30-day trial. The consumer Copilot app does not accept custom MCP servers.
Test the agent, then publish
In the Copilot Studio test pane ask: "List my Google Ads accounts". The agent should answer with account names and IDs. Then ask: "Show last 7 days spend across Google Ads, Meta Ads and LinkedIn Ads". One answer, three platforms.
When the answers are right, publish the agent to the Microsoft 365 Copilot channel. In most tenants an admin approves it before it shows up in Teams and Microsoft 365 Copilot.
OAuth 2.0 dynamic discovery, and the API key fallback
When you pick OAuth 2.0 and Dynamic discovery, Copilot Studio reads PaidSync's published OAuth metadata, registers itself as a client through dynamic client registration, and runs the sign-in with PKCE. You do not type a client ID or a client secret. The person who builds the agent signs in with their PaidSync login, and that login is what allows the agent to apply changes.
| Wizard field | Value |
|---|---|
| Server name | PaidSync |
| Server URL | https://mcp.paidsync.ai/mcp |
| Authentication | OAuth 2.0, Dynamic discovery |
| Transport | Streamable HTTP |
Some tenants block dynamic client registration. If the OAuth step fails for that reason, choose API key in the wizard, set it as a Query parameter named api_key, and paste the ps_ key from your PaidSync dashboard. Copilot Studio then calls this URL:
https://mcp.paidsync.ai/mcp?api_key=ps_your_key_hereThe key path is read-only. Reports and audits work. Applying a change still requires the OAuth 2.0 sign-in, and a key in a URL lands in logs and browser history, so OAuth is the path to ask your admin for.
Power Platform DLP, what your admin will ask
Copilot Studio runs on Power Platform, and Power Platform data loss prevention (DLP) policies decide which connections an agent may use. Tenant DLP policies govern the PaidSync connection like any other. If the tool will not save, or the connection shows as blocked after you click Create, the environment's DLP policy is the first thing to check.
Your Power Platform admin will want three facts. The server is a single host, mcp.paidsync.ai. Authentication is OAuth 2.0 with dynamic client registration and PKCE, so no shared secret leaves the tenant. Ad platform tokens are stored encrypted at rest with AES-256-GCM, and no change reaches an ad account without a person approving it. Single sign-on and a data processing agreement are available on request for larger teams.
Two agents you can build this week
Both examples use PaidSync tools your agent already has after step 4. The prompts go in the agent's instructions. The approval step is the same in each case, and it is the part that lets a finance or marketing lead trust the agent on day one.
Weekly pacing agent
Every Monday the agent asks PaidSync for month-to-date spend and the monthly budget for each account across Google Ads, Meta Ads and LinkedIn Ads. It compares the two, works out the daily rate needed to land on budget, and posts a short summary in Teams. Accounts more than ten percent ahead or behind get a proposed budget change. Each proposal lands as an approval card. The media manager taps approve, the change runs, and the card keeps a one-tap undo and a 7-day outcome check so the team can see whether the change did what it was meant to. A dry_run preview shows the exact new budget before the tap.
Disapproval agent
Each morning the agent asks PaidSync for disapproved and suspended products in Google Merchant Center, the same check the Merchant Center Auditor runs in the PaidSync workspace. It groups the products by reason, drafts the feed fix, and hands the list to the person who owns the feed. The product update is a write, so it waits as an approval before anything changes in Merchant Center. If a Google Ads Shopping campaign is losing volume because of those products, the agent says so in the same message, with the spend figure, and can propose a pause that also waits for approval. Removing a product or a campaign is destructive and needs confirm_destructive on top.
What the agent can do in Google Ads, Meta and LinkedIn
All three are build-tier platforms in PaidSync, which means the agent can create campaigns, not just report on them. The counts below come from the PaidSync capability matrix.
- Google Ads, 149 tools. Search, Shopping and Performance Max reporting, search terms, negative keywords, budgets, bidding, campaign creation, pause and enable.
- Meta Ads, 81 tools. Campaign, ad set and ad performance, image and video upload, campaign creation and updates, pause and enable across Facebook and Instagram placements.
- LinkedIn Ads, 25 tools. Campaign group and campaign performance, campaign and creative creation, updates, pause.
- One prompt, three platforms. Cross-platform questions run in one turn. "Compare cost per lead across Google Ads, Meta Ads and LinkedIn Ads for August" is a single request.
- Saved workflows. A TypeScript composition saved with paidsync_workflows_save can be run by the agent with paidsync_workflows_run. Five official workflows ship today, including account-audit, find-waste and weekend-underspend.
Microsoft Advertising has its own MCP server in a read-only open pilot since June 17 2026 (about.ads.microsoft.com). It covers Microsoft Advertising accounts only and cannot change anything. PaidSync adds Microsoft Ads alongside the other thirteen platforms, with writes held for approval.
Custom agentic workflows for your ad operations
The two agents above are a starting point. Teams that run real budgets usually need more. A pacing agent that knows your fiscal calendar. A disapproval agent that files tickets in your system. An approval chain where the media manager proposes and the finance lead signs. PaidSync builds these agents with you, on Copilot Studio or on your own agent stack, with the same approval gating on every write.
The founder is a Google Premier Partner who has managed over $500M in ad spend. PaidSync is also a Meta Business Partner, a LinkedIn Marketing Partner and a TikTok Marketing Partner.
See how we build with teams Book a founder callFrequently asked questions
How do I connect Google AdWords to Microsoft Copilot Studio?
Google AdWords is the old name for Google Ads. Create a PaidSync account, connect Google Ads with the Google account that owns your ads, then in Copilot Studio open your agent and go to Tools, Add a tool, New tool, Model Context Protocol. Paste https://mcp.paidsync.ai/mcp, choose OAuth 2.0 with Dynamic discovery, click Create and Add to agent. Copilot Studio can now read your Google Ads data and propose changes that wait for your approval.
Does this work in Microsoft 365 Copilot or only in Copilot Studio?
Both, in that order. You add the PaidSync tool inside Copilot Studio, test the agent there, then publish it to the Microsoft 365 Copilot channel. After that it appears in Teams and in Microsoft 365 Copilot. Most tenants need an admin to approve the published agent first.
Which Microsoft account or licence do I need?
A work or school account. Copilot Studio is included with Microsoft 365 Copilot licences and is also available as a standalone subscription or a 30-day trial. The consumer Copilot app does not accept custom MCP servers, so a personal Microsoft account is not enough.
What if my tenant blocks dynamic client registration?
Choose API key instead of OAuth 2.0 in the tool wizard, set it as a Query parameter named api_key, and paste your ps_ key. That path is read-only. Applying a change to a campaign still requires the OAuth 2.0 sign-in, so ask your Power Platform admin to allow the PaidSync connection if your team needs to act, not just report.
Can the agent change budgets and pause campaigns, or only read?
It can do both. Google Ads, Meta Ads and LinkedIn Ads are all build-tier platforms in PaidSync, which means the agent can create campaigns, pause and enable them, and change budgets and settings. Every write is held for approval before it runs. A dry_run preview shows the exact change first, and destructive operations need confirm_destructive.
Is the API key safe to put in the tool URL?
It works, but a key in a URL lands in logs and browser history. That is why OAuth 2.0 is the primary path in Copilot Studio and why the key path is read-only. If you use the key, treat it like a password and rotate it from the PaidSync dashboard if it leaks.
What does the free plan cover, and what does a team pay?
Free is $0 for 15 tasks per month, enough to test the agent end to end. Pro starts at $99 per month and Team starts at $249 per month. A task is one unit of work the agent completes, such as a report or an applied change. Custom agent builds for larger teams are scoped on a founder call.
Does Microsoft have its own ads MCP server?
Yes, for Microsoft Advertising only. Microsoft's official server has been in a read-only open pilot since June 17 2026. It covers Microsoft Advertising accounts and cannot change anything. PaidSync covers Google Ads, Meta Ads, LinkedIn Ads, Microsoft Ads and ten more platforms from one endpoint, with approval-gated writes.
Related pages
460+ tools. 14 platforms. One endpoint in Copilot Studio, approval on every change.
Book a founder call Start on the free plan