Advertising and Marketing MCP Servers
2 advertising and marketing MCP servers are cataloged, 0 with verified current-spec support.
MCP servers fronting advertising and marketing platforms: campaign creation and management, audience and catalog operations, creative asset handling, and performance reporting.
- Microsoft Advertising MCP Server
- Spec Support Unverified
Microsoft's own remote-only MCP server for Microsoft Advertising, documented on Microsoft Advertising's Learn setup guide (ms.date 2026-07-22); no repository is linked from any fetched Microsoft Advertising or Learn page. Authority is first-party on two Microsoft-controlled surfaces: the Learn guide instructs readers to "Register an OAuth client and connect Microsoft Advertising MCP Server to supported AI clients," and the documented endpoint itself resolves on Microsoft's own bingads.microsoft.com domain. Probed 2026-09-15: 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 challenge naming the endpoint's own RFC 9728 protected-resource metadata document, and a direct GET of that document confirmed the resource URL, two authorization servers, and the required scopes. Neither probe negotiated a specification revision, so spec_status stays unknown. No fetched page names a transport; the setup guide's only signal is a VS Code mcp.json snippet setting "type" to "http," so transports is left empty even though the endpoint plainly accepts JSON-RPC over HTTPS.
- TikTok for Business MCP Server
- Spec Support Unverified
TikTok's first-party MCP server for the TikTok Ads platform, documented on business-api.tiktok.com as packaging roughly 400 TikTok API for Business endpoints as MCP tools. It is served at two paths under /open_mcp/: tt-ads-mcp-flat loads the full tool set at connection time, and tt-ads-mcp-layer loads around 40 core tools with the rest discoverable on demand. Tokens are scoped per path. Authorization is OAuth 2.0 with dynamic client registration and PKCE (S256), access tokens valid 24 hours and refresh tokens 30 days. No TikTok surface names a supported MCP revision, so spec support is unverified.