Om MCP Overview
Pick your agent harness and connect the hosted Om MCP. Score proteins, start Discovery, and use Om tools from Claude, Codex, Cursor, VS Code, Copilot, Gemini, Grok, or another remote MCP client.
Om MCP is the hosted MCP interface for Om. Pick the agent you already use,
add https://agents.omtx.ai/mcp, complete the client OAuth flow, and keep
Om tools in the same session.
Pick your agent harness to use Om
Claude
Claude.ai, Claude Desktop, and Claude Code.
- Verified
- Custom connector or claude mcp add
Codex
ChatGPT Developer mode plugin and the Codex CLI.
- Verified
- Email-only OAuth
Cursor
Add the hosted URL in .cursor/mcp.json and connect from Tools & MCP.
- Standard MCP config
- Cursor desktop
VS Code
Add a remote HTTP server in .vscode/mcp.json.
- Standard MCP config
- Complete OAuth when VS Code prompts
GitHub Copilot
Add the hosted server with the Copilot CLI, then authenticate from /mcp.
- Standard MCP config
- copilot mcp add
Gemini CLI
Add the hosted HTTP server, then run /mcp auth omtx.
- Standard MCP config
- gemini mcp add
Grok
Add the hosted Om MCP to Grok, then complete OAuth on first use.
- Standard MCP config
- grok mcp add
Other MCP clients
Any remote HTTP MCP client that can complete browser OAuth.
- Same hosted URL
- Use the Om API if the client cannot do OAuth
Setup in four steps
Pick your agent
Use Claude, Codex, Cursor, VS Code, Copilot, Gemini, Grok, or another remote MCP client.
Add the hosted Om MCP
Point the client at https://agents.omtx.ai/mcp.
Authenticate with OAuth
Complete the client’s browser login. Om asks for email only.
Restart and verify
Ask for om_status, pricing_get, or credits_get 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. |
Verified versus standard MCP config
Claude and Codex are the Om-tested login paths. Cursor desktop, VS Code, Copilot, Gemini, Grok, and other remote MCP clients use the same hosted URL. Cursor on the web and Cursor Agents use a hosted callback Om has not enabled yet. If a client cannot complete browser OAuth, use the Om API with an API key.
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.