> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rippit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Codex

> Connect Rippit to Codex: CLI, ChatGPT desktop app, and IDE extension.

The Codex CLI, the ChatGPT desktop app, and the IDE extension share one MCP configuration at `~/.codex/config.toml`, so adding Rippit in any of them adds it to all three.

## Command line

Add the server to `~/.codex/config.toml`:

```toml theme={null}
[mcp_servers.rippit]
url = "https://mcp.rippit.com/mcp"
auth = "oauth"
```

Then sign in:

```sh theme={null}
codex mcp login rippit
```

Your browser opens to `app.rippit.com`. Sign in and approve the consent screen. Verify with `codex mcp list`.

Rippit has no static API token, so don't set `bearer_token_env_var` on the entry; a token override suppresses the OAuth flow.

## ChatGPT desktop app

The desktop app's coding view manages the same servers:

1. Open **Settings** and find the MCP servers pane (listed under **Connections** in recent versions).
2. Select **Add server**.
3. Enter a name and choose **Streamable HTTP**.
4. Enter `https://mcp.rippit.com/mcp`.
5. Save, then **Restart**.
6. Select **Authenticate** and complete sign-in in the browser.

Adding Rippit here does not make it available in ChatGPT conversations; see [ChatGPT Web / Desktop](/clients/chatgpt/admin) for that.

## Consent screen

Codex registers itself with Rippit automatically, so the consent screen describes the client as **unverified** with **self-reported** details. That is expected for automatically registered clients; see [Security](/security#client-registration).

## Next steps

* [What Rippit can do for AI assistants](/mcp-server/overview#what-rippit-can-do-for-ai-assistants)
* [Troubleshooting](/troubleshooting)