Ask
Ask in your assistant
A question or a request, in plain words.
- Client
- Claude
- Workspace
- Chosen at consent
- Request
- Scale the best ad set
MCP server
The Adrails MCP server lets Claude, ChatGPT, Claude Code, Codex and other remote MCP clients work on your Meta ad accounts. Sign in with OAuth, choose one workspace and its permissions, then ask. Reads return your figures, and every change comes back as a proposal you approve in Adrails.
Reviewed Oct 3, 2026
Product view
Your assistant reads the same workspace you open in Adrails. Check a figure in Campaigns or Analysis, and review the change it prepared before it reaches Meta.
Product workflow
Your assistant reads through the server, prepares one exact change, and stops. The change reaches Meta only after you approve it in Adrails.
Ask
A question or a request, in plain words.
Read
Read tools return your figures and change nothing.
Proposal
A write tool returns a proposal and its link, nothing more.
Approval
You review the exact change, signed in as yourself.
Illustrative workspace data. Values show the product flow and are not customer results.
MCP tools
Each name is the tool your client lists. A read changes nothing. A proposal returns a link, and the change waits for your approval in Adrails.
01
Ask for spend, results, revenue, ROAS, CPA, CTR, CPM, reach and frequency over an exact period, at the account, campaign, ad set or ad level, and compare it with another period. The server reads Meta for that ad account and returns a table your assistant reasons over.
Other tools go past raw figures: they review campaigns against their actual objective, say whether each budget should be kept, raised, cut or investigated, and group ads by the image or video they use to find winners and fatigue.
02
A new Meta launch starts with launch_brief. It takes only what you said or chose and returns what a clean launch still needs, as questions with options: the ad account, objective, pixel and event, countries, budget, dates, Page and copy. Once nothing is missing, campaigns_launch prepares the campaign, ad sets and ads.
After you approve, Adrails sends the images or Google Drive files to the ad account and builds everything paused. Switching the ads on is a second proposal, and it lists every budget that starts spending.
03
A pause, a resume, a budget change of at most 30%, a duplicate or a split test is prepared as one exact change. The result is marked awaiting approval and carries a link to the Review advertising change page in Adrails, where you choose Approve this change or Decline.
On approval, Adrails reads Meta again and applies the change once, or blocks it if the entity changed in the meantime. A proposal expires after 30 minutes, and an applied change can be undone while Meta still matches what Adrails wrote.
04
Add https://adrails.ai/api/mcp to your client. It registers itself and opens Adrails in your browser, where the consent screen asks for the workspace and the permissions. There is no client ID, secret or API key to copy.
Read access is required and covers every ad account in that workspace. Preparing advertising changes is a separate permission that only an owner or admin can grant. Revoke a client at any time under Your connections on the MCP page.
FAQ
A server that speaks the Model Context Protocol, so an AI assistant such as Claude or ChatGPT can call tools that read and act on Meta ad accounts. Adrails runs one at https://adrails.ai/api/mcp, and your assistant signs in to it with your Adrails account.
Claude on claude.ai and in the desktop app, Claude Code, ChatGPT with Developer mode and Codex are documented step by step. Any client that supports remote MCP over Streamable HTTP, with OAuth and dynamic client registration, connects the same way.
No. No tool creates, edits, pauses, switches on or rebudgets a campaign, ad set or ad by itself. It prepares a proposal, and only you, signed in to Adrails as an owner or admin, can approve it. The permission prompt in your AI client is not an approval.
No. Meta is connected once in Adrails. The assistant signs in to Adrails with OAuth, and tool results never contain provider credentials.
No. Your assistant's model does the reasoning, so a tool call uses no agent credit. The one exception is an automation run that contains an agent step. Preparing a proposal needs an active plan.
Yes. A connection covers every ad account in its workspace, and a call can narrow to some of them. To work in another workspace, connect again and choose it.