Install Om MCP in other clients

Connect any remote HTTP MCP client to the hosted Om MCP. If the client cannot complete browser OAuth, use the Om API instead.

The hosted Om MCP is one URL. If your agent can connect to a remote HTTP MCP server and complete a browser OAuth login, point it at https://agents.omtx.ai/mcp. You do not need a local Om install or an API key in the MCP config.

Generic remote MCP configJSON
{
  "mcpServers": {
    "omtx": {
      "url": "https://agents.omtx.ai/mcp"
    }
  }
}

Additional client examples

OpenCodeJSON
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "omtx": {
      "type": "remote",
      "url": "https://agents.omtx.ai/mcp",
      "enabled": true
    }
  }
}
WarpJSON
{
  "mcpServers": {
    "omtx": {
      "url": "https://agents.omtx.ai/mcp"
    }
  }
}
GooseYAML
extensions:
  omtx:
    enabled: true
    name: Om
    type: streamable_http
    uri: https://agents.omtx.ai/mcp
    timeout: 300

If the client cannot do remote MCP OAuth

Hosted Om MCP uses OAuth, not API-key headers. If your client only supports static API keys, or cannot complete a browser login, use the Om API and SDK instead of the hosted MCP.

Email only

Om asks for email only. If the client requests openid, profile, or phone, cancel instead of approving.

Verify

  • Confirm the URL is exactly https://agents.omtx.ai/mcp.
  • Complete OAuth in the client, then restart if tools do not appear.
  • Ask for om_status before scoring, Discovery, or Hub launches.
API AuthenticationQuickstartTroubleshooting