15 live tools for Microsoft Advertising, every write held for your confirmation, inside the same server that runs Google Ads, Meta, LinkedIn, TikTok, GA4, and GTM. Compared honestly against CData's Bing Ads MCP and the Zapier Microsoft Advertising MCP.
PaidSync is a Microsoft Ads MCP server that manages and optimizes existing Microsoft Advertising campaigns from Claude, ChatGPT, and Gemini. 15 tools cover reading performance, pausing and enabling campaigns, adjusting budgets, and updating campaign and ad-group settings. Every write is held for your confirmation before it touches the account. Free at $0 for 15 tasks a month, Pro from $99/mo, and the same connection also covers Google Ads, Meta, LinkedIn, TikTok, GA4, GTM, and 6 more platforms. New Microsoft Ads campaigns are still built in Microsoft Advertising; PaidSync takes over from day one of live traffic.
An MCP server turns an ad platform's API into typed tools an AI assistant can call. Connect one to Claude or ChatGPT and "pause every Microsoft Ads campaign whose CPA is above $70 in the last 14 days" becomes something the assistant can check, propose, and, once you approve, execute. This page covers PaidSync's Microsoft Ads surface in full: the 15 tools, exactly what they do and do not do, how the approval gates work, and how it compares with the two Microsoft Ads MCP options on most current lists in August 2026.
It is written for both audiences. Marketers who want to run Microsoft Ads day-to-day from a chat window, and agent builders who want to know exactly what the protocol surface looks like before wiring it into a workflow. Each section is labeled.
What a Microsoft Ads MCP server does (and what PaidSync's does not)
Three things, in practice. It reads, so the assistant can pull spend, CPA, CTR, and campaign-level performance without you exporting from the UI. It manages, so existing campaigns and ad groups can be paused, enabled, re-budgeted, and updated through conversation. And it gates, so nothing the AI proposes runs until a human confirms it.
The honest bit up front: PaidSync's Microsoft Ads tool set is manage-only. It does not create new campaigns from scratch, does not create ad groups, does not write keywords, and does not manage bidding strategies as tools of its own. For those, you use Microsoft Advertising directly. PaidSync's role starts the moment a campaign is live and takes daily management, optimization, and reporting off your plate. This is different from the Google Ads, Meta, LinkedIn, and TikTok surfaces, where PaidSync also builds from scratch; see the honest capability matrix on the full MCP server page.
All 15 Microsoft Ads tools by category
PaidSync's live server exposes 15 Microsoft Ads tools (server total 430+ across 13 platforms). The table names all of them; the live catalog is also discoverable from any session via paidsync_context with include_tools:['microsoft'].
| Category | Named tools |
|---|---|
| Account and identity | connect_microsoft_ads, microsoft_auth_status, list_ms_accounts, set_active_microsoft_account, get_ms_active_account, list_ms_ad_accounts, list_ms_customers |
| Read | list_ms_campaigns, list_ms_adgroups, get_ms_performance |
| Manage existing campaigns | pause_ms_campaign, enable_ms_campaign, update_ms_campaign_budget, update_ms_campaign, update_ms_adgroup |
Three of these carry most of the operational work. update_ms_campaign_budget re-paces spend without opening Microsoft Advertising, update_ms_campaign edits name, status, and campaign-level settings, and update_ms_adgroup handles ad-group settings. Combined with get_ms_performance and the list_* readers, a Monday-morning pacing and pausing pass runs entirely in chat.
For marketersManage Microsoft Ads from a chat window
The practical shape of a week on PaidSync's Microsoft Ads stack looks like this. Monday morning you ask "what changed in the last 7 days on Microsoft Ads, by campaign, and where is CPA drifting above target". The assistant pulls it from get_ms_performance and answers in plain numbers. You spot two campaigns pacing over budget on stale creative, ask for a pause on the worst offender and a 30% budget cut on the other, review the drafted changes, and confirm. Later you ask for a status report on live campaigns; the assistant lists them from list_ms_campaigns.
Because the same server carries Google Ads (136 tools), Meta Ads (69 tools), LinkedIn (25 tools), TikTok (13 tools), GA4 (28 tools), and GTM (37 tools), the follow-up question "did the Microsoft budget cut leak volume to my Google Ads Search campaigns, and did GA4 see the shift" is answered in the same session, not in another tab. That cross-platform session is the practical difference between a Microsoft Ads connector and a paid-media server.
Trust is the honest concern with write access, and the answer is procedural, not promissory. Nothing applies without your confirmation, previews show the exact planned change first, and destructive operations require a second explicit confirmation. Sessions can be revoked at any time.
Connect a Microsoft Advertising account to Claude, ChatGPT, or Gemini and run the first pacing report in minutes.
Start free, 15 tasks, no card See all 13 platformsThe protocol surface behind the 15 tools
PaidSync is one MCP endpoint covering 13 platforms; details on the MCP server page. To keep client context small, tools/list returns a lean starter set. The full catalog is discovered at runtime through paidsync_context, which returns the active account, connected platforms, and the grouped tool catalog (include_tools:['microsoft'] returns the exact Microsoft tool names), and executed through paidsync_exec. That two-call pattern means an agent can enumerate and invoke all 15 Microsoft tools without a 430-tool schema payload sitting in every conversation.
Safety is enforced server-side, not left to the client. Writes are approval-gated, most mutation tools accept dry_run for a no-op preview, and destructive operations require confirm_destructive. Sessions can be revoked at any time. For discovery and verification, the domain publishes OAuth authorization-server and protected-resource metadata (RFC 8414 and RFC 9728), an MCP server card, agent-auth.json, security.txt, and a Content-Signal directive, so an agent can establish what this server is and how to authenticate against it before the first task.
PaidSync vs CData Bing Ads MCP vs Zapier Microsoft Advertising MCP
As of August 2026, Microsoft has not shipped a first-party MCP server for Microsoft Advertising. Three practical options show up on current lists. CData's Bing Ads MCP Server is JDBC-backed and analytics-flavored: the main package is read-only and answers natural-language questions by translating them into SQL against Microsoft Advertising data, with a separate free beta that adds write, update, delete, and action capabilities. You self-host it, wire it into your BI stack, and get flexible querying. Zapier's Microsoft Advertising MCP surfaces Zapier's Microsoft Advertising actions through the MCP protocol; the documented action set today is narrow (add contact to a customer list, apply offline conversions, create a customer list), and it inherits Zapier's 9,000+ app ecosystem. PaidSync is hosted, ad-operations focused, and manages existing campaigns across Microsoft plus 12 other platforms in one session.
| Dimension | PaidSync | CData Bing Ads MCP | Zapier Microsoft Advertising MCP |
|---|---|---|---|
| Microsoft Ads tools | 15 named | SQL surface over the API (read-only main package, free write beta) | Narrow documented action set |
| Campaign creation | No, use Microsoft Advertising | Beta write capability | Not the documented use case |
| Manage existing campaigns | Yes, pause, enable, budget, settings | Via SQL update in beta | Limited to documented actions |
| Approval gates on writes | Yes, every write held for confirmation | Not the model | Through Zapier's own auth flow |
| Hosted vs self-hosted | Hosted, connect and go | Self-hosted with JDBC driver | Hosted |
| Platform scope in same session | 13 platforms (Google, Meta, LinkedIn, TikTok, GA4, GTM, and more) | Microsoft Ads only via JDBC, other CData drivers separate | 9,000+ Zapier apps |
| Best fit | Daily management across a paid-media stack | SQL-style analytics over Microsoft Ads data | Customer-list plumbing and offline conversion imports |
| Price | Free $0 (15 tasks), Pro from $99/mo | Free beta, paid commercial license | Free tier plus paid Zapier plans |
Quick verdict.
You want SQL-style querying of Microsoft Ads data inside your BI stack: CData. Purpose-built for that pattern.
Your Microsoft Ads work is customer lists and offline conversion imports, and you already live in Zapier: Zapier's Microsoft Advertising MCP. It plugs into what you have.
You run Microsoft Ads day-to-day and want to pace, pause, enable, and re-budget existing campaigns alongside Google, Meta, LinkedIn, or TikTok in one AI conversation: PaidSync. Approval-gated management across the stack, no bouncing between UIs.
What this does not do
Stated plainly, because scoping a tool accurately beats overselling it.
- No new Microsoft Ads campaigns or ad groups. Build the campaign in Microsoft Advertising, then hand it to PaidSync for daily management.
- No keyword-level writes. Adding, updating, or negating keywords is not exposed as a tool today. Negative-keyword hygiene on Microsoft Ads is handled in the platform.
- No bidding-strategy tools. Bid-strategy changes live in Microsoft Advertising.
- No ad-copy or asset writes. Creating or editing ads themselves is done in Microsoft Advertising; PaidSync manages the campaign wrapper around them.
- No unattended spend. Every write waits for your confirmation. If you want an AI that changes live Microsoft Ads budgets without a human tap, this is deliberately not that.
Roadmap decisions on Microsoft Ads coverage track customer demand. If a capability above is central to your workflow, tell us at the demo booking page so it can be prioritized honestly.
Pricing
Every plan includes all 13 platforms and there is no per-account or per-platform charge. Every tool call counts as one task, whether it reads a report or updates a budget. Full detail at paidsync.ai/pricing.
| Plan | Price | Included |
|---|---|---|
| Free | $0/mo | 15 tasks a month, no card required |
| Pro | From $99/mo | 600 tasks ($99), 1,200 tasks ($149), or 4,000 tasks ($199) |
| Team | From $249/mo | 5 seats, 6,000 shared tasks |
| Done For You | Custom | Fully managed paid media |
Put 15 Microsoft Ads tools, and the other 12 platforms, in front of your AI assistant today.
Frequently asked questions
What is a Microsoft Ads MCP server?
An MCP (Model Context Protocol) server exposes Microsoft Advertising API actions as typed tools that AI assistants like Claude, ChatGPT, and Gemini can call. A Microsoft Ads MCP lets the assistant read campaign performance and manage existing campaigns and ad groups through conversation instead of Microsoft Advertising UI clicks. PaidSync's Microsoft surface is 15 tools, and it does not create new campaigns from scratch.
Does PaidSync create new Microsoft Ads campaigns?
No. PaidSync's Microsoft Ads tool set is manage-only: it reads performance and acts on existing campaigns and ad groups. Building a new campaign is done in Microsoft Advertising, then handed to PaidSync for daily management, optimization, and reporting. This is stated on the page rather than hidden. For platforms where PaidSync does build from scratch (Google, Meta, LinkedIn, TikTok, ChatGPT Ads), see the full MCP server overview.
How many Microsoft Ads tools does PaidSync have?
15 live Microsoft Ads tools, inside a server of 430+ tools across 13 platforms. The set covers account and identity (7 tools), read (3 tools), and manage (5 tools). No campaign or ad-group creation, no keyword-level writes, no bidding-strategy tools today.
How does PaidSync compare with CData's Bing Ads MCP?
CData's Bing Ads MCP Server is JDBC-backed and analytics-focused. The main product is read-only and answers natural-language questions by translating them into SQL against Microsoft Advertising data; a separate free beta adds write, update, and delete. You self-host it, connect it to your BI stack, and get flexible querying. PaidSync is hosted, ad-operations focused, and its write surface is management actions (pause, enable, budget, settings), not raw SQL mutations. Use CData for warehouse-style querying. Use PaidSync to run Microsoft Ads alongside Google, Meta, LinkedIn, TikTok, GA4, and GTM in one AI conversation with approval-gated actions.
How does PaidSync compare with Zapier's Microsoft Advertising MCP?
Zapier's Microsoft Advertising MCP surfaces Zapier's Microsoft Advertising actions through MCP. The documented actions today are narrow (add contact to a customer list, apply offline conversions, create a customer list) and it inherits Zapier's 9,000+ app ecosystem. It does not cover general campaign management. PaidSync is purpose-built for daily campaign management across Microsoft Ads and 12 more platforms, with a smaller general-purpose app surface.
Is it safe to give an AI write access to a live Microsoft Ads account?
PaidSync never applies a change without your confirmation. Every write is approval-gated in chat, most write tools support a dry_run preview, and destructive operations require an explicit confirm_destructive step. Sessions can be revoked at any time.
How much does the PaidSync Microsoft Ads MCP cost?
Free is $0 for 15 tasks a month with no card. Pro starts at $99 per month for 600 tasks, with 1,200 tasks at $149 and 4,000 at $199. Team starts at $249 per month for 5 seats and 6,000 shared tasks. Done For You is custom-priced fully managed paid media. Every plan includes all 13 platforms; there is no per-platform charge.