Ad Platforms

X Ads

23 tools for X (formerly Twitter) Ads: accounts, campaigns, line items, funding instruments, targeting criteria, promoted posts and reach and performance stats. MCP Ads proxies X's own Ads MCP server rather than reimplementing the REST API, so Claude gets the same access X's official tooling has, through one MCP Ads connection.

What you can do

Claude can list your X Ads accounts and the campaigns inside them, drill into line items and the funding instruments that pay for them, pull reach and performance stats at account or campaign level, and search targeting criteria by interest or location before applying them to a line item. It can also promote an existing post from the account rather than authoring a fresh creative.

  • List accounts, campaigns, line items and funding instruments
  • Pull account and campaign reach and performance stats
  • Create and update campaigns and line items, and activate a campaign
  • Search interests and locations, then add or remove targeting on a line item
  • List the account's posts and promote one of them
  • See which entities are active right now and which web event tags exist

Why this is a proxy, not a rebuild

X publishes its own Ads MCP server. MCP Ads connects to it directly instead of maintaining a separate REST integration, so the tool coverage stays aligned with what X itself exposes rather than drifting out of sync with a hand-maintained wrapper. The practical consequence is that when X adds a capability to its gateway, it becomes reachable here through the generic call tool before a dedicated wrapper exists, and you can list the gateway's tools directly to see the current surface.

  • x_ads_list_gateway_tools shows exactly what X's server offers today
  • x_ads_call_tool reaches any of those tools, including ones without a named wrapper here
  • Named tools such as x_ads_campaign_reach are stable wrappers over the most-used gateway calls

Connect the account

X Ads connects in the browser. You sign in to X with the account that holds access to the ads account, approve the permission screen, and MCP Ads holds the grant. There is no X developer app to create and no API keys to manage.

  1. Open Connections and pick X Ads

    From the MCP Ads dashboard, choose X Ads. The browser opens X's authorisation page.

  2. Sign in with the X account that owns or administers the ads account

    X Ads access follows the X login. If an agency user manages a client's ads account, that user's login must already be added to the ads account in X Ads Manager; a login with no ads role authorises and then sees no accounts.

  3. Confirm the ads accounts

    The dashboard lists the ads accounts the login can reach. Each request to Claude names one of them, so note the account ID if you have several.

  4. Ask for something real

    Structure first, then stats, so you can see the account Claude found before trusting a number from it.

    Try this first
    List my X Ads accounts and their active campaigns, then
    show reach and engagement stats for the last 7 days on
    the main account, and tell me which line items are live.

Representative tools

Generated from the live server registry. These are real tool names Claude can call today; the full list is in the reference.

x_ads_list_accountsx_ads_list_campaignsx_ads_account_statsx_ads_campaign_reachx_ads_search_targeting_interestsx_ads_promote_post

Safety on this platform

Careful

X exposes real writes here: creating and activating campaigns, creating line items, adding targeting and promoting posts. A newly created campaign is not active until you ask for it to be activated, and there is no tool to delete a campaign or a funding instrument. Because x_ads_call_tool can reach anything on X's gateway, treat a request that uses it as a write until you have checked what the underlying tool does.

Troubleshooting

  • Authorisation completes but no ads accounts are listed: the X login has no role on the ads account. In X Ads Manager the account owner adds users under Account access; reconnect after that.
  • A tool call fails with an error from X's gateway rather than from MCP Ads: the request is being proxied, so the message is X's own. Run x_ads_list_gateway_tools to check the tool still exists and its parameters have not changed.
  • A promoted post is rejected: X only promotes posts from the same account that owns the ads account, and only ones that pass its ad policy. Check the post is on the right handle and is not a reply or a quote of a restricted post.
  • Stats come back empty for a campaign you know ran: X stats are granular by entity and time; ask for the campaign by ID with an explicit date range, and remember that a campaign paused for the whole range legitimately returns nothing.

Go further

Common questions

What is a funding instrument?

X's name for the payment method attached to an ads account. Every campaign is charged to one, and creating a campaign requires naming it, which is why there is a tool to list them.

Why does X use "line items" instead of ad groups?

That is X's own structure: a campaign holds line items, and each line item holds targeting, bid and the promoted posts. Claude uses X's terms so its answers match what you see in X Ads Manager.

Can Claude write the ad copy and post it?

The X Ads tools promote existing posts from the account. Posting new organic content is a separate capability; if it is connected, Claude can publish the post first and then promote it through X Ads.

What happens if X changes its Ads MCP server?

Because MCP Ads proxies X's server, changes appear here without waiting for a wrapper update. The named tools are stable; anything new is reachable through x_ads_list_gateway_tools and x_ads_call_tool until a named tool is added.

Go deeper on X Ads

Ready to connect?

Start free, connect the platforms you use, and run your first workflow from Claude in minutes.