Connect Codex
Add PacedMind's MCP server to Codex's configuration, for the Codex app and the Codex sessions you start yourself, check the connection, and update it after a new token.
Codex reads its MCP servers from its configuration file, ~/.codex/config.toml, which the Codex command-line tool and the Codex app share. Sessions PacedMind starts in a terminal bring their own connection to PacedMind, which replaces this entry for them, headers included, so they only send their own token. The Codex app, and Codex sessions you start yourself, need PacedMind's entry in that file.
With a PacedMind Cloud account
Connect Codex to PacedMind Cloud instead: it signs in with your account (codex mcp login pacedmind), and no token goes into config.toml. See Connect to PacedMind Cloud. This page is about the desktop app's own server, without an account.
With Connect in Settings
In Settings → MCP server, under Connect your agents, select Connect next to Codex and confirm. PacedMind adds the section below to config.toml, in place of an earlier pacedmind section or one under PacedMind's earlier name, organizer, and keeps the previous file as config.toml.pacedmind-backup (Connected Codex, its app included. New Codex sessions can use PacedMind.). Computers then shows Codex as Connected.
By hand
-
Open Settings → MCP server and, under Connect your agents, select Copy config next to Codex. It copies:
# ~/.codex/config.toml [mcp_servers.pacedmind] url = "http://127.0.0.1:4319/api/mcp" http_headers = { Authorization = "Bearer pm_..." } -
Open
config.tomlin the.codexfolder of your user profile, such asC:\Users\Anna\.codex\config.tomlon Windows or/Users/anna/.codex/config.tomlon macOS, and paste the section at its end, in place of an earlier[mcp_servers.pacedmind]or[mcp_servers.organizer]section. Create the file if it doesn't exist.
Keep the name pacedmind: PacedMind's skills and first messages refer to the server by that name. A section under the earlier name, organizer, still works, and Computers shows it as Old name; Connect replaces it.
The section holds the token itself, because the Codex app has no environment variable to read it from. Keep config.toml private. An older section with bearer_token_env_var = "ORGANIZER_TOKEN" works only where that variable is set, which isn't the case in the Codex app: replace it with the one above.
Check the connection
Start Codex, in the app or a terminal, and ask something that needs the planner, such as List my overdue tasks in PacedMind. Codex should call the pacedmind tools, such as get_overview or list_tasks. If it can't, see Troubleshooting.
With the agent skills installed in ~/.codex/skills, Codex also knows how to plan, triage and run project work with the tools.
After regenerating the token
A new token in Settings → MCP server disconnects Codex until its configuration has the new one: select Connect in Settings → MCP server again, or copy and paste the section again. Sessions PacedMind starts in a terminal pick up the new token on their own.
Remove the connection
Delete the [mcp_servers.pacedmind] section, or [mcp_servers.organizer] under the earlier name, from config.toml. An ORGANIZER_TOKEN variable set up for the older section isn't needed either: remove it from your user's environment variables on Windows, or its line in ~/.zshrc on macOS.
Connect Claude Code
Register PacedMind's MCP server in Claude Code, for the Claude app and the sessions you start yourself, check the connection, and update it after a new token.
Tool reference
Conventions shared by all 44 tools of PacedMind's MCP server (references, dates, statuses, clearing values, errors) and an index of every tool.