Skip to content
Kyno Docs

Connect Codex

Codex can connect directly to Kyno’s remote MCP server. The Codex CLI, IDE extension, and desktop app share the same MCP configuration on the same machine.

Add Kyno

Section titled “Add Kyno”

Run this in a terminal:

Terminal window
codex mcp add kyno --url https://console.kyno.work/mcp
codex mcp login kyno

The login command opens a browser. Continue with Google or an email magic link and authorize the connection.

Check the connection:

Terminal window
codex mcp list

You can also type /mcp inside Codex to see connected servers.

Deploy your first app

Section titled “Deploy your first app”

Open Codex in the project directory and ask:

Inspect this project, prepare it for Kyno, deploy it, and share it with person@example.com. Do not upload any .env file. Use variables for non-sensitive settings and secrets for credentials.

Codex should inspect the project, add a root Dockerfile if one is missing, and call Kyno’s deployment tools.

Important: Do not paste secret values into your prompt or commit them to source. Keep them in a local environment file so Codex can pass them to Kyno as write-only secrets.

Project-wide configuration

Section titled “Project-wide configuration”

Codex can also load Kyno from a trusted project’s .codex/config.toml:

[mcp_servers.kyno]
url = "https://console.kyno.work/mcp"

Run codex mcp login kyno once to complete OAuth. Use the CLI command above for personal setup; commit project configuration only when your team intentionally wants every Codex user in that repository to see the Kyno server.