Om MCP Configuration Options

What you can configure in Codex, Claude Code, and other clients when connecting to the hosted Om MCP.

Om MCP is a hosted remote MCP server. In practice, the important configuration lives in your MCP client: the server URL and the auth mode. Unlike some hosted MCP products, Om MCP does not currently expose URL query parameters for read-only mode, project scoping, or feature-group selection.

Core connection settings

SettingValueNotes
MCP URLhttps://agents.omtx.ai/mcpHosted Om MCP endpoint.
Transportstreamable HTTPRemote MCP clients should connect over HTTPS.
Codex authAuthorization: Bearer $OM_API_KEYRecommended for Codex because the current remote MCP setup supports bearer-token auth directly.
Custom-header authx-api-key: $OM_API_KEYRecommended for Claude Code and other clients that support custom headers.

Common client-side settings

Codex add commandBash
codex mcp add omtx --url https://agents.omtx.ai/mcp --bearer-token-env-var OM_API_KEY
Codex remote MCP configtoml
[mcp_servers.omtx]
url = "https://agents.omtx.ai/mcp"
bearer_token_env_var = "OM_API_KEY"
  • Keep the API key in environment variables, not hard-coded in tracked files.
  • Add timeout overrides only if your local setup actually needs them.
  • For most users, the clean default config is enough.

What Om MCP does not currently expose

Om MCP does not currently document customer-facing URL query parameters for feature toggles, read-only mode, or project scoping. The public contract today is one hosted server plus Om API key authentication.

Recommended defaults

  • Use https://agents.omtx.ai/mcp as the server URL.
  • In Codex, use Authorization: Bearer $OM_API_KEY via bearer_token_env_var = "OM_API_KEY".
  • In Claude Code and other header-capable clients, use x-api-key: $OM_API_KEY.
  • Restart the client after any MCP config change.
  • Start by verifying om_status before moving into Diligence, Data Access, or Hub workflows.
QuickstartAuth & SafetySecurity Risks