Connect Codex

Codex talks to Rendley over an MCP server with a bearer token. First create the key in Rendley, then add the server in Codex.

Codex (desktop app)

In Rendley, open Settings, scroll to API Keys, and click + Create your first key.

Name the key (for example Codex) and click Create key.

Copy the key now. Rendley shows it once.

In Codex, click your avatar in the bottom-left, then Settings.

Under Integrations, select MCP servers, then click + Add server.

Fill in the form and click Save:

Name: Rendley
Transport: Streamable HTTP
URL: https://mcp.rendley.com/mcp
Headers: add a header with key Authorization and value Bearer YOUR_RENDLEY_API_KEY

In a new chat, type /mcp. You should see rendley listed as Authenticated (API key) and Enabled.

The Codex CLI uses ~/.codex/config.toml. Point it at an environment variable for your key:

[mcp_servers.rendley]
url = "https://mcp.rendley.com/mcp"
bearer_token_env_var = "RENDLEY_API_KEY"

Then export the key (add it to your shell profile so new sessions inherit it):

export RENDLEY_API_KEY="your_key_here"

Keeping the key in an env var means a rotated key just needs a new export, with no config edit.

Ask in the chat:

What can Rendley do here?

List my projects.

If Codex lists Rendley’s tools and your projects, you’re connected. From there, describe the video you want and Codex builds it and returns a link.

Codex returns 401. The bearer token is wrong or missing. In the desktop app, re-check the Authorization header. In the CLI, run echo $RENDLEY_API_KEY to make sure it’s exported in the shell that launched Codex.
rendley not listed under /mcp. Open Settings → MCP servers and confirm the server is saved and enabled.