Codex
Add Kinesis to Codex, sign in with OAuth, or read an API key from your environment.
Connect Kinesis from the Codex CLI. You need Codex installed and a Kinesis account.
Connect with your Kinesis account
Sign in
Follow the sign-in page if Codex opens it. Otherwise run:
codex mcp login kinesisSign in to Kinesis, review the permissions and select the organizations the connection can reach. Complete organization SSO if prompted, approve, then return to Codex.
On a machine without a browser, use:
codex mcp login kinesis --no-browserOpen the printed authorization URL in a browser on another machine. After approval, paste the resulting callback URL into the waiting terminal when Codex asks for it. Keep that URL private.
API key from an environment variable
Create a scoped key in Account settings → API keys, and make KINESIS_API_KEY available to the process that launches Codex. For CI, use its secret store.
codex mcp add kinesis --url "https://mcp.kinesis.network/mcp" --bearer-token-env-var KINESIS_API_KEYCodex reads the variable at runtime. This command saves the variable's name, not the key, in its configuration. No OAuth login is needed for this option. The example uses the default compact catalog.
Configure the file directly
Instead of the CLI command, add this to ~/.codex/config.toml:
[mcp_servers.kinesis]
url = "https://mcp.kinesis.network/mcp"
# Uncomment for API-key authentication instead of OAuth:
# bearer_token_env_var = "KINESIS_API_KEY"For OAuth, leave the bearer setting commented and run codex mcp login kinesis. If the entry already exists, edit it rather than creating a duplicate table. Restart the client or start a new session after configuration changes.
These manual Codex setups use the standard Kinesis endpoint. The OpenAI MCP profile is a separate option for integrations that require its credential restrictions.
Connection options · Troubleshooting · Official MCP documentation
Was this helpful?
