Codex

Get your token

Press ⌘K → Connect AI Agent in the board you want Codex to use, then export the token under a name you'll reference from the config:

export KRAFA_TOKEN="krafa_YOUR_TOKEN"

Put the export in your shell profile. Codex reads the variable from the environment it launches in, so a token that only exists in one terminal produces a server that only connects in that terminal.

Add the server

[mcp_servers.krafa-taste]
url = "https://app.krafa.ai/api/mcp"
bearer_token_env_var = "KRAFA_TOKEN"

Or from the CLI:

codex mcp add krafa-taste \
  --url https://app.krafa.ai/api/mcp \
  --bearer-token-env-var KRAFA_TOKEN

A project-scoped .codex/config.toml works the same way in a trusted project.

Keys are flat. Several guides in circulation show a nested transport = { type = "streamable_http", url = "..." } table. That shape only appears in codex mcp get --json output, and putting it in config.toml is a hard parse error.

If you need the header spelled out (say the value isn't a plain bearer token) use env_http_headers instead, which maps a header name to the environment variable holding its full value:

[mcp_servers.krafa-taste]
url = "https://app.krafa.ai/api/mcp"
env_http_headers = { Authorization = "KRAFA_AUTH_HEADER" }

Verify

codex mcp list

The entry shows its URL and the bearer token environment variable it's reading. codex mcp get krafa-taste prints the resolved config, and /mcp inside a session lists the three tools.