How to Manage Meta Ads from Cursor: The Full Workflow (2026)

What you can manage from Cursor, at a glance

Everything below runs from the Agent panel once the account is connected. The right-hand column is the honest answer to the question people actually ask: yes, Cursor can change a Meta Ads account — but only through a write tool you approve.

Rows 1 to 3 are the management loop; rows 4 to 8 feed it. On Meta the loop is creative-led — the algorithm does the bidding, so the levers you actually pull are what runs, where it runs and how much it gets.

Step 1: connect the account (about 2 minutes)

Cursor reads MCP servers from .cursor/mcp.json in the project or ~/.cursor/mcp.json in your home directory. A remote server needs only a url. The managed Ryze AI connector is the fastest route because it authenticates with a sign-in and Meta authorization, needs no developer app, and holds no secrets in the file, so the config can be committed for the team.

Self-hosting is possible with an open-source Meta Ads MCP server as a stdio entry; it needs a reviewed Meta developer app and a long-lived token. The five routes are ranked in how to connect Cursor to Meta Ads.

Step 2: the weekly operating loop

Meta accounts fail gradually: creative decays, frequency creeps, one placement quietly eats a third of the budget. The defense is the same five checks every week, in the same order, with the results written down. Each row is one slash command and about ten minutes, most of it reading the output.

Two things make the loop stick. The outputs are files, so Thursday's change run reads Tuesday's fatigue list rather than re-deriving it, and Friday's briefs feed the designers directly. And the changes/ folder is an audit trail: what was paused, what budget moved, why, and what CPA did afterwards — which is what you need when someone asks two weeks later why ROAS moved.

Step 3: diagnose — the three prompts that find the money

Run diagnostics before touching anything. On Meta the three that matter are creative fatigue, frequency and placements; between them they explain most CPA drift. These are the Tuesday and Wednesday jobs; the full skill files have the complete instructions.

Creative fatigue (Tuesday)

Frequency and CPM (Wednesday)

Placements (Wednesday)

State the attribution window in every reporting prompt or put it in the rule; it is the reason numbers do not match Ads Manager nine times out of ten. And read every diagnosis bottom-up: the ranked list is the headline, the evidence lines tell you whether the Agent reasoned from your numbers.

Step 4: optimize — ship changes with two approvals

Thursday is the only day the account changes. Three prompts, each of which ends with the Agent showing a list and waiting. Cursor asks before every MCP tool call; the connector's write tools are approval-gated on the server side as well. Both layers stay on, and nothing touches an ad set inside its learning phase.

Pause the fatigued ads

Move budget between funnel stages

Exclude the money-pit placements

Step 5: report — files the team actually reads

Reporting is where Cursor beats a chat assistant outright. The digest is a Markdown file in the repo, the creative scorecard is a CSV the design team can sort, the briefs are a page they can work from. The Monday and Friday jobs:

Weekly digest (Monday)

Creative scorecard (Friday)

Next-sprint briefs (Friday)

One habit worth building: ask the Agent to append a one-line result to changes/ two weeks after every Thursday change (“paused 4 fatigued ads 2026-09-04: account CTR +11%, CPA -8%”). That closes the loop and turns the folder into the account's memory.

Step 6: automate — what Cursor can schedule and what it cannot

The desktop app runs when you are in it. Three ways to make the loop run without you, in increasing order of hands-off.

Guardrails that keep this safe

Every one of these came from a mistake we made or watched someone make. Put them in the rule file so every skill inherits them.

• Pause, never delete. Deletes are permanent in Meta Ads. The connector's delete tool only runs on an item-by-item approved list; the rule should say the Agent never asks for it.
• Respect the learning phase. No edits to an ad set within seven days of a significant change, or the reset costs more than the fix. Make the Agent check edit history before proposing.
• Show the list, then wait. Every write prompt ends with “wait for my approval”. Cursor's tool approval is the second gate; keep both.
• Cap single changes at 20%. Budgets move in steps. A 35% funnel shift is three Thursdays, not one.
• Name the attribution window. 7-day click vs 1-day view is the reason ROAS does not match Ads Manager. Put it in the rule.
• Log everything to changes/. Date, what, why, and the two-week result. This is the file that saves you in the next budget review.

Cursor vs Claude vs Grok for running Meta Ads

All three connect to the same MCP server, so the data is identical. The difference is what happens to the output and where the work runs.

The practical answer for most teams is to pick the tool they already have open. If that is Cursor, this guide is the workflow; the same loop exists for Claude and for Grok. Running Google as well? The Google version of this workflow is how to manage Google Ads from Cursor.

For the product side, the Ryze help center covers what the Ryze agent manages in Meta ads and approvals.