X AdsX Ads MCP server

X Ads MCP Server for any AI client.

NotFair connects your X Ads account to Claude, Codex, Cursor, and any MCP client — 39 tools to inspect campaigns, find issues, and stage approved changes.

View setup guide

No credit card required · Read live data, approve every write

Works with
X Ads MCP
Live

MCP endpoint

https://notfair.co/api/mcp/x_ads
OAuth 2.0Streamable HTTP

Live tools

39

New to MCP? Read the spec at modelcontextprotocol.io.

Tools exposed

39What 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.

ToolType
runScriptRead
getAnalyticsRead
listCampaignsRead
listLineItemsRead
listPromotedTweetsRead
getAdAccountRead
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.

Or follow a per-client setup guide

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.

Any client that speaks the MCP Streamable HTTP transport — Claude.ai (Web, Desktop, Cowork), Claude Code, OpenAI Codex CLI, Hermes Agent, OpenClaw, Cursor, Cline, and custom MCP clients. The server URL is the same; only the client-side config differs.

No. The X Ads MCP server is hosted at https://notfair.co/api/mcp/x_ads. 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.