>_

SpendSignoff documentation

The always-on operator for your ad accounts. Read and draft from your AI client — approve before anything goes live.

Agent setup

Run the agent in Cursor

Cursor reads MCP servers from a JSON config. Add the SpendSignoff entry, authorize an ad account read-only, and approve drafts in the SpendSignoff app.

Your AI can read and draft — it can never spend without your approval.

Cursor is supported today

Cursor loads MCP servers from ~/.cursor/mcp.json. Add the SpendSignoff entry, restart Cursor, and complete the OAuth 2.1 handshake when it prompts.

Cursor works well for engineers who manage ad accounts and write code in the same flow. The agent drafts changes; you approve them in the SpendSignoff app, not from the editor.

Add the MCP server

Add or merge this block into ~/.cursor/mcp.json:

~/.cursor/mcp.json

{
  "mcpServers": {
    "spendsignoff": {
      "url": "https://mcp.spendsignoff.com/mcp"
    }
  }
}

First-time setup

1

Add the config entry

Add the spendsignoff block to ~/.cursor/mcp.json and restart Cursor. On first use, Cursor opens the OAuth 2.1 flow and requests mcp.read and mcp.draft scopes.

2

Authorize an ad account

Open the SpendSignoff dashboard, go to Accounts, and connect a Google Ads or Meta account. The first link is read-only; the agent reads account data until you authorize writes via the approval flow.

3

Use the agent from the Cursor chat pane

In the Cursor chat pane, type a plain-English instruction such as "which ad sets in my Meta account have a frequency above 4?" The agent calls query_entities with the appropriate filters and returns a structured answer.

4

Review and approve drafts

Ask the agent to propose a change. It calls propose_change, returns a before-and-after diff, and the draft appears in the SpendSignoff approval queue. Confirm it in the app.

Read and draft only — the agent cannot spend your budget

The SpendSignoff Performance Marketing Agent holds mcp.read and mcp.draft scopes only. It reads account data and produces change drafts. It cannot push a change live. Every live change requires a two-step Approve and Confirm in the SpendSignoff app and is recorded in a KMS-signed append-only audit log.

Useful for ad-adjacent development work

Engineers building bidding scripts, reporting dashboards, or data pipelines can use the agent to read live account structure and performance data from Cursor without switching context to a separate ads UI.

Next

Core workflows

The five operations — audit, launch, optimize, report, and monitor — with exact prompts.

    Run the SpendSignoff agent in Cursor