X Ads MCP vs Get MCP Ads

Twenty-three, on X's developer page: nine account and inventory reads, two analytics, two targeting searches, ten writes. Auth is the advertiser's own OAuth2 token with ads.read, ads.write and offline.access. Campaigns and line items are always created paused. Nothing spends until activate_campaign or activate_line_item.

1. 01If the job is X Ads, use X's own Ads MCP at ads-api.x.com/mcp, not this gateway.
2. 02If the job is Google, Meta, TikTok, Pinterest, GA4 or Search Console, paste the Get MCP Ads URL into your MCP client.
3. 03Connect those platforms in the dashboard and tick accounts.
4. 04Do not look for an X row to tick. There is not one.

That count is X's inventory on X's server. We will not pretend it is ours, and we will not hide it behind a fetch failure. Primary page: X Ads MCP docs.x.com/x-ads-api/mcp. If X adds tools, their docs move first. This gateway's catalogue will not grow an x_ads_* name until we actually ship a source, which we have not.

Paused creates on X are their safety rule. Paused creates on Get MCP Ads are our safety rule, on Meta, Google, TikTok and Pinterest. They look similar and they are not the same product. Confirm on this gateway is confirm: true on a paid plan. Activate on X is activate_campaign on X's server. Do not mix the two in one sentence as if we proxy X.

No. There is no X Ads source. The live sources are Meta Ads, Pinterest Ads, Google Ads, TikTok Ads, Search Console, Google Analytics 4. Microsoft Advertising is soon: OAuth exists, tools do not. An assistant connected to this gateway cannot list, pause or create X campaigns, because those tools are not in the catalogue. There is nothing to tick.

If an assistant claims an x_ads tool on this URL, it is inventing. Use X's URL for X. Use this URL for the six live sources. See One MCP URL for six live sources. Our Microsoft soon row is not a substitute for X, and it is not Microsoft's official MCP either.

Yes, as two servers. X's Ads MCP is their endpoint and their OAuth. Get MCP Ads is mcp.getmcpads.com/mcp and our ticked-account allowlist. They do not share a token. Adding X's server does not create an X source inside this gateway. Adding ours does not proxy X. Two connectors, two products, two allowlists.

Most desks that buy X and Google will hold both connectors. That is two OAuth grants and two tool lists, which is correct. What is incorrect is expecting this gateway to grow X tools because X launched. Official launch posts do not change our catalogue. Pricing on this product does not include an X row. There is no X Ads.

Microsoft Advertising MCP is a separate official open pilot. Adding Microsoft's endpoint is a third connector, with Azure AD OAuth. Our Bing OAuth, where it exists in the dashboard, still exposes no tools. Three products, three catalogues. See Microsoft Advertising MCP pilot.

Do not use this gateway when the work is X Ads, when you need X's 23-tool catalogue including activate_campaign, or when you need Microsoft Advertising tools today. Use X's server for X. Use Microsoft's pilot for Microsoft. We do not proxy either.

• The work is X Ads. Use X's server. We do not proxy it.
• You need X's 23-tool catalogue, including activate_campaign. That lives at ads-api.x.com/mcp.
• You need Microsoft Advertising tools today. Our OAuth exists; our tools do not. Microsoft's own MCP is a separate open pilot.

If the work is Google, Meta, TikTok, Pinterest, GA4 or Search Console, this URL is still the hosted path with a ticked-account allowlist. The X launch does not remove those six sources. It also does not add a seventh. Treat any roadmap rumour that we will ship X as outside this page. This page describes what ships today.