Om MCP Configuration Options

What you can configure in Claude, Codex, Cursor, VS Code, Copilot, Gemini, Grok, 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 MCP uses OAuth.

Pick your agent harness

Common client-side settings

Claude Code add commandBash
claude mcp add --transport http omtx https://agents.omtx.ai/mcp
Claude Code remote MCP configJSON
{
  "mcpServers": {
    "omtx": {
      "type": "http",
      "url": "https://agents.omtx.ai/mcp"
    }
  }
}
  • Use claude mcp add --transport http omtx https://agents.omtx.ai/mcp for the simplest CLI setup.
  • In Claude.ai, add a custom connector named Om and paste the same URL.
  • Restart Claude Code after adding the server, then use /mcp to authenticate.

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.
  • Complete the client OAuth flow. Om asks for email only.
  • Restart the client after any MCP config change.
  • Start by verifying om_status before moving into Diligence, Data Access, or Hub workflows.