Microsoft Advertising MCP Server
Microsoft Advertising MCP Server is an MCP server published by Microsoft; its MCP spec-revision support has not been verified yet. It is the first-party server from Microsoft. Last verified 2026-09-15.
Does Microsoft Advertising MCP Server support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision Microsoft Advertising MCP Server supports (as of 2026-09-15).
Is Microsoft Advertising MCP Server a first-party (official) MCP server?
Yes. Microsoft Advertising MCP Server is the first-party MCP server published by Microsoft (last verified 2026-09-15).
How do I connect to Microsoft Advertising MCP Server?
Microsoft Advertising MCP Server is available via a hosted remote endpoint at https://partner.api.bingads.microsoft.com/ext/mcp/vnext?toolSetNames=OpenBeta. Authentication: oauth. Transports: not verified.
When were Microsoft Advertising MCP Server's facts last verified?
2026-09-15. Each fact on this page links to the sources used to verify it.
Microsoft Advertising's MCP server gives AI assistants read access to live Microsoft Advertising account data: campaigns, ad groups, ads, and keywords, along with performance metrics such as spend, clicks, impressions, and return on ad spend. Microsoft's Learn setup guide documents four clients, Copilot Studio, GitHub Copilot in VS Code, ChatGPT, and Claude, and the announcement additionally named Microsoft 365 Copilot. The server is remote-only; no implementation repository is linked from any Microsoft Advertising or Learn page fetched.
Authority is first-party on Microsoft-controlled evidence: the Learn setup guide instructs readers to register an OAuth client and connect to the "Microsoft Advertising MCP Server," and the documented endpoint, https://partner.api.bingads.microsoft.com/ext/mcp/vnext, resolves on Microsoft's own bingads.microsoft.com domain.
Probes against that endpoint on 2026-09-15 found it live and OAuth-gated. A POST server/discover at protocol revision 2026-07-28 and a legacy POST initialize at 2025-11-25 both returned HTTP 401 with a WWW-Authenticate: Bearer header naming the endpoint's own protected-resource metadata document; fetching that document directly returned RFC 9728 metadata naming the resource, two authorization servers (Microsoft's own and Google's), the msads.manage scope, and offline_access. Neither probe negotiated a specification revision, so spec_status stays unknown. Microsoft announced the server in an August product-news post dated 2026-08-31, as reported here, five weeks after the setup guide first carried its 2026-07-22 date.
How widely adopted is Microsoft Advertising MCP Server?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Microsoft Learn MCP Server Setup Guide, fetched 2026-09-15 (ms.date 2026-07-22) - "Set the Server URL: https://partner.api.bingads.microsoft.com/ext/mcp/vnext?toolSetNames=OpenBeta"; "Register an OAuth client and connect Microsoft Advertising MCP Server to supported AI clients, including Copilot Studio, GitHub Copilot in VS Code, ChatGPT, and Claude"; documents AAD OAuth with token endpoint https://login.microsoftonline.com/common/oauth2/v2.0/token - accessed
- Microsoft Advertising MCP Server product page, fetched 2026-09-15 - "Manage your Microsoft Advertising campaigns from your favorite AI assistant, Copilot, Claude, ChatGPT, or others"; hosted on Microsoft's own about.ads.microsoft.com domain and links back to the same Learn setup guide - accessed
- Endpoint probe 2026-09-15 - POST server/discover with Mcp-Protocol-Version 2026-07-28 to https://partner.api.bingads.microsoft.com/ext/mcp/vnext?toolSetNames=OpenBeta returned HTTP 401 with header WWW-Authenticate: Bearer resource_metadata="https://partner.api.bingads.microsoft.com/ext/mcp/vnext/.well-known/oauth-protected-resource" - accessed
- Endpoint probe 2026-09-15 - legacy POST initialize at protocol version 2025-11-25 against the same URL returned the identical HTTP 401 and WWW-Authenticate challenge, confirming no revision-specific behavior difference between the current and legacy negotiation paths - accessed
- OAuth protected-resource metadata document, fetched 2026-09-15 - GET returned JSON: resource "https://partner.api.bingads.microsoft.com/ext/mcp/vnext", authorization_servers ["https://login.microsoftonline.com/client/v2.0","https://accounts.google.com"], bearer_methods_supported ["header"], scopes_supported ["https://ads.microsoft.com/msads.manage","offline_access"], resource_documentation pointing back at the Learn setup guide - accessed