Run Meta Ads from Cursor

Valkiria reads the Meta ad account you connected over Meta OAuth and gives the assistant Facebook and Instagram campaign results, lead forms with their leads, the audit findings and the care recommendations. Cursor reads the Valkiria server from a config file and authenticates with a developer API key in a header. The key carries the scopes you gave it, so you decide up front whether the editor can only read or also propose.

Checked:

01

Connect Cursor in 3 steps

  1. In Valkiria create a developer API key with the scopes you need.
  2. Add the server to .cursor/mcp.json as shown below, replacing vk_live_… with your key.
  3. Restart Cursor and tell the assistant: "Get started with Valkiria".
  • This recipe uses a header instead of a sign-in, so it needs a developer API key. Developer API keys are part of the plans that include API access; the pricing page shows which.
  • Keep the key out of version control: put .cursor/mcp.json in .gitignore or use a user-level config.
.cursor/mcp.json
{
  "mcpServers": {
    "valkiria": {
      "url": "https://valkiria.pro/mcp",
      "headers": { "Authorization": "Bearer vk_live_…" }
    }
  }
}

02

What works for Meta Ads today

Connection: Meta OAuth with the Marketing API scopes. Tokens are stored encrypted and can be revoked from Valkiria or Business Manager.

The assistant can read

  • Campaigns with status and budgets across Facebook and Instagram.
  • Dated spend, clicks and conversions per currency for an explicit date range.
  • Lead forms and the leads they collected.
  • Open findings of the standing campaign audit and the care recommendations with a preview.
  • Live from Meta: ad sets and ads, delivery status, ad performance, placement breakdown, creative fatigue and wasted spend, plus audiences, pixels and Pages.

The assistant can propose or request

  • Propose a campaign or ad set budget, an ad set schedule, targeting or placements, new ad copy, a new ad set or ad, a duplicate of a campaign, or promoting a Page post.
  • Approve or reject a care recommendation after previewing what it changes.
  • Request a pause or a resume of a campaign.
  • Create a campaign draft inside Valkiria. A campaign that later reaches Meta is created PAUSED.
  • Pull new leads from Meta into Valkiria on request.
  • Create and update automation rules.
  • Create a monitor that checks the account on a schedule and notifies you or queues a proposal, and schedule a report by email. Neither changes an ad account by itself.

Live integration statusMeta Ads in Valkiria

03

Prompts to try: Meta Ads in Cursor

Copy one, replace the parts in brackets and send it. The assistant picks the tools itself.

  1. Which Meta campaigns had the biggest jump in cost per result over the last 14 days compared with the 14 days before?

  2. List my Meta lead forms and how many leads each one collected this month.

  3. Show the 20 newest leads from my Meta lead forms with the form each came from.

  4. List the open audit findings for my Meta account and tell me which ones cost money right now.

  5. Export this month's Meta leads to leads/meta-this-month.csv and list the forms that produced none.

  6. Read the ad copy in copy/meta.md, write three variants per ad and save them next to the originals.

04

How changes stay safe

  • This client authenticates with a developer API key in a header. The key can only do what its scopes allow; create a read-only key if the editor should never propose changes.
  • Two scopes, chosen by you at sign-in: read, and propose. With read alone the assistant cannot request any change.
  • A change requested from an assistant is a proposal. It waits in Approvals in Valkiria until the account owner approves it, unless the write policy you set for that account allows that kind of change by itself.
  • New campaigns are created paused. Starting new spend and deleting always wait for a person.
  • The assistant can list what is waiting for approval and reject a proposal. It cannot approve one: approval stays with the owner in Valkiria.
  • The change history shows who or what made each change and the value before and after, with Undo where the change can be reversed.
  • You can disconnect an assistant at any time on the Connect AI page; a developer API key can be deleted the same way.

05

Limits

Meta Ads

  • Lead data is personal data: the assistant sees leads only with a key or grant that includes the leads scope.
  • Deleting from the assistant removes a Valkiria draft only, never a campaign in Meta.

Cursor

  • A developer API key is required, and developer API keys are not included in every plan.
  • A key does what its scopes allow until you delete it, so create a read-only key if the editor should never propose changes.
  • The assistant sees only your own Valkiria workspace, and only the ad accounts connected there.
  • Numbers are as fresh as the last sync or import; the assistant can tell you when that was.
  • Money stays in each account's own currency. Different currencies are not converted or added up.
  • Reading data is not counted against the monthly allowance; changes and AI generations are. Allowances per plan are on the pricing page.

06

FAQ

Ask Cursor about your Meta Ads account

Create a free account, connect an ad account and add the connector. The first pass only reads.

Drag to move. Alt + arrow keys move the button; Alt + Home resets its position.

Cookie Preferences

We use cookies to enhance your experience. Essential cookies are always active. You can manage optional cookies below.

Essential
Analytics
Marketing
Third-Party