Connect Codex to Edka

Connect Codex to your Edka organization and ask it about your infrastructure directly. Codex gets the same tools as the Claude integration, which lists them in full.

Read access covers organization details, clusters, apps, add-ons, deployments, databases, notifications, agents, and custom apps. Write access adds publishing and installing apps and creating and deleting Codex environments. Codex acts as you, with your Edka role and cluster permissions, in one organization. Responses leave out configuration values, environment variable values, and database credentials.

Connect from Codex CLI

Add the server:

codex mcp add edka --url https://api.edka.io/mcp/platform

Codex opens your browser. Sign in with your Edka account, keep or uncheck write access, and click Authorize. Edka tools are then available in Codex sessions.

To sign in again later, run:

codex mcp login edka

Choose read or write access

The consent screen lists read access as required and write access as an optional checkbox, checked by default. Uncheck it to connect with read access only. Codex then gets the read tools and none of the write tools.

A connection keeps the access you granted at sign-in. To change it, revoke Codex’s access as described under Removing access, then run codex mcp login edka and choose on the consent screen.

Organization scope

The connection is bound to the organization that is active when you authorize it. To connect a different organization, make it active in the Edka console, then run codex mcp login edka again.

Removing access

codex mcp remove edka

To revoke Codex’s access from Edka, open Settings > Security in the Edka console and select Revoke next to Codex under Authorized applications. Codex loses access on its next request, and connecting it again asks for your approval.

Edka checks organization membership on every request, so removing someone from the organization ends their connection right away.