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

# Codex

> Connect Codex (CLI or desktop app) to Modus over MCP.

Codex can use Modus as an MCP server from both the CLI and the desktop app.

<Frame>
  <img src="https://mintcdn.com/modus-c77f86cb/0t9CfZKMweBgcLaa/images/mcp/scope-codex.png?fit=max&auto=format&n=0t9CfZKMweBgcLaa&q=85&s=ae6651799d357a9233df5974cfff64ac" alt="Codex tab on a scope's MCP tab with the codex mcp add command for a single scope" width="418" height="408" data-path="images/mcp/scope-codex.png" />
</Frame>

## Codex CLI

The most focused setup is a single [scope](/guides/scopes). Open the scope's
**MCP** tab → **Codex** and copy its ready-made commands:

```bash theme={null}
codex mcp add modus-revenue-analyst --url https://mcp.getmodus.com/org/<org>/scope/<scopeId>
codex mcp login modus-revenue-analyst
```

`codex mcp login` opens the Modus sign-in in your browser — approve access and
choose your organization. To connect **all** of Modus instead, use the org-level
URL from **Account → MCP**:

```bash theme={null}
codex mcp add modus --url https://mcp.getmodus.com/modus?toolsets=context
codex mcp login modus
```

## Codex desktop app

Add Modus in the app's MCP settings, or directly in `~/.codex/config.toml` — use
a scope's URL (from its **MCP** tab) or the org-level URL:

```toml theme={null}
[mcp_servers.modus-revenue-analyst]
url = "https://mcp.getmodus.com/org/<org>/scope/<scopeId>"
```

Restart Codex; the first request triggers the OAuth sign-in.

## Using it

Ask org questions in natural language — Codex discovers your published scopes
and workflows through Modus's tools. Codex doesn't support MCP slash commands,
so name the scope you want in your question when it matters.

Need help? Contact us at [support@getmodus.com](mailto:support@getmodus.com).