Run your ads from Cursor

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

Ad platforms you can ask Cursor about

Each platform works at its own depth. Open one to see what the assistant reads, what it can propose and the prompts to start with.

03

Platforms without an assistant guide

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

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

Connect Cursor and ask the first question

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