What it does
Codex reads your Brands and tokens, exports them as code and proposes token changes for a person to approve. The tools are listed at /docs/mcp.
Before you start
- A Stoaken account with at least Viewer on a Brand. On the Free plan agents are read only.
- Codex CLI or the Codex IDE extension (they share
config.toml). - Optional: an API key from Settings > API keys.
Setup
npx stoaken init --client codex
codex mcp login stoakeninit writes .codex/config.toml in the project, keeping everything else in the file. Codex only reads a project's .codex/config.toml once you trust the project; otherwise put the same table in ~/.codex/config.toml. codex mcp login stoaken opens the browser to sign in.
Configuration
[mcp_servers.stoaken]
url = "https://www.stoaken.com/mcp"With an API key instead of OAuth:
[mcp_servers.stoaken]
url = "https://www.stoaken.com/mcp"
bearer_token_env_var = "STOAKEN_API_KEY"Codex reads the key from that environment variable and sends it as Authorization: Bearer. Neither form puts a secret in the file.
Try it
- "Use the stoaken tools to list my Brands."
- "Export the Default theme as Tailwind 4 and update src/theme.css."
Troubleshooting
- Server not loaded: the project isn't trusted, so
.codex/config.tomlis ignored. Trust it or move the table to~/.codex/config.toml. - Connects without auth / 401: neither OAuth credentials nor
STOAKEN_API_KEYresolved. Runcodex mcp login stoakenor export the variable. - Check with
codex mcp list.
Limits
- No tool approves or publishes a release.
- Writes count towards a per-key limit; Free plan is read only.