Skip to main content

Connect Rshift MCP in Codex

B
Written by Binbin Shen

Connect Rshift MCP in Codex

Codex can call Rshift workspace tools through an MCP server. This is useful when Codex needs Rshift brand context and tools while working on code, documentation, or operating tasks.

Before you start

  1. Enable MCP from the Rshift workspace AI page.

  2. Copy the MCP URL.

  3. Copy the full MCP key.

  4. Confirm that your Codex environment supports MCP server configuration.

Add the server

Codex stores MCP settings in config.toml. The default location is ~/.codex/config.toml; trusted projects can also use .codex/config.toml.

Recommended: keep the key in an environment variable and let Codex read it from there:

export RSHIFT_MCP_KEY="<MCP_KEY>"

Then add this to config.toml:

[mcp_servers.rshift]
url = "https://mcp.rshift.com/<workspace>/"
bearer_token_env_var = "RSHIFT_MCP_KEY"

If you must use a static header, http_headers also works, but do not commit real keys:

[mcp_servers.rshift]
url = "https://mcp.rshift.com/<workspace>/"
http_headers = { "Authorization" = "Bearer <MCP_KEY>" }

Verify the connection

  1. Reopen your Codex CLI / IDE session.

  2. In the Codex TUI, run /mcp and confirm that the rshift server is available.

  3. Test with a read-only tool first.

Common issues

  • Invalid config: confirm that you are editing config.toml with [mcp_servers.rshift], not JSON.

  • Authorization fails: confirm that RSHIFT_MCP_KEY exists and contains the key itself, without the Bearer prefix.

  • Tools are not visible: confirm that MCP is enabled and included in the workspace plan.

  • Config changes do not apply: restart the Codex session, or run codex mcp --help to inspect the MCP commands supported by your CLI.

Security

Do not put MCP keys in shared prompts, public issues, or repositories. For troubleshooting, describe the error code and config shape without sending the plaintext key.

Did this answer your question?