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

# Codex

> Use OpenAI Codex with the FITsociety MCP server.

Use this guide when you want Codex to call FITsociety MCP tools from the Codex
CLI, IDE extension, or app.

## Prerequisites

Before connecting, make sure:

* your company has the `mcp` feature enabled
* a Manager or Admin coach has created an MCP grant (OAuth consent or a static
  MCP API key) for the access you need

See [Setup for Coaches](/mcp/setup-for-coaches) for how to enable the feature
and create a grant.

## Server URL

```text theme={null}
https://mcp.fitsociety.io/mcp/v1
```

## Add the server

Codex stores MCP server configuration in `config.toml`. User-level config lives
at `~/.codex/config.toml`; project-level config can live at `.codex/config.toml`
inside a trusted project.

Add:

```toml theme={null}
[mcp_servers.fitsociety]
url = "https://mcp.fitsociety.io/mcp/v1"
```

You can also use the Codex CLI:

```bash theme={null}
codex mcp add fitsociety --url https://mcp.fitsociety.io/mcp/v1
```

## Authentication

Prefer OAuth when Codex starts the remote MCP authorization flow. The flow sends
the coach to FITsociety, where they approve the company grant, modules, write
tools, and consent flags.

If your Codex environment is configured to use a static bearer credential, use a
company MCP API key generated by a Manager or Admin coach. Keep the key outside
the repository and provide it through your local MCP configuration or secret
manager.

## Verify

Ask Codex:

```text theme={null}
List the FITsociety MCP tools you can access.
```

The available tools should match the grant permissions. If no tools appear,
check that the grant is active, the company has MCP enabled, and the owner coach
is still an active Manager or Admin.