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 flow. 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.
AuthenticationOAuth 2.0Hosted Om MCP expects the client’s remote-MCP OAuth flow rather than manual API-key headers.
Direct API authx-api-key or Authorization: Bearer <OAuth access token>This applies to direct `/v2/*` API routes, not hosted MCP startup. Hosted Om MCP uses OAuth.

Common client-side settings

Codex add commandBash
codex mcp add omtx --url https://agents.omtx.ai/mcp
codex mcp login --scopes email omtx
Codex remote MCP configtoml
[mcp_servers.omtx]
url = "https://agents.omtx.ai/mcp"
  • Use codex mcp login --scopes email omtx after adding the server.
  • 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 client-managed OAuth login.

Recommended defaults

  • Use https://agents.omtx.ai/mcp as the server URL.
  • In Codex, add the server and then run codex mcp login --scopes email omtx.
  • In Claude Code, add the server and then use /mcp to authenticate.
  • 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