Google, Meta, and TikTok each ship official Ads MCP servers for campaign management on one platform. Complementary to adscapi's multi-platform conversion fan-out.
In 2026 Google, Meta, and TikTok each shipped official MCP servers for their Ads APIs. They are read- and campaign-management oriented: query performance, launch or edit campaigns, and change budgets — one platform per server. They let an agent manage campaigns on that network. adscapi lets an agent fire one conversion across ~28 platforms at once (write-side fan-out) and read spend/ROAS back. Complementary, not overlapping.
| Dimension | adscapi | Official ad-platform MCP servers |
|---|---|---|
| Direction | Conversion fan-out + measurement | Campaign management (read + buy/edit) |
| Platforms | ~28 destinations from one call | One platform per official MCP server |
| Conversion write-fan-out | Yes — one event to every configured CAPI | No — not their job |
| Agent interface | MCP (plus SDK, CLI, HTTP relay) | MCP |
| What an agent does | Report conversions everywhere and close the loop | Query performance, launch/edit campaigns, set budgets |
| Relationship | Complementary write-side fan-out | Complementary per-platform campaign ops |
Billing is described by model only — check each vendor for current prices. adscapi is MIT-licensed open source; you bring your own platform tokens.
adscapi is free and open source. Set your platform tokens, call track() once, and every configured Conversions API receives the event — hashed the way each platform expects.
Back to the compare hub for every competitor, or read the docs to install.