Meta Ads and Google Ads in Cursor

Cursor's agent calls the Adrails tools from the editor. Ask for performance_period on a campaign while you work on its landing page, read campaigns_structure before you change the events a site sends, or have store_revenue set Shopify or Stripe revenue next to spend in a report your project generates. The results are the same tables the Adrails agents use, with the exact data in structuredContent.result.

Launches and changes work the same as in every client. launch_brief says what a clean launch still needs, campaigns_launch or google_ads_build prepares the campaign, and a pause, a budget change of at most 30%, an edit, a duplicate or a split test is prepared as one exact change you apply in Adrails.

• Read results and structure next to the code they depend on
• Build reports from exact figures, with revenue next to spend
• Prepare launches and changes, applied from Adrails

Cursor reads remote MCP servers from a mcp.json file: .cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project. A server is one entry with a url. Cursor's Customize page installs and manages servers too, and switches one off without removing it.

Adrails gives out no client ID or secret, so the entry needs no auth block: the client registers itself and the sign-in happens in your browser. Adrails accepts a localhost callback for an app on your computer and an https callback on a public host, which covers Cursor on the desktop and Cursor's web agents. Cursor asks before it runs an MCP tool by default; that is Cursor's own setting, and an advertising change waits on its page in Adrails.

• 1. Add Adrails to .cursor/mcp.json or ~/.cursor/mcp.json: { "mcpServers": { "adrails": { "url": "https://adrails.ai/api/mcp" } } }
• 2. Sign in when Cursor asks: your browser opens Adrails
• 3. Choose the workspace and the permissions, and choose Allow access
• 4. Back in Cursor, check that the Adrails tools are listed and ask your first question

The server registers 63 tools: the 43 tools the Adrails agents use in the app and 20 tools for accounts, integrations, campaign drafts, automations, Knowledge and job status. Cursor lists only the tools the connection's permissions and your role allow, so a read-only connection shows no write tool. Reads return data and change nothing; a tool that changes an ad account prepares the change and needs an idempotency key.

Every tool, its inputs and who can call it is in the MCP tools reference, and the server card lists each tool with the schema the server registers, marked read-only or not.

The sign-in is OAuth 2.1 with dynamic client registration and PKCE. 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 after Adrails reads the platform again. Everything a launch creates lands 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 Cursor at any time under Your connections on the MCP page in Adrails; removing the entry from mcp.json does not revoke it there.