X shipped X Ads MCP on August 24, 2026, an MCP server that hands AI agents 23 tools for a live ad account through one endpoint, ads-api.x.com/mcp. Ten of those tools write: they create and update campaigns and line items, add or remove targeting, turn a post into an ad, and switch a paused campaign on. The other thirteen read account data, run two performance reports, or search the targeting taxonomy.
MCP is an open standard for connecting AI systems to outside applications and data, not something X built for advertising. X’s own framing, from Monique Pintarelli of X: the intent is to bring “full-funnel campaign management directly into the AI tools they already use,” letting advertisers “optimize faster, reduce friction, and build more advanced AI-driven workflows.” Access runs through the existing Ads Project flow in the X Developer Console and requires at least one X ads account; X names Grok and Claude Code as MCP-capable clients it works with, alongside custom agents built on the MCP SDKs.
The Pause Is a Call, Not a Person
X’s documentation states, verbatim, that “campaigns and line items are always created PAUSED, and nothing spends money until it is explicitly activated.” The published tool list narrows what that guarantees: activate_campaign and activate_line_item sit inside the same ten-tool write group as create_campaign and update_line_item, gated by the same ads.write scope. An agent that can build a campaign can also switch it on, with a second API call under the same scope; the documentation describes no human-approval step. ppc.land’s reading of that design: the paused-by-default rule “bounds the downside of a misinterpreted instruction,” but an agent holding ads.write “can still update an existing campaign, adjust targeting on a running line item and activate what it created.” Activation, in ppc.land’s phrase, “is a tool, not a manual step outside the agent’s reach; the constraint is that activation must be requested rather than inferred.” The one setup that produces a genuinely read-only agent is withholding ads.write from the grant entirely, which stops all ten write tools from loading.
How Are X Ads MCP’s 23 Tools Split Between Reads and Writes?
Of the 23 published tools, 9 read account and campaign data, 2 return performance stats (get_account_stats, get_campaign_reach), 2 search the targeting taxonomy, and 10 write, including both tools that activate a paused campaign or line item. Access runs on three OAuth2 scopes, ads.read, ads.write and offline.access, with access tokens expiring roughly two hours after issue. X’s documentation permits one live OAuth grant per app-and-user pair at a time.
The Word “Measure” Covers Two Tools
X’s announcement language is that advertisers can create, manage, optimise and measure campaigns from the AI tools they already use. The documented tools cover the first three verbs; the fourth rests on two analytics calls. Two tools return analytics, account stats and reach; none is a conversion, attribution or lift-measurement tool, and none of those three appears in the documented list of 23. ppc.land describes what the two tools give back as “performance reporting rather than measurement in the attribution or incrementality sense.” An agent built on this server can assemble a campaign end to end and turn it on. What it hands back afterward is account statistics and reach, not what the campaign was worth.
One Login Revokes the Other
The one-grant rule has a quiet operational edge. Multiple callback URIs can be registered against the same app, but signing in from a second client revokes the first one’s tokens; refresh tokens rotate on each use, and access tokens last roughly two hours. Two clients registered under the same app, one for reporting and one for campaign writes, cannot hold live tokens for the same user at once.
Not First Through This Door
X is not first here. Meta opened its ad system on April 29, 2026 and extended MCP access to all developers on July 16, 2026, with write capability from the start; Google publishes its own Ads MCP integration guide, and TikTok, Pinterest and Snapchat have signalled comparable tooling. elsop has covered a platform that went the other way: OpenAI opened ChatGPT ads to 31 European markets without shipping a self-serve ads manager, so buying a European campaign still runs through an agency or OpenAI’s own sales desk, with self-serve access and the start of personalised ads left undated. X’s server sits at the other end of that gap: a buying surface shipped as an API endpoint rather than an interface.
The documented set has no conversion or attribution tool, so whatever an agent builds and activates still needs a tracking scheme decided by a person before it goes live. elsop’s campaign URL builder generates consistent UTM parameters for that layer, one the MCP documentation does not address in either direction.
Source: X Ads MCP documentation, ppc.land.
