Om MCP Available Tools
The hosted Om MCP exposes LULA scoring, proteome scoring, residue maps, fine-tunes, Discovery Launch, Hub, Diligence, molecule ordering, and wallet tools through one remote MCP server.
Om MCP gives Claude, Codex, Cursor, VS Code, Copilot, Gemini, Grok, and other OAuth-capable MCP clients a direct tool surface over Om. You do not need to memorize every tool name to use it well, but it helps to know how the tool families are organized and what kinds of questions each family can answer.
Tool families
| Family | What it does | Best for | Representative tools |
|---|---|---|---|
| LULA scoring | Scores a protein against Om Accessible Space or uploaded SMILES, including hotspot residue maps. | Rank orderable molecules for one target | lula2_score, lula1_score, lula2_residue_map, jobs_wait, jobs_get_top_scored_molecules |
| Proteome scoring | Scores one SMILES across an uploaded protein FASTA panel. | Off-target / selectivity of a single molecule | artifacts_upload_bytes, lula2_proteome_score, lula1_proteome_score |
| Molecule orders | Retrieves Om Accessible Space rows or a complete Om 50 export, then quotes and places Wallet Credits-funded physical molecule shipments. | Local Om 50 integration or after LULA hits are selected | molecule_accessible_space, molecule_accessible_space_export, molecule_fulfillment_pricing, molecule_fulfillment_order, molecule_fulfillment_order_status |
| Fine-tune and rescore | Fine-tunes hosted LULA on labeled pairs, then scores with the derived checkpoint. | Customer assay labels back into ranking | lula2_finetune, lula1_finetune, finetuned_derived_models_list, lula2_score |
| Discovery Launch | Quotes and creates the same Discovery program as the website, protein sequence plus N molecules from Accessible Space with AS-MS included. | Binder and non-binder validation data in weeks | discovery_launch_quote, discovery_launch_order, discovery_launch_get, credits_get |
| Hub | Launches active structure, docking, and design models. | Boltz-2 and other Hub jobs from the same session | hub_models_catalog, hub_boltz2, hub_boltzgen, hub_chai1, hub_openfold3, hub_diffdock, hub_submit |
| Diligence | Searches, gathers, crawls, synthesizes, and deepens target research. | Learn more about a target after scoring | diligence_search, diligence_gather, diligence_crawl, diligence_deep_diligence, diligence_synthesize_report |
| Data Access | Shows Generated Data available to your account and returns bounded ranked molecule rows or binder and non-binder export URLs for a protein. | ML workflows, data review, candidate prioritization | datasets_catalog, datasets_generated_protein_uuids, binders_get_ranked_molecules, binders_get_shards, binders_urls |
| Jobs | Tracks asynchronous work, waits on completion, exports results, and retrieves artifacts. | Operational workflows and job orchestration | jobs_history, jobs_status, jobs_wait, jobs_export_json, jobs_get_artifact_url |
| Artifacts | Uploads files, creates signed upload URLs, finalizes uploads, and resolves artifact metadata. | Hub inputs, FASTA panels, labeled CSVs | artifacts_upload_bytes, artifacts_create_upload_url, artifacts_finalize_upload, artifacts_get |
| System | Checks health, pricing, Wallet Credits, account profile state, and explicit wallet funding. | Hello World and inspecting account context | om_status, pricing_get, credits_get, users_profile, wallet_topup |
Natural-language asks that map well to Om MCP
Research and diligence
Ask natural questions about targets, mechanisms, competitors, or pathways.
- “Search KRAS and summarize the therapeutic strategy.”
- “Run deep diligence on KEAP1 resistance.”
- “Gather the strongest evidence for EGFR resistance mechanisms.”
Generated Data retrieval
Ask for account-owned Generated Data, bounded ranked molecule rows, or binder and non-binder exports for a specific protein UUID.
- “What Generated Data can I access in Data Access?”
- “Give me molecular binders for this protein UUID.”
- “Show the top 5 binder molecules across the full Generated Data snapshot.”
- “Show me non-binders too so I can compare the Generated Data.”
Jobs and artifacts
Ask the client to launch work, wait on it, and return the result or the artifact URLs.
- “Launch this workflow and wait until it completes.”
- “Export the result as JSON.”
- “Get the signed artifact URL for the output.”
Hub execution
Launch broad public Hub models from the same session where you did the research.
- “Launch a Hub workflow for this target.”
- “Use the uploaded artifact in the next run.”
- “Track the job until it finishes.”
Discovery video requests
Request an Om discovery music video from an MCP client with structured creative inputs.
- “Submit a discovery video request for this target.”
- “Use this music prompt and visual prompt.”
- “List my submitted video requests.”
Wallet funding
Add Wallet Credits after the user approves the exact amount and payment mode.
- “Check my Wallet Credits before launching this job.”
- “Ask me before adding $125 by saved card.”
- “Create an invoice for a larger Wallet Credits deposit.”
Notes on tool names
- Most users should start with natural-language asks and let the MCP client choose the tool.
- Some tool names remain transport-oriented because they mirror the canonical Om API surface.
- Customer-facing docs should describe outcomes in plain language, even when the underlying tool returns signed Generated Data export URLs or job IDs.
- If you need strict orchestration or exact payload control, move from MCP into the direct API.