Connect Codex

Codex has no MCP directory, so connection is a one-time config edit. Once set up, Codex can read your meetings when you ask it to, which sends the meeting you choose to OpenAI. That is the point of it; it is never called private.

The connector is free and local: the desktop app serves an MCP endpoint on your machine, and Codex connects to it directly. No hosted relay, no account, no subscription.

Prerequisites

• Minutist desktop app installed and running (the endpoint is served by the app).
• Codex CLI installed on the same machine.

Add Minutist to Codex

1. Open your Codex config

   The config file lives at ~/.codex/config.toml on macOS and Linux, and at %USERPROFILE%\.codex\config.toml on Windows. Create it if it does not exist.

2. Paste the [mcp_servers] entry from the app

   The app’s connector settings pane shows the exact block for your local port and bearer token. It points at http://localhost:<port>; nothing leaves your machine until Codex reads a meeting and sends it to OpenAI.

3. Verify the connection

   Ask Codex something that requires reading a meeting, for example:

   codex "Summarise my last meeting in Minutist"

   Codex will call the local MCP server, which returns the meeting you named. If the command fails, check that the Minutist desktop app is running and that the port and token in config.toml match what the app shows.

Caution

Each request that references a meeting sends that meeting’s transcript and notes to OpenAI; Codex reads it locally and carries it to the provider. This is how the connector works; there is no version that keeps the content local while also letting Codex read it. If you need the content to stay on your machine, use Minutist’s local chat instead.

What Codex can do

Codex has access to the same 23 MCP-exposed tools the Claude connector uses (24 tools in total; one write tool, reprocess_meeting, is internal-only and not reachable over MCP). See MCP tool reference for the full list. Most tools are read-only; a small number allow reversible writes (for example, renaming a meeting or setting a speaker name). Codex cannot delete meetings or recordings.

Revoking access

Disable the connector (or regenerate its bearer token) in the app’s connector settings pane; either immediately cuts off every client using the old token. Then remove the [mcp_servers.minutist] block from config.toml.