searchLABSCO SUMMARY
One grammar instead of thirty search habits.
The pivots are what make it more than a federated search: from a variant to the trials that mention it, from a drug to its adverse events, from a paper to what cites it — without rebuilding the filters each time you cross a source boundary.
What it is
A single binary with one grammar that reaches the biomedical databases that normally each have their own API, identifiers and search habits. The same tools are available to an agent over MCP as to a person at a shell.
What you get
- A grammar rather than a tool per source:
search <entity>for discovery,get <entity> <id> [sections]for a detail card,<entity> <helper> <id>for cross-entity pivots,enrichfor gene-set enrichment,batchfor parallel gets, andsearch allfor counts-first orientation across entities - Detail-card entities and the providers behind them: gene (MyGene.info, UniProt, Reactome, STRING, GTEx, Human Protein Atlas, DGIdb, ClinGen), variant (MyVariant.info, ClinVar, gnomAD v4, CIViC, OncoKB, cBioPortal, AlphaGenome), article, trial (ClinicalTrials.gov API v2 and NCI CTS), drug, disease, pathway, protein, diagnostic, adverse-event and pgx
- Search-only surfaces for gwas via the GWAS Catalog and phenotype via Monarch Initiative HPO semantic similarity
- Literature search that fans out across PubTator3 and Europe PMC, deduplicating PMID, PMCID and DOI identifiers, with an optional Semantic Scholar leg
- Cross-entity pivots that avoid rebuilding filters — variant to trials or articles, drug to adverse events or trials, disease to trials, drugs or articles, gene to trials, drugs, articles or pathways, protein to structures, and article to citations, references, recommendations or entities
- A paper trail from one known paper: citations, references, recommendations and extracted entities
- Local study analytics for downloaded cBioPortal-style datasets — query, cohort, survival, comparison and co-occurrence, with terminal, SVG and PNG charts
biomcp skill listfor shipped worked examples you can open as a workflow
Requirements
Install the CLI with uv tool install biomcp-cli, a one-line binary installer, Homebrew, Docker, or the PyPI package; the MCP server is the same package started with serve. Claude Code has a plugin, Claude Desktop an extension, and a remote HTTP server is available. Most commands work with no credentials at all. Optional keys raise limits or unlock enrichments: NCBI_API_KEY for PubTator, PubMed and PMC, S2_API_KEY for authenticated Semantic Scholar with a dedicated 1 req/sec quota instead of the shared 1 req/2sec pool, OPENFDA_API_KEY, NCI_API_KEY for NCI trial search, ONCOKB_TOKEN and ALPHAGENOME_API_KEY. References and recommendations can come back empty for paywalled papers because of publisher elision upstream.
Setup effort
One command — uv tool install biomcp-cli
USE CASES
Getting oriented on a gene and a disease together
Cross-entity search returns counts first, so you see where the evidence actually lives before drilling into any one source.
Working up a variant
The variant card pulls ClinVar, gnomAD population data, CIViC, OncoKB and cBioPortal into one place, and pivots straight into the trials and articles that mention it.
Finding trials for a patient profile
Trial search runs against ClinicalTrials.gov API v2 and the NCI CTS API, filterable by condition and recruiting status.
Following a paper outward
From one PMID, walk its citations, references, recommendations and the entities it mentions, turning a single paper into an evidence map.
Checking a drug's safety signal
Adverse events come from OpenFDA FAERS, MAUDE and recalls plus CDC WONDER VAERS, reachable as a pivot from the drug itself.
Analysing a cohort locally
Download a cBioPortal-style dataset and run cohort, survival, comparison and co-occurrence analyses with charts, without uploading anything.
7 tools
Listed in project docs. Your client may show a different list.
getvariant_normalize_carvariant_erepogene_cspecvariant_articlesbiomcpBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
biomcp on PATH
INSTALLATION
Connect your client
Server setup
uv tool install biomcp-cliMCP Clients
Claude Code
/plugin marketplace add genomoncology/biomcp
/plugin install biomcp@biomcpCodex
codex mcp add biomcp -- biomcp serveClaude Desktop
{
"mcpServers": {
"biomcp": {
"command": "biomcp",
"args": [
"serve"
]
}
}
}Any MCP client — Docker
docker run --rm -i ghcr.io/genomoncology/biomcp serve