Install Om MCP in Codex

Add the hosted Om MCP to Codex and authenticate with your Om API key.

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 pass your Om API key as a bearer token.

codex mcp addBash
codex mcp add om-mcp --url https://agents.omtx.ai/mcp --bearer-token-env-var OM_API_KEY
~/.codex/config.tomltoml
[mcp_servers.om-mcp]
url = "https://agents.omtx.ai/mcp"
bearer_token_env_var = "OM_API_KEY"

Why bearer auth is shown here

Om MCP accepts both x-api-key and `Authorization: Bearer <OM_API_KEY>`. Codex has first-class remote MCP bearer-token support, so this is the simplest path to document and the closest to the current official Codex MCP flow.

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, dataset export retrieval, or job launch.

Good first prompts

  • Use Om MCP to search KRAS and summarize the therapeutic strategy.
  • List available proteins in the Om dataset catalog.
  • Run deep diligence on KEAP1 resistance and show the strongest citations.
  • Launch a Hub workflow and tell me how to track the job.