# Roster with Codex

Start with a small, read-only question. Keep accounting decisions in Roster.

## 1. Arrange Your Connection

Email **cadyn@rosterroyalties.com** for assisted setup. Specify your Roster login, the label you need, and whether the agent should only read or also prepare review proposals. Never send passwords or API tokens by email or chat.

Roster currently provisions a workspace-scoped connection. There is no self-service “give Codex everything” button. Account-correction execution requires separate permission and exact human approval; it is not part of the default read-and-review setup.

## 2. Technical Configuration

Your technical team can configure the hosted MCP service in the Codex host's `~/.codex/config.toml`:

```toml
[mcp_servers.roster]
url = "https://agent.rosterroyalties.com/mcp"
bearer_token_env_var = "ROSTER_ACCESS_TOKEN"
default_tools_approval_mode = "writes"
tool_timeout_sec = 45
```

`ROSTER_ACCESS_TOKEN` is the **name** of an environment variable, not a credential value. Supply its value through the secure environment of the process running Codex. Do not commit a token to a repository or put it into a shared configuration, prompt or screenshot. Desktop launch environments can differ from terminal environments; ask for setup help if the desktop app cannot see the variable.

Run `codex mcp list` to inspect configured servers, or `/mcp` in the Codex terminal interface. Then ask Codex to call `get_roster_capabilities`. A successful capability response establishes tool availability, not access to every label or execution permission.

Official configuration reference: [OpenAI MCP documentation](https://developers.openai.com/codex/mcp).

## 3. Start With Reads

Replace the fictional name and dates below with the account you intend to review:

> Review Aria Vale for May 2026 in my label. Read only. First confirm the label and artist account match. Show statement IDs, periods, currencies and statuses. Flag possible gaps and cite the evidence. Do not change, approve, notify or pay anything.

Missing records are not a zero balance. Ask whether dates, account matching, imports or source evidence are incomplete. Reconciliation flags are review questions, not certified accounting errors or a guarantee of fully reconciled books.

## 4. Prepare A Review

After inspecting the exact records:

> Prepare a statement-review proposal for these statement IDs in this label. Explain the checks and evidence used. Create only the proposal; do not alter the statements. Give me its reference and review status.

This writes a proposal and its audit event. It does **not** approve statements or apply financial changes. In Roster, open **Ops > Agent Approvals**, find the request, inspect its scope and compare the underlying statements before deciding.

## 5. Understand The Decision

- **Statement-review approval:** records a human review decision; it does not execute accounting changes.
- **Account-correction approval:** authorises only the exact changes and balances shown. A separately permitted executor must still apply them.
- **Approved** is not **Applied**. Check the result and activity after any execution.
- **Needs fresh evidence:** request a new inspection of current records, not approval of stale evidence.
- **Interrupted execution:** some changes may already have saved. Inspect the original proposal and retry it only after checking the result; do not create replacement credits blindly.

Current MCP tools cannot publish statements, send notifications or initiate payments. Import staging has separate preflight, scope and Autopilot requirements and does not create statements. Neither broad tool availability nor an Autopilot policy adds missing API permissions.

## About These Lessons

The Agent Approvals lesson uses the real frontend and one explicitly seeded, non-executable fictional QA proposal. It stops before recording a decision. The Codex lesson combines instructional configuration/prompt slides with real QA navigation. A capability read was verified, but these videos do not demonstrate fresh credential provisioning or end-to-end MCP proposal creation, approval or execution.

For reviewed recoupment carry-forward, see the separate Balance carry-forward lesson. This is not an instruction to use legacy bulk chaining.