Microsoft Advertising MCP pilot

Get MCP Ads provides its own Microsoft Advertising connector with native tools and reporting. Connect through Microsoft in Sources and explicitly select the advertising accounts your assistant may access. It does not proxy Microsoft's MCP endpoint. The source reference lists supported reads, writes and reporting requirements.

The dashboard lets you connect Microsoft Advertising and select the accounts your assistant may access. Native reporting and supported writes are documented in the source reference. Writes require an eligible paid plan and confirmation; account permissions still apply. See One MCP URL for ads and analytics.

Microsoft's 17 Jun 2026 blog describes the open pilot as read-only access to live campaign data. Learn's setup guide does not publish a write catalogue on the page we fetched. That historical description concerns Microsoft's official MCP, not our native connector's write tools. If that changes, it will change on Microsoft's pages first.

Supported Microsoft write tools are available on eligible paid plans, with preview and confirmation before execution. New advertising entities are created paused. Account permissions and provider validation still apply. These are the gateway's controls, not a claim about Microsoft's separate MCP. See Pause a campaign from an assistant.

Google Ads, GA4 and Search Console on this URL are live sources with shipped tools. Official Google Ads MCP is a different Google server you self-host. Microsoft's official MCP is Microsoft Advertising. Three products, three catalogues. This gateway's Google sources do not start including Bing because Microsoft launched a pilot.

Yes, as two connectors, with two OAuth systems: Azure AD for Microsoft, OAuth 2.1 with dynamic client registration for Get MCP Ads. They do not share tokens or allowlists. Adding Microsoft's server does not create Bing tools inside this gateway. Adding ours does not proxy Microsoft.

A desk that buys Microsoft and Google will hold both. That is correct. For our connector, follow the explicit connection status in Sources. X Ads is also available through its own connection, using X’s official MCP. Microsoft and X have separate connectors with documented scopes and account selection. Authorize each provider separately and select its own advertising accounts.

Official X is X Ads MCP vs Get MCP Ads. Official landscape is Official ads MCPs compared. Pricing does not bypass Microsoft access restrictions: purchasing a plan does not enable a restricted source.

Use Microsoft's first-party MCP when you specifically need that service, its authentication or an operation outside our native connector's published scope.

• Use Microsoft's first-party MCP when you specifically need that service, its authentication or an operation outside our native connector's published scope.
• If the account you need is not authorized or selected in Sources, the gateway cannot access it.
• If you need X Ads operations outside the reviewed tool catalog.

For Microsoft Advertising alongside other supported platforms, connect each source and select its accounts on Get MCP Ads. Use Microsoft's separate endpoint only when you need its own service. An authorization or account-selection refusal should be resolved in Sources, not by broadening access implicitly.