Agent setup
Run the agent in Codex
Codex MCP support is rolling out. Add the SpendSignoff server to the Codex MCP config, authorize an ad account read-only, and approve drafts in the SpendSignoff app.
Codex support is rolling out
Codex is the OpenAI coding agent. SpendSignoff support is on the way: the plan is an MCP server entry in the Codex config, registered over OAuth 2.1 and scoped to mcp.read and mcp.draft.
The intended config is below. The setup arc is the same as every other client — add the entry, authorize an ad account read-only in the SpendSignoff dashboard, then type plain-English instructions and approve drafts in the app.
Intended config
Add the SpendSignoff server to the Codex MCP config:
config.toml
[mcp_servers.spendsignoff]
url = "https://mcp.spendsignoff.com/mcp"Setup steps
Add the MCP server entry
Add the [mcp_servers.spendsignoff] block to your Codex config and restart the agent. Codex will open the OAuth 2.1 flow on first use, requesting mcp.read and mcp.draft.
Authorize an ad account
Open the SpendSignoff dashboard, go to Accounts, and connect a Google Ads or Meta account read-only. The agent reads spend and structure; writes require a draft and your approval.
Review and approve your first draft
Ask the agent to propose a change. It calls propose_change and returns a diff. Open the Approval Queue in the SpendSignoff app and confirm via the two-step Approve and Confirm control.
Read and draft only — the agent cannot spend your budget
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.Next
Run in Cursor
Cursor is live today — the JSON config setup is nearly identical.