X Ads MCP serverX Ads MCP Server for any AI client.
NotFair connects your X Ads account to Claude, Codex, Cursor, and any MCP client — 40 tools to inspect campaigns, find issues, and stage approved changes.
No credit card required · Read live data, approve every write
MCP endpoint
https://notfair.co/api/mcp/notfairLive tools
40New to MCP? Read the spec at modelcontextprotocol.io.
30-second setup video
Connect Claude to X Ads
Watch the complete NotFair setup—from choosing your ad account to confirming the connection inside Claude.
Watch on YouTubeTools exposed
40What your AI client can read and change
Read tools provide live ad-account context. Write tools propose changes — every write requires explicit human approval before it hits the X Ads API.
| Tool | Type | What it does |
|---|---|---|
runScript | Read | Sandboxed JS with X Ads API fan-out — fan out 20 calls in one pass for audits and analysis. |
getAnalytics | Read | Performance analytics with breakdowns: spend, impressions, engagements, CTR, CPC, CPM, conversions. |
listCampaigns | Read | List campaigns with status, objective, budget, funding instrument, and schedule. |
listLineItems | Read | Line item details: objective, bid strategy, daily/total budget, targeting summary. |
listPromotedTweets | Read | Promoted Tweets with status, parent line item/campaign, and creative envelope. |
getAdAccount | Read | Account snapshot: currency, timezone, funding instruments, amount spent, status. |
| and more | ||
Ready to wire up your client?
Sign in to NotFair, link your X ad accounts, then paste a config above into your MCP client.
FAQ — NotFair X MCP server
Common questions about authenticating, configuring, and using the NotFair X Ads MCP server.
It's a hosted Model Context Protocol server that exposes your X (Twitter) ad accounts to MCP-compatible AI clients. Read tools provide live campaign context for diagnosis; write tools propose fixes that you approve in chat.
Claude.ai users install the published Notfair connector from Claude's directory. Claude Code, OpenAI Codex CLI, Hermes Agent, OpenClaw, Cursor, Cline, and custom MCP clients connect to the appropriate hosted NotFair MCP endpoint.
No. The X Ads MCP server is hosted at https://notfair.co/api/mcp/notfair. You just point your client at it and authenticate.
OAuth 2.0 with PKCE is the recommended flow — Claude.ai and Codex run it automatically. For clients that don't support OAuth, you can use a Bearer token via the Authorization header. Generate either at notfair.co/connect/x-ads.
Yes. Connecting to NotFair's X MCP is free with no credit card. Paid plans unlock higher usage limits and team features.
Only with your explicit approval. Write tools propose changes (pause campaigns, adjust budgets, rename entities, etc.), the client surfaces them, and you confirm before anything hits the X Ads API. Read access is unrestricted; write access is gated.
X Ads runs everything under a single ad account: funding instruments pay for campaigns, campaigns hold line items, and line items deliver promoted Tweets. The MCP exposes everything X surfaces through the X Ads API: campaigns, line items, promoted Tweets, targeting, and analytics.
Per-client setup guides
Walkthroughs for each supported client.
Claude × X Ads
Set up the NotFair X Ads MCP in Claude.
Read setup guideClaude Code × X Ads
Set up the NotFair X Ads MCP in Claude Code.
Read setup guideCodex × X Ads
Set up the NotFair X Ads MCP in Codex.
Read setup guideCursor × X Ads
Set up the NotFair X Ads MCP in Cursor.
Read setup guideOpenClaw × X Ads
Set up the NotFair X Ads MCP in OpenClaw.
Read setup guideHermes × X Ads
Set up the NotFair X Ads MCP in Hermes.
Read setup guideCompare X Ads MCP servers on tools, media, and write safety
See NotFair, Markifact, and AdKit compared on monthly operations, X-specific tool count, image/video upload, approvals, and public verification prompts. There is no official X Ads MCP.