Can Claude create X Ads campaigns through PaidSync?

No. PaidSync works on X campaigns and line items that already run. Claude can pause and enable them, change campaign daily budgets and line item bids, and rename them. New campaigns, line items and promoted posts are built in X Ads Manager.

What X Ads data can Claude see?

Spend, impressions, clicks and engagements by account, campaign or line item for any date range, and lists of your campaigns, line items and promoted posts. Spend is in the ad account's currency and days follow its time zone. PaidSync has no X conversion or audience report.

Is there an official X Ads MCP server?

Yes. X runs its own Ads MCP server at ads-api.x.com/mcp for X Ads. Its setup page asks you to create an X developer app with Ads API access and use its OAuth 2.0 client ID (checked 30 Sep 2026). PaidSync needs no developer app and puts X next to Google, Meta, LinkedIn and TikTok in one chat.

Is PaidSync free to use with X Ads?

Yes, to start. The free plan gives you 15 tasks with no credit card. Pro is from $99 a month for 600 tasks, Team is from $249 a month for 5 seats and 6,000 tasks, and Done For You is custom.

Does the same connection work in ChatGPT?

Yes. The same PaidSync login works in Claude, Claude Code and ChatGPT, where you add the PaidSync app. Set up PaidSync once and your X Ads account is there in each of them.

Is it safe to let Claude change live X campaigns?

The update tools for budgets, bids, names and status preview a change before it applies and read it back from X afterwards. Every change also shows in X Ads Manager, where you can reverse it. In the PaidSync workspace, by default, every change is an approval card.

How to Connect X Ads (Twitter Ads) to Claude

How to connect X Ads to Claude with PaidSync

This is the route through Claude's connector directory. No API key is needed, because Claude connects with a PaidSync sign-in (OAuth).

Before you start

Any Claude plan works, including Free, and there is nothing to install.
Signing in with Google? There is no separate sign-up. You pick Continue with Google in step 2, and your free PaidSync account (15 tasks, no credit card) is created when you press Approve.
Prefer an email and password? Create the account at paidsync.ai/signup before you start. The sign-up link inside the sign-in window opens the website and does not bring you back to Claude.
Know which X account can open your ad accounts in X Ads Manager. You use it in step 3. You do not need an X developer account.
On a Team or Enterprise plan, an Owner adds PaidSync for the organization under Organization settings, then Connectors. Each person then connects with their own PaidSync login.

Add PaidSync to Claude from the connector directory

Open PaidSync in the Claude connector directory and click Connect. Or, in claude.ai or the Claude Desktop app, open Customize, then Connectors, click + next to Connectors, search PaidSync, and click Connect.

Sign in with your PaidSync login. That OAuth sign-in is what lets Claude apply changes. Connectors work on every Claude plan, including Free.

Using Claude Code instead? Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, then type /mcp inside a session to sign in.

On a client with no directory, add PaidSync as a custom connector with the server URL instead (on a Team or Enterprise plan, only an Owner can add one):

https://mcp.paidsync.ai/mcp

Save it, then sign in with your PaidSync login when Claude asks.

Sign in to PaidSync and press Approve

The PaidSync sign-in screen opens. Pick Continue with Google, or sign in with your PaidSync email and password. A PaidSync screen then asks whether to allow Claude to manage your ad accounts via PaidSync. Press Approve and Claude shows PaidSync as connected.

New to PaidSync and signing in with Google? Your free account (15 tasks, no credit card) is created when you press Approve. The screen also mentions ad accounts already connected inside PaidSync. On a new account that list is empty until you finish step 3.

Connect your X Ads account and ask Claude

In any chat, ask: "Connect my X Ads." Claude replies with a link. It opens X's own sign-in and authorize screen. Sign in with the X account that can open your ad accounts and authorize PaidSync. PaidSync never sees your X password.

Come back and ask: "List my X ad accounts." Claude uses list_x_accounts to show them and set_active_x_account to pick the one you name. Connecting X, listing your ad accounts and picking one uses none of your tasks. Then try: "Show my X campaign performance for the last 7 days."

What PaidSync can and cannot do on X Ads

PaidSync has 14 X Ads tools. They work on campaigns and line items that already run.

PaidSync can

Read performance. Spend, impressions, clicks and engagements by account, campaign or line item for any date range, in the ad account's currency and time zone.
List what runs. Campaigns, line items and promoted posts on the ad account you picked.
Pause and enable. Campaigns with pause_x_campaign and enable_x_campaign, and line items through update_x_line_item.
Change budgets and settings. Campaign daily budgets with update_x_campaign_budget, line item bids, and campaign and line item names.

PaidSync cannot

Create. No new campaigns, line items or promoted posts, and no creative uploads. Build those in X Ads Manager.
Targeting, audiences and conversions. PaidSync has no X tool for targeting, tailored audiences or conversion reporting.

Budget, bid, name and status edits through the update tools preview as a dry run by default and are read back from X after they apply. In the PaidSync workspace, by default, every change is an approval card. The full list of the 14 tools is on the X Ads MCP server page.

X Ads prompts to try in Claude

Each prompt runs on the PaidSync tools named after it and uses one or more of your tasks. Budget, bid, name and status edits through the update tools preview by default, and Claude applies them when you ask.

"Show my X campaigns from the last 7 days with spend, impressions, clicks and engagements." Runs get_x_performance at campaign level, which lists campaigns by spend.
"Which X line items spent the most in the last 30 days, and what did each pay per click?" Runs get_x_performance at line item level. Claude works out cost per click from spend and clicks.
"Pause the Spring Launch campaign on X." Runs list_x_campaigns to find it, then pause_x_campaign. enable_x_campaign turns it back on.
"Preview setting the daily budget on the Retargeting campaign to 80." Runs update_x_campaign_budget, which previews by default. The budget is in the ad account's own currency.
"Preview lowering the bid on the Lookalikes line item to 1.50." Runs list_x_line_items to find it, then update_x_line_item, which previews by default.

Why use PaidSync for X Ads in Claude

One sign-in, no developer app. You authorize PaidSync on X's own screen. There is no X developer app to create, no client ID to copy and no API key.

Built for cross-platform work. X rarely runs alone. With Meta or Google connected too, Claude puts X spend and clicks next to theirs in the same conversation.

One connection, 14 platforms. X Ads sits next to Google Ads, Meta, LinkedIn, TikTok, Microsoft Ads, GA4, Google Tag Manager and more, 610+ tools at one endpoint. PaidSync holds Google, Meta and TikTok partner status.

Other ways to connect X Ads to Claude

Each of these works differently from PaidSync. One line on each, from its own current page.

X's own Ads MCP server. X runs one at ads-api.x.com/mcp for X Ads. Its setup page asks you to create an X developer app with Ads API access and use its OAuth 2.0 client ID, and it names Grok and Claude Code as clients (checked 30 Sep 2026).
Zapier. Zapier's page for its Twitter integration says it was deprecated effective 31 August 2023 (checked 30 Sep 2026).
n8n. n8n's X (Formerly Twitter) node covers posts, direct messages, users and lists, and its docs list no ads operations (checked 30 Sep 2026).
Build your own. Write an MCP server on the X Ads API, register an X developer app, and host and maintain it yourself.

How do I connect X Ads to Claude Code?

This guide is for the Claude app. In Claude Code, adding PaidSync is one command:

claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp

Start a session, type /mcp, pick paidsync, and sign in with your PaidSync login in the browser window that opens. Then ask Claude Code to connect your X Ads, the same as step 3. No key is pasted anywhere. The Claude Code setup page covers the shared .mcp.json for teams and a headless audit run.

Troubleshooting X Ads in Claude

The sign-in fails. Sign in to PaidSync the way you signed up, with Continue with Google or with your PaidSync email and password. Email users without an account create one at paidsync.ai/signup, then click Connect in Claude again. If X's authorize screen fails, ask Claude "Connect my X Ads" again for a fresh link.
Claude picked the wrong ad account. Ask Claude to list your X ad accounts and switch to the one you mean, by name or ID. It runs list_x_accounts, then set_active_x_account, and every X request after that goes to the account you picked. Switching uses none of your tasks.
An ad account is not listed. PaidSync lists the ad accounts that the X account you authorized can open. Check in X Ads Manager that this X account has access to the ad account, or ask an account admin to add it, then ask Claude to list your ad accounts again. Still missing? Email support@paidsync.ai.
Claude says it has no X tool. PaidSync shows Claude a short starter list of tools to keep the chat light. Ask Claude to call paidsync_context before anything else. It returns your connected platforms and the full tool list, X included, and Claude then runs those tools through paidsync_exec. If PaidSync is missing from Claude altogether, check that it shows as connected under Customize, then Connectors.