Codex Integration

Connect OpenAI Codex to Tanda, and Codex can read your projects and statements of work, add task items, acceptance criteria and tests while it works in your code, point out what isn't tested yet, and open requests for change (RFCs) or root cause analyses (RCAs) as it finds them.

Server URL: https://agents.testandaccept.com/mcp Authentication: OAuth. You sign in with your Tanda account; there's no API key or token to store.

The Codex CLI, the Codex IDE extension and the ChatGPT desktop app share one MCP configuration, so you set Tanda up once and use it in all three.

Connecting Codex, step by step

Add the server

codex mcp add tanda --url https://agents.testandaccept.com/mcp

Add this to ~/.codex/config.toml:

[mcp_servers.tanda]
url = "https://agents.testandaccept.com/mcp"
http_headers = { "Tanda-Organization" = "acme" }

http_headers is optional: it names the organization (slug, name or ID) your requests default to when you belong to several. To set it up for one repository only, put the same block in .codex/config.toml in that repository, with that repository's organization. Codex reads project configuration only for projects you trust. There are no secrets in it, so it's safe to commit.

codex mcp login tanda

Your browser opens:

Sign in to Tanda with Google, GitHub, Microsoft, or email and password.
Approve access. The consent screen lists your organizations; one connection works in all of them. Choose Read to let Codex view your data, and Write to let it create and update it.

Codex registers itself with Tanda automatically and stores the sign-in for you.

Check the connection

codex mcp list

Inside a Codex session, run /mcp to see Tanda and its tools.

Ask Codex

"List my Tanda organizations."
"In Acme, show the acceptance criteria for SOW Website Rebuild that have no tests."
"Read the acceptance criteria for task Checkout, then write tests for this repo that cover them."

Working with multiple organizations

One connection reaches every Tanda organization you belong to. Name the organization in your request ("In Beta Labs, list my projects"), using its name or slug. To stop naming it, set a Tanda-Organization header in config.toml (above), or say "Work in Beta Labs from now on" and Tanda remembers it for this connection. If you belong to only one, you never need to name it. Every answer says which organization it came from. See Choosing a default organization for details.

Troubleshooting

Symptom	Fix
Tanda isn't listed in `/mcp`	Check `codex mcp list`. If you configured it in a project's `.codex/config.toml`, make sure you trust that project.
Tools return `401`	You haven't signed in yet, or the sign-in expired. Run `codex mcp login tanda` again.
The sign-in page can't reach Codex	Codex receives the sign-in on a local `127.0.0.1` address. On a remote machine or behind a strict firewall, set a fixed port with `mcp_oauth_callback_port` in `config.toml` and forward it.
`403 insufficient_scope` when creating or updating	You didn't approve Write. Run `codex mcp login tanda` and approve it.
"this connection is limited to …"	The sign-in predates multi-organization support. Run `codex mcp login tanda` again.

To disconnect, remove the [mcp_servers.tanda] block from your configuration. codex mcp --help lists the commands to log out and remove servers.

See MCP Client Setup for the full list of tools.

Codex Integration

On this page