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

# Configure Codex

> Connect Codex CLI, desktop, or IDE extension to the Suggix MCP server.

Configure Suggix as a remote MCP server in Codex to make workspace feedback context available in local Codex workflows.

## Add the API key

Set the API key as an environment variable:

```bash theme={null}
export SUGGIX_MCP_API_KEY="sgx_mcp_your_key"
```

For Codex desktop or IDE extension usage, add the same value to `~/.codex/.env` so the app can read it after restart:

```dotenv theme={null}
SUGGIX_MCP_API_KEY=sgx_mcp_your_key
```

## Add the remote MCP server

Run the following command once. Codex writes the MCP server configuration for you:

```bash theme={null}
codex mcp add suggix \
  --url https://mcp.suggix.com/mcp \
  --bearer-token-env-var SUGGIX_MCP_API_KEY
```

This configuration is stored in `~/.codex/config.toml`. Restart Codex after changing `config.toml` or `.env`.

## Verify the connection

In Codex CLI, run:

```bash theme={null}
codex mcp list
```

In the desktop app or IDE extension, start a new local task and ask Codex to use Suggix context, for example: `Review recent feedback for this feature and suggest the next implementation priority.`

<Warning>
  Keep the API key in `~/.codex/.env` or another secret store. Do not put a raw key directly in `config.toml` or a project file.
</Warning>

<Card title="Suggix MCP Overview" icon="plug" href="/mcp/overview">
  Learn how to create and revoke workspace MCP API keys.
</Card>