Live on Product Hunt Intraface launched today. Less steering, more vacations. See the launch
Start for free

Connect Codex to Intraface

Run codex mcp add intraface --url https://app.intraface.cc/mcp in your terminal. Codex opens your browser straight away; sign in to Intraface and click Allow. The server is saved in ~/.codex/config.toml, so the Codex IDE extension can use it too. From then on Codex can pull a shared board, edit it and publish a new version.

Part of Integrations: how to connect each coding agent to a shared Intraface board.

Set it up

  1. Add Intraface to Codex. Your browser opens on app.intraface.cc.

    codex mcp add intraface --url https://app.intraface.cc/mcp
  2. Sign in and click Allow. The terminal says you're logged in.

  3. Give Codex a board link and let it work.

    Read <board link> and follow its collab.md.

    It pulls the board, edits it on your machine and publishes a new version.

Option A: codex mcp add

One line in your terminal:

codex mcp add intraface --url https://app.intraface.cc/mcp

Codex saves the server and opens your browser on app.intraface.cc right away. Sign in, click Allow, and the terminal tells you you're logged in. Run codex mcp list to check: the intraface row shows OAuth as its auth.

The entry lives in ~/.codex/config.toml and is short enough to write by hand:

[mcp_servers.intraface]
url = "https://app.intraface.cc/mcp"

To set Intraface up for a whole repository, put the same table in .codex/config.toml at its root. Codex reads that file once you trust the project.

Option B: a token for headless runs

On a machine with no browser, use an Intraface token instead. Create one in the Intraface app under Settings, then Agents, and copy it when it's shown. Export it in your shell profile as INTRAFACE_TOKEN, then point Codex at the variable:

[mcp_servers.intraface]
url = "https://app.intraface.cc/mcp"
bearer_token_env_var = "INTRAFACE_TOKEN"

The token stays in your environment, never in the config file.

What works once you're connected

Hand Codex a board and say: "Read and follow its collab.md." It reads the board's house rules and open comments, pulls the latest files, edits them on your machine and publishes a new version. It can also compare two versions, reply to comments and resolve them.

Publishes go in one at a time, so nobody's work is overwritten. If a teammate changed the same file first, Codex pulls the new version and redoes its edit.

Troubleshooting

  • Codex asks before every tool call. Set default_tools_approval_mode = "writes" in the intraface table so it only asks before tools that change something.
  • The server is missing from codex mcp list. A project's .codex/config.toml only counts once you trust the project. Trust it, or move the table to ~/.codex/config.toml.
  • Calls time out on a large board. Raise tool_timeout_sec in the intraface table; the default is 60 seconds.
  • Signed out. Run codex mcp login intraface to sign in again.

FAQ

Do I need to run codex mcp login after adding Intraface to Codex?
Not the first time. Adding the server starts the sign-in on its own. Keep codex mcp login intraface for later, for example after you revoke the agent in the Intraface app and want to connect again.
Can my team share one Codex MCP config for Intraface?
Yes. Put the [mcp_servers.intraface] table in .codex/config.toml at the repository root. Codex reads it in projects you trust, and each person signs in with their own account, so no token ends up in the file.
Does the Codex IDE extension see the Intraface server too?
Yes. The Codex IDE extension reads the same ~/.codex/config.toml, so connecting once from the terminal covers it as well.

Stop sending HTMLover Slack.

Create an account in a minute, connect your coding agent, and make your first board.