Install Om MCP in Codex

Add the hosted Om MCP to Codex and authenticate with Codex OAuth login.

Codex supports remote HTTP MCP servers and stores those entries in ~/.codex/config.toml. For Om MCP, the cleanest supported setup is to point Codex at the hosted Om MCP endpoint and complete the MCP OAuth login flow after adding the server.

codex mcp addBash
codex mcp add omtx --url https://agents.omtx.ai/mcp
codex mcp login --scopes email omtx
~/.codex/config.tomltoml
[mcp_servers.omtx]
url = "https://agents.omtx.ai/mcp"

Why OAuth is shown here

Codex documents OAuth login for streamable HTTP MCP servers that support OAuth. Hosted Om MCP now follows that flow, so the documented path is: add the server first, then run codex mcp login --scopes email omtx. Codex currently requests additional OIDC scopes by default; requesting only email avoids the openid ID-token path until asymmetric Supabase signing is enabled.

What to do after restart

  1. Restart Codex so the new MCP server is loaded.
  2. Ask for om_status or pricing_get to confirm the server is attached.
  3. Move into a real workflow such as target search, Generated Data export retrieval, or job launch.

Good first prompts

  • Use Om MCP to search KRAS and summarize the therapeutic strategy.
  • List Generated Data entries available to my account.
  • Run deep diligence on KEAP1 resistance and show the strongest citations.
  • Launch a Hub workflow and tell me how to track the job.