Genomics MCP server
io.github.rewire-bio/genomics-mcp·v0.1.0Bounded genomic data from archives and indexed files, with versioned reference evidence.
0 stars
Reviews
Write oneNobody has reviewed Genomics MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Genomics MCP tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Genomics MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
Install Genomics MCP in Claude Code, Cursor or VS Code
claude mcp add genomics-mcp -- docker run -i --rm ghcr.io/rewire-bio/genomics-mcp:0.1.0
What the publisher says
From the Genomics MCP repository's README, as published. We do not edit it. Read it on GitHub
Genomics MCP
<!-- mcp-name: io.github.rewire-bio/genomics-mcp -->
An MCP server for finding genomic datasets, retrieving bounded data at a locus, and looking up versioned, source-attributed reference evidence. It runs on your machine. Research use only; no clinical verdicts.
Status: 0.1.0, release prepared, not yet published. All 23 tools are implemented and tested. The first release will be a GitHub release and a GHCR container image. Current publication state: docs/registry-ledger.md.
What it does
- Discovery: EGA, ENA, ENCODE, GEO and NCBI Datasets studies, datasets, samples, phenotypes (as the archive supplies them) and files.
- Genomics: reads, coverage, pileup, variants, sequence, features and signal from indexed BAM/CRAM, VCF/BCF, FASTA, BED/GFF3/GTF and bigWig/bigBed files on local disk, HTTPS or S3. EGA regions come through EGA's htsget.
- Transfers: bounded, resumable, checksummed downloads to a local workspace. Files are returned as paths, never as bytes in MCP text.
- Composition: inspectlocus and comparesamples across several files.
- Reference: HGNC, Ensembl, ClinVar (germline, somatic clinical impact and oncogenicity kept separate), gnomAD, UniProt, Open Targets, and optional AlphaGenome Atlas precomputed predictions with your own key.
Intervals are 0-based half-open with an explicit assembly. Nothing is lifted over silently. CRAM needs a reference whose MD5 matches the header. Default limits: 1 Mb region, 10,000 records, 1 MiB response, 30 s deadline, 100 MiB transfer.
Install
Full options, platform notes and Windows (WSL2/container): docs/install.md.
Container (linux/amd64)
After the release is published:
docker run --rm -i \
--mount type=bind,source="$HOME/genomics-data",target=/data,readonly \
--mount type=volume,source=genomics-mcp-work,target=/work \
ghcr.io/rewire-bio/genomics-mcp:0.1.0Only /data is readable as local input; /work holds downloads and indexes (bounded to 10 GiB).
Python (macOS, Linux)
Needs Python 3.12, uv, a C compiler, and libcurl and zlib development files. pyBigWig is built from source because the published Linux wheel has no remote-file support.
git clone https://github.com/rewire-bio/genomics-mcp
cd genomics-mcp
uv sync --locked --no-dev
uv run genomics-mcp --check-configUse
stdio (default)
{
"mcpServers": {
"genomics": {
"command": "uv",
"args": ["--directory", "/path/to/genomics-mcp", "run", "genomics-mcp"],
"env": { "GENOMICS_MCP_ALLOWED_ROOTS": "/path/to/your/data" }
}
}
}For the container, use "command": "docker" with the run arguments above.
Streamable HTTP
HTTP needs a bearer token of at least 32 characters and binds to 127.0.0.1 unless configured otherwise. There is no hosted service.
export GENOMICS_MCP_HTTP_TOKEN="$(python3 -c 'import secrets; print(secrets.token_urlsafe(32))')"
uv run genomics-mcp --transport http --port 8765
# endpoint: http://127.0.0.1:8765/mcp header: Authorization: Bearer $GENOMICS_MCP_HTTP_TOKENConfiguration
Copy config.example.toml and pass it with --config or GENOMICSMCPCONFIG. genomics-mcp --check-config prints a summary without secrets.
- Local files are readable only under paths.allowed_roots.
- Ambient cloud credentials (AWS_*, ~/.aws, instance metadata) are never used. For private S3 or MinIO, add a [storage.profiles.] entry that names the environment variables holding your keys.
- EGA controlled files need your own EGA account. GENOMICSMCPEGAPUBLICTEST_ACCOUNT=1 uses EGA's documented public test account.
- Values derived from files you have not marked public are sent to external APIs only when a call sets allowexternalannotation.
Tools
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Genomics MCP: common questions
- Is Genomics MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Genomics MCP safety report
- How do I install Genomics MCP?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Genomics MCP need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Genomics MCP maintained?
- The last commit was 40 days ago (2026-09-25). The latest release is v0.1.0.