Meta Ads and Google Ads in Claude

Ask Claude for spend, results, revenue, ROAS, CPA, CTR, CPM, reach and frequency over an exact period, at the account, campaign, ad set or ad level, for one account or for every account of the workspace. performance_period and metric_compare read the figures, campaigns_structure returns how an account is built, creative_insights groups ads by the image or video they use, and store_revenue sets Shopify or Stripe revenue next to the spend that drove it. Claude reasons over the tables and answers in the conversation.

A new launch starts with launch_brief, which 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 on Meta, and google_ads_build prepares a Search, Display, Demand Gen or Performance Max campaign. A pause, a resume, a duplicate, a split test or a budget change of at most 30% is prepared as one exact change.

• Read results, structure and creative performance across accounts
• Prepare a launch from a brief, built paused when it is applied
• Prepare pauses, budget moves and edits, applied from Adrails

On claude.ai and in the Claude desktop app, the connection is a custom connector. Under OAuth client, keep Use Claude's published identity, the recommended option: Adrails reads Claude's client details from the document Anthropic hosts, and there is no client ID, secret or API key to copy. Register automatically works as well. On a Claude Team or Enterprise plan, an owner of your Claude organization adds the connector first, under Organization settings, then Connectors.

When Claude asks you to allow a tool call, that is Claude's own setting. It does not apply an advertising change: the change waits on its page in Adrails.

• 1. Open Customize, then Connectors, choose Add, then Add custom connector
• 2. Name it Adrails, paste https://adrails.ai/api/mcp as the server URL and keep Use Claude's published identity under OAuth client
• 3. Add the connector, then connect it: Adrails opens, you sign in, choose the workspace and the permissions, and choose Allow access
• 4. In a conversation, open the plus menu, then Connectors, enable Adrails and ask your first question

The server registers 63 tools: the 43 tools the Adrails agents use in the app, from performance reads and creative reviews to launches and budget changes, and 20 tools for accounts, integrations, campaign drafts, automations, Knowledge and job status. Claude lists only the tools the connection's permissions and your role allow, so a read-only connection shows no write tool.

Every tool, its inputs and who can call it is in the MCP tools reference. The server card lists each tool with the schema the server registers, marked read-only or not, so a directory or a reviewer sees the same catalog Claude does.

The sign-in is OAuth 2.1 with PKCE. Claude identifies itself with its published client document, and a client without one registers itself. The consent screen asks for one workspace and the permissions you grant: Read workspace data is required and covers every ad account of that workspace, and Prepare advertising changes is a separate permission that only an owner or admin can grant. A permission never goes beyond your role, and a connection never reaches another workspace.

No tool creates, edits, pauses, switches on or rebudgets a campaign, ad set or ad by itself. A change comes back with a link to the Review advertising change page in Adrails, where an owner or admin applies it or declines it. Adrails reads the platform again first and applies the exact change once, or blocks it if the entity moved in the meantime. A launch is built paused, switching it on is a second proposal that lists every budget that starts spending, and an applied change can be undone while the platform still matches what Adrails wrote. A proposal expires after 30 minutes.

Every tool call is recorded with who made it, the workspace, the client, the tool, the outcome and the duration, never the argument values. Revoke Claude at any time under Your connections on the MCP page in Adrails; removing the connector in Claude does not revoke it there.