>_

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 Manus

Manus MCP support is rolling out. The intended setup registers the SpendSignoff server in the Manus agent config over OAuth — read-only first, drafts you approve in the SpendSignoff app.

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

Manus support is rolling out

Manus is an autonomous multi-step agent. SpendSignoff support is on the way: the plan is a remote MCP server entry registered over OAuth 2.1, scoped to mcp.read and mcp.draft. No mcp.approve scope exists — Manus can read your linked ad accounts and draft changes, but it cannot push a change live.

The intended config is below. The arc is the same as every other SpendSignoff client: connect, authorize an ad account read-only, review the draft in the SpendSignoff app, then run the two-step Approve and push live flow.

Rolling out

Manus MCP support is in progress. The config below reflects the intended setup. If you are testing early, verify that your Manus build supports remote MCP servers over Streamable HTTP before proceeding.

Intended config

Add the SpendSignoff MCP server to the Manus agent config and complete the OAuth 2.1 handshake:

Settings → Developer → Edit Config, paste the block, then restart Claude.

claude_desktop_config.json

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

Manual config entry

If Manus does not yet surface a UI for MCP servers, add the entry directly to the agent config file:

manus_config.json

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

Three steps to live

1

Connect Manus to SpendSignoff

Add the SpendSignoff MCP server entry to the Manus config and complete the OAuth 2.1 handshake. Manus 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 from the SpendSignoff app. The first authorization is read-only: SpendSignoff reads spend, structure, and performance so the operator can find where budget is wasted. Reads are ungated on every plan, including Free.

3

Review and ship your first approval

Manus drafts a change using propose_change 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.

Manus holds read and draft only

Whatever Manus can reach through SpendSignoff, it reaches with mcp.read and mcp.draft alone. It can read your ad accounts and draft proposed changes. It cannot push a change live — approval happens in the SpendSignoff app, behind a two-step confirm, and every live change 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 Manus.

Next

Connect Claude

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

    Connect Manus — SpendSignoff Docs