Connect Codex CLI to OrgX

Set it up

[mcp_servers.orgx]
url = "https://mcp.useorgx.com/mcp"

codex mcp login orgx

1. Edit the Codex configAdd an [mcp_servers.orgx] table with the OrgX MCP URL to ~/.codex/config.toml.
2. Sign inRun codex mcp login orgx and approve the workspace in the browser.
3. Confirm the sessionConfirm the workspace with orgx_bootstrap when it is discovered, then retrieve one linked record without writes. Status-only profiles use their permitted search or pulse tools instead.

What OrgX receives from Codex CLI

• Hosted MCP receives the tool arguments your client sends and returns tool results. These can include prompts, queries, decisions, artifact text or links, and workspace identifiers.
• OrgX also handles account, connection, authorization, and operational records needed to run the service. A browser-only trial is not offline or zero-data-retention.
• Local wizard and plugin setup can change client configuration and install capture hooks. Depending on the client and enabled capture, records can include session IDs, working-directory and transcript paths, timestamps, event and tool counts, summaries, and work context. Review the specific integration before installing it on a machine containing employer code.

Capture depth still differs by client today: the record is shared, but how much of a session reaches it depends on the client and the capture you enable. Read the data-handling summary