Skip to main content

​
Choose a Codex Path

PathAuthenticationBest forStatus
Codex OAuth loginCOLA Cloud OAuth through WorkOS/AuthKitInteractive Codex CLI or IDE setupPreferred when available
Codex API-key Bearer authCOLA Cloud API key in AuthorizationNon-interactive setup, CI, and fallback workflowsSupported
COLA Cloud’s MCP server advertises OAuth discovery for connector clients. Codex also supports Bearer-token auth for streamable HTTP MCP servers.

​
Codex with OAuth

Add the COLA Cloud remote MCP server to your Codex config: 
[mcp_servers.colacloud]
url = "https://mcp.colacloud.us/mcp"
Then start the OAuth flow: 
codex mcp login colacloud
Complete the COLA Cloud sign-in in the browser. After login, use /mcp in the Codex UI to confirm the server is connected, then ask Codex to use COLA Cloud.

​
Codex with API-Key Bearer Auth

Create a COLA Cloud API key in Dashboard > API Keys, then configure Codex to read it from your environment: 
[mcp_servers.colacloud]
url = "https://mcp.colacloud.us/mcp"
bearer_token_env_var = "COLA_API_KEY"
Start Codex from a shell that has the key available: 
export COLA_API_KEY=cola_xxxx
codex
Use prompts like:
  • “Use COLA Cloud to find recent bourbon approvals from Kentucky.”
  • “Fetch details for the most relevant COLA records and include links.”
  • “Search permittees in New York matching importer.”

​
Troubleshooting

SymptomWhat to check
codex mcp login colacloud is not availableUse API-key Bearer auth for that Codex version or surface.
OAuth login succeeds but tool calls fail with oauth_connection_requiredThe OAuth subject is not linked to an active COLA Cloud account. Contact help@colacloud.us.
Tools do not appearConfirm the config table is [mcp_servers.colacloud], the URL is https://mcp.colacloud.us/mcp, and the server is enabled in /mcp.
API-key setup failsConfirm COLA_API_KEY is exported in the same shell that starts Codex and that the value starts with cola_.