Reads
Answer straight away. Nothing changes.
- Verified account, funding currency and Ads permissions
- Bounded funding-scoped campaigns and line items
- Seven-day aggregate campaign engagement and billing metrics
Ads · MCP server
Keep X campaign changes within the chosen funding account.
MegaMCP is a hosted X Ads MCP server that lets Claude, ChatGPT and Cursor read accounts, funding, campaigns, line items and performance and propose campaign status and daily cap changes that you approve.
Rolling outBuilt, and switching on as approvals land.What this meansRolling out means the code is built and the platform is still approving MegaMCP's app: Google, Meta, Microsoft and the one-click ad-platform sign-ins switch on as each approval lands.
Also searched as Twitter Ads MCP.
Live demo
Ask in plain English. Your AI reads X Ads with real MegaMCP tools, then hands you a plan. Nothing moves until a person clicks Approve, and supported changes can be undone.
Tools in this example
x_ads_campaign_performanceReads live datax_ads_update_campaignProposes a change planShow this campaign's clicks and billed spend for last week, then pause it.
x_ads_campaign_performanceDone7 daysx_ads_update_campaignWaiting for approvalplan readyLaunch Week spent $198 for 41 clicks. Here's the pause, for your approval.
Paused.
What your AI can do
Read account and funding metadata, campaign and line-item settings, and bounded aggregate performance before reviewing supported campaign status or daily-cap changes. This list comes straight from the running product: 4 read tools and 1 write tool.
Answer straight away. Nothing changes.
Each one returns a plan with a diff. Nothing moves until a person approves.
Updates require current ad-manager/admin access, accepted account state and exact funding/currency binding. Daily caps respect existing total caps. Fresh drift checks and readback apply, but concurrent X edits can race a PUT. ACTIVE can resume charges; provisional billing data can change. Posts, targeting and new campaigns are unavailable.
Plus complete diff previews, human approvals and the flight recorder on every connection. Live changes require a paid plan.
| What it does | Tool id | Type |
|---|---|---|
| Inspect enabled account/funding | x_ads_get_account | Read |
| List funding-bound campaigns | x_ads_list_campaigns | Read |
| List campaign ad groups | x_ads_list_line_items | Read |
| Campaign aggregate performance | x_ads_campaign_performance | Read |
| Review existing campaign status/daily cap | x_ads_update_campaign | Change |
Example prompts
Paste any of these into Claude, ChatGPT or Cursor once X Ads is connected.
“List campaigns using this enabled funding instrument.”
“Read this campaign's aggregate clicks and billed spend for last week.”
“Prepare to pause this eligible campaign.”
“Prepare this daily cap in the verified account currency.”
“Which line items run under this campaign?”
“Verify the account's funding currency.”
“Which campaign spent the most this week?”
“Prepare a lower daily cap for this campaign.”
Setup
About two minutes for Claude, ChatGPT or Cursor. Nothing to install.
Start a free workspace and open Connections. One-click X sign-in is built and appears in your dashboard once X approves MegaMCP's app for Ads API access; each ad account and funding instrument becomes its own switch. Until then, the beta requires an application approved specifically for X Ads API access and a dedicated authorized user's OAuth1 consumer key/secret and token/secret.
Every app uses the same server URL.
https://megamcp.com/api/mcpTry “List campaigns using this enabled funding instrument.” Reports answer straight away. Anything that changes X Ads comes back as a plan for you to approve.
Safety
The same loop guards every MegaMCP connection: ask, see the diff, approve, undo.
X Ads write tools never touch X Ads directly. They return a plan, and a person approves it in the dashboard, or in chat if an admin allows it.
Caps are checked when a plan is built and again right before it's applied, so a change that would blow a cap is blocked.
Supported changes reverse through a separately reviewed undo plan. Anything that can't be undone is marked before you approve it.
Platform checks stop stale edits, and the flight recorder logs every tool call, plan and approval, with who did it and from which AI app.
| Time | Event |
|---|---|
| 09:14 | x_ads_get_account |
| 09:15 | Plan created by Claude |
| 09:16 | Approved by Ana |
FAQ
Yes. As of October 2026, X publishes an X Ads MCP server, hosted, with read and write access depending on the OAuth scopes you grant. MegaMCP keeps X Ads in the same connection as your other ad platforms and limits changes to reviewed campaign status and daily caps within one funding instrument.
An MCP (Model Context Protocol) server lets AI assistants such as Claude, ChatGPT and Cursor use X Ads through tools. MegaMCP's hosted X Ads MCP server gives your assistant 4 read tools and 1 write tool for accounts, funding, campaigns, line items and performance, and every change waits for a human approval.
Yes. MegaMCP is a remote MCP server with OAuth sign-in, so one URL works in ChatGPT (as an app, with developer mode on), Claude (as a custom connector), Cursor, Claude Code and VS Code. Your AI app's own plan decides whether it can add custom MCP servers.
Yes, with your approval. It can propose campaign status and daily cap changes changes. Each one comes back as a plan with a line-by-line diff and waits for a human before anything moves. Updates require current ad-manager/admin access, accepted account state and exact funding/currency binding. Daily caps respect existing total caps. Fresh drift checks and readback apply, but concurrent X edits can race a PUT. ACTIVE can resume charges; provisional billing data can change. Posts, targeting and new campaigns are unavailable.
One-click X sign-in is built and appears in your dashboard once X approves MegaMCP's app for Ads API access; each ad account and funding instrument becomes its own switch. Until then, the beta requires an application approved specifically for X Ads API access and a dedicated authorized user's OAuth1 consumer key/secret and token/secret. All four values are encrypted and locally expire after one hour, bound to one account and funding instrument. Public OAuth onboarding and automatic refresh are unavailable. A general X API subscription does not establish Ads approval; vendor terms and live acceptance still need confirmation. New accounts remain disabled until assigned and enabled.
Reading X Ads is free on MegaMCP's Free plan (100 reads a day, no card). Approved changes are included in every paid plan, from $19/month after a 5-day free trial, with unlimited runs and no credits. MegaMCP adds no markup: your X Ads ad spend is billed by the platform as usual.
Your X Ads credentials are encrypted at rest (AES-256-GCM) and bound to their connection, and MegaMCP never trains AI models on your data. Your AI only sees the accounts you switch on, members limited to certain clients only see those clients, and every tool call lands in the flight recorder.
5 days. On the house.
No credit card to start. Every workspace comes with a sandbox ad account, so you can watch the whole ask, diff, approve, undo loop before you connect anything real.
New integrations, platform approvals, the occasional dark joke. One or two emails a month. Unsubscribe anytime.