Codex

Give Codex the backlog it is coding against.

Atrix is an MCP server for OpenAI Codex. Run codex mcp add atrix --url https://atrix.dev/api/mcp, sign in, and Codex can read your issues, specs and pages, open and update work, and comment as it goes — within the scopes you approve and never beyond your own permissions.

7-day trial · card required · cancel anytime

terminal · codex mcp

Once connected

What Codex can do with Atrix

The tool names below are the ones Codex sees. Reading needs only the first connection; writing needs a write scope you approve.

  • Read the work first

    work_list_issues, work_get_issue and project_status give Codex the issue, its last comments and status history, and what else in the product is overdue or stuck.

  • Read the spec, not a summary

    search, pages_list and pages_get fetch the spec or requirements page behind an issue in full, so Codex works from what was agreed.

  • Open and update issues

    work_create_issue files the bug Codex found, with ifNotExists to avoid duplicates. work_update_issue, work_set_issue_status and work_comment_issue record progress.

Write notes back to pages

pages_append adds implementation or release notes to the end of a page, merging with anyone editing it rather than overwriting them.

Data

Scoped, audited, revocable

Atrix receives only the tool calls Codex makes, not your repository or your session. Each call is logged by tool, outcome and subject, never by contents.

What Atrix reads

  • Only what the granted read scopes cover: work, projects, pages, ideas, CRM, calendar and more
  • Deal values, hiring and people records only with both the scope and your permission
  • Never pay or compensation, under any scope

What Atrix writes

  • Nothing on the first connection, which asks only to read
  • With write scopes you approve: issues, comments, statuses, pages and other records
  • Feed posts only with the separately named feed.post scope

How to connect

Connect in three commands

For CI or a server without a browser, use a personal Atrix token: codex mcp add atrix --url https://atrix.dev/api/mcp --bearer-token-env-var ATRIX_TOKEN, with ATRIX_TOKEN set in the environment.

  • Add the server — Run codex mcp add atrix --url https://atrix.dev/api/mcp. The command carries no credential.
  • Sign in to Atrix — Run codex mcp login atrix if Codex has not started sign-in already. In the browser, pick the workspace and approve read access.
  • Check it — Run codex mcp list to see atrix in the list, or type /mcp inside a Codex session.
terminal · codex mcp

Plans

Codex works on every plan

Connecting is free on the Atrix side, and Codex's tool calls do not use Atrix AI runs.

  • Builder$39/mo

    Connect Codex with any scopes your role allows.

  • Studio$149/mo

    Every one of your 15 seats can connect their own Codex.

FAQ

Questions, answered

Does it work in the Codex IDE extension and app too?

Yes. As of October 2026, OpenAI documents that the Codex CLI, IDE extension and desktop app share one MCP configuration, so a server added once is available in each.

How does Codex get permission to write?

The first connection asks only to read. When Codex calls a write tool, Atrix answers 403 insufficient_scope naming the scope it needs, and you approve exactly that scope in the browser.

How do I use it in CI?

Create a personal Atrix token with only the scopes the job needs, store it as ATRIX_TOKEN, and add the server with --bearer-token-env-var ATRIX_TOKEN. Codex saves the variable's name, not the token.

Are there rate limits?

Yes: 120 calls and 30 writes a minute, per token. Over the limit, Atrix returns 429 with a Retry-After header in seconds.

Can Atrix see my code?

Only what Codex puts into a tool call, such as the text of a comment it writes. Atrix never reads your repository through this connection.

Let Codex read the ticket before it writes the code.

Connect it during the 7-day trial. The developers page has setup for every client.

7-day trial · card required · cancel anytime