Om MCP Overview
Connect Codex, Claude Code, and other OAuth-capable MCP clients to the hosted Om MCP.
Om MCP is the hosted MCP interface for Om. Add it to Codex, Claude Code, or another OAuth-capable MCP client, authenticate with your client’s built-in OAuth flow, and use Om tools directly from the same session.
Setup in four steps
Use an OAuth-capable MCP client
Codex and Claude Code can authenticate to the hosted Om MCP through their built-in remote-MCP OAuth flows.
Codex or Claude CodeAdd the hosted Om MCP
Point your MCP client at the hosted Om MCP endpoint.
Authenticate with OAuth
Add the server first, then complete the client’s OAuth login flow for the hosted Om MCP.
Restart and verify
Ask for `om_status`, `pricing_get`, or `datasets_catalog` to confirm the server is attached.
Hosted server
| Setting | Value | Notes |
|---|---|---|
| MCP URL | https://agents.omtx.ai/mcp | Hosted Om MCP endpoint for remote MCP clients. |
| Transport | streamable HTTP | MCP clients should connect over HTTPS to the /mcp route. |
| Authentication | OAuth 2.0 | Hosted Om MCP expects the client’s remote-MCP OAuth flow rather than manual API-key headers. |
| Direct API auth | x-api-key or Authorization: Bearer <OAuth access token> | Direct `/v2/*` API routes still support API-key auth as the canonical external path. Hosted MCP startup uses OAuth. |
Add Om MCP to your client
codex mcp add omtx --url https://agents.omtx.ai/mcp
codex mcp login --scopes email omtx[mcp_servers.omtx]
url = "https://agents.omtx.ai/mcp"Diligence
Search, gather, crawl, synthesize, and run deep diligence from the same session.
- Fast target triage
- Claim-backed research workflows
- Citation-oriented outputs
Data Access
Find Generated Data available to your account and retrieve binder and non-binder exports for a protein.
- Account-scoped data discovery
- Signed binder and non-binder exports
- Model-ready Generated Data pulls
Jobs + Artifacts
Launch work, wait on completion, export results, and retrieve artifacts without leaving the session.
- Polling and wait helpers
- Artifact upload and finalize
- Signed download URLs
Hub
Launch supported model workflows and inspect execution state directly.
- Submit runs
- Track job progress
- Pull outputs into downstream work
System
Check health, pricing, profile, and Wallet Credits from the same client session.
- om_status
- pricing_get
- credits_get
- users_profile
Good first prompts
- Run
om_statusto verify the MCP is attached. - Run
pricing_getto inspect the current pricing manifest. - Ask Om MCP which Generated Data entries are available in Data Access.
- Run
diligence_searchordiligence_gatheron a target you already care about.
Typical MCP workflow
Ask the question
Start with a target, protein UUID, job goal, or workflow question inside your MCP client.
Use Om tools directly
Run Diligence, Data Access, Jobs, Artifacts, or Hub tools without building request glue first.
Keep the result in-session
Let the next step use the returned evidence, data export URLs, job IDs, or artifact URLs immediately.
Move into the API when needed
Use the direct API only when you need orchestration beyond the MCP session.
Security and approval
Hosted Om MCP is an authenticated OAuth tool surface. Keep manual tool approval on in your MCP client, authorize only the account/workspace you intend to use, and treat the connected session like live account access.