>_

SpendSignoff documentation

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

AI client setup

Connect OpenClaw

OpenClaw MCP support is rolling out. The intended setup adds the SpendSignoff server to the OpenClaw MCP config — read-only first, drafts you approve in the SpendSignoff app.

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

OpenClaw support is rolling out

OpenClaw is an open agent client. SpendSignoff support is on the way: the plan is a remote MCP entry registered over OAuth 2.1 with the mcp.read and mcp.draft scopes only.

The intended config is below. Whatever the client surface looks like, the scope boundary holds — read and draft in the client, approval in the SpendSignoff app.

Intended config

Add the SpendSignoff server to the OpenClaw MCP config:

mcp.json

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

Three steps to live

1

Connect the client

Add the SpendSignoff MCP server to your client and finish the OAuth 2.1 handshake. The client requests two scopes only — mcp.read and mcp.draft. There is no mcp.approve scope to grant.

2

Authorize an ad account, read-only

OAuth into Google Ads or Meta. The first authorization is read-only: SpendSignoff reads spend, structure, and performance so the operator can find money. Reads are ungated on every plan, including Free.

3

Review and ship your first approval

The operator drafts a change — say, moving budget off a stalled ad set — and shows the before → after diff. You run the two-step Approve and push live → Confirm control in the SpendSignoff app. Only then does it touch the live account, with a signed audit entry and one-click rollback.

The client only ever holds read and draft

Whatever your AI client can reach, it reaches with mcp.read and mcp.draft alone. It can read your accounts and draft changes. It cannot push a change live — approval happens in the SpendSignoff app, behind a two-step confirm, and is recorded in a KMS-signed append-only audit log.

What works today

  • Read campaigns, ad sets, budgets, bids, and performance across linked Google Ads and Meta accounts.
  • Ask the operator for a plain-English read: pacing, wasted spend, top movers, anomalies.
  • Draft budget reallocations, bid changes, and pacing fixes as reviewable diffs via propose_change.
  • Approve or reject drafts in the SpendSignoff app — never inside the AI client.

Next

Connect Claude

Claude Desktop is live today — start there while OpenClaw rolls out.

    Connect OpenClaw — SpendSignoff Docs