What the market looks like right now

Google ships a free, official MCP server for Google Ads. It is read-only and covers a useful set of reporting queries. Meta does not ship an official MCP server — third-party connectors fill that gap, with varying write coverage and no consistent safety model. There are also a handful of commercial products: Adspirer is the best-known at roughly $42K MRR as of mid-2026.

Open-source connectors on GitHub number roughly forty across all platforms. Most of them are thin wrappers over a single platform SDK — they expose the API surface as tools without adding any policy layer on top.

Where SpendSignoff differs from unofficial connectors

• Policy layer — SpendSignoff installs a draft-before-live kernel in FastAPI. Every write through propose_change creates an inert draft; the ad platform API is never called until you approve. Unofficial connectors generally call the API directly on the write tool invocation.
• Audit log — every approved action is recorded append-only with KMS signing. Most open-source connectors produce no structured change record.
• Scope isolation — SpendSignoff requests mcp.read and mcp.draft only; there is no mcp.approve scope to grab. An unofficial connector that exposes apply_change as an MCP tool effectively has all three in one.
• Platform breadth — SpendSignoff covers Google Ads and Meta today, with LinkedIn and TikTok on the near-term roadmap. Most community connectors cover one platform.

Against Adspirer specifically

Adspirer ($115K all-time revenue, $485-$2000/yr tiers as of mid-2026) targets the same buyer. It is the reference product this was built against. The concrete gaps we found: Adspirer has no documented act-without-approval autonomy loop; its pricing is per-call rather than flat account-anchored; and there is no public evidence of a KMS-signed audit log or one-click rollback.

The prices SpendSignoff charges are lower per account. The autonomy loop — propose-only in V1 — is the capability Adspirer does not ship. Whether those differences matter to you depends on your workflow.

How to evaluate any MCP server for ad spend

Ask three questions. First: does a write tool call the ad platform API immediately, or does it stage a draft? Second: is there a structured, signed change record independent of the ad platform? Third: what scope does the OAuth flow request, and does it include anything beyond read and draft? The answers tell you whether a human is meaningfully in the loop.