About Genomics MCP
Genomics MCP is a local MCP server for computational biologists and researchers to discover public genomic datasets, read bounded regions, and query reference databases. It reports source and version provenance, but does not provide clinical interpretation or biological conclusions.
Key features
- 01Search public datasets
- 02Read bounded genomic regions
- 03Look up variants, genes, and proteins
- 04Budgeted file downloads
- 05Report sources and versions
Use cases
- 01Find data in EGA, ENA, ENCODE, and more
- 02Read regions from BAM or bigWig files
- 03Check variant and gene reference information
MCP support
As a local MCP server, it exposes tools and resources for data discovery, genomic reads, and reference lookups. It supports stdio or token-protected local Streamable HTTP.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEGenomics MCP
Let your AI assistant retrieve real genomic data and reference evidence, with the sources it came from.
Genomics MCP is a local Model Context Protocol server. An agent can use it to find public datasets and read a bounded region from archive, remote or local files. It can also look up variants and genes in public reference databases. Region queries use an explicit assembly and 0-based half-open coordinates. Where the format and server support range reads, a region is read without downloading the whole file. Whole-file downloads are a separate, budgeted step. Results report which sources were consulted (provenance and per-source status), with accessions, versions and retrieval times where the source provides them.
It is a research tool. It retrieves and reports data. It does not give clinical interpretation, call variants or draw biological conclusions.
Read the blog article: Genomics MCP: genomic data access for AI agents, including an agent case study at the BCL11A enhancer.
Who it is for
Computational biologists and researchers who want an agent to pull data from EGA, ENA, ENCODE, GEO, NCBI or their own indexed files without writing integration code. It also suits people building agents or evaluations who need real data with traceable sources. It does not generate benchmarks itself.
Example requests
Illustrative prompts; results depend on your client and model. Intervals are 0-based half-open (start included, end excluded); VCF-style variant positions are 1-based.
- "Show the reads from EGA file EGAF00007243773 (dataset EGAD00001003338) overlapping GRCh38 chr10:[10000, 10050)." Needs
GENOMICS_MCP_EGA_PUBLIC_TEST_ACCOUNT=1, EGA's documented public test account. - "What is the mean signal of ENCODE file ENCFF792QDS over GRCh38 chr1:[1000000, 1001000)?"
- "Check the reference base of GRCh38 variant 7-140753336-A-T against NCBI, then list its ClinVar records with germline, somatic and oncogenicity classifications kept separate."
- "Download the ENA FASTA for DQ285577.1 and show its first 30 bases."
- "Compare genotypes in chr1:[100000, 200000) across the two VCFs in my data folder."
Measured example
The ENCODE request above, run through a clean install on 2026-09-25 with live data:
- File: ENCODE ENCFF792QDS, GRCh38 bigWig, 1,413,106,336 bytes
- Interval: chr1:[1000000, 1001000)
- Result: exact mean 26.361254017233847, from HTTP range reads. The workspace held 0 bytes afterwards (nothing written to disk; network reads still happened).
Four other live demonstrations ran with the same install: an EGA test BAM region, an ENA sequence download, a reference check with ClinVar, and local MinIO. Commands and machine-readable results: docs/demos.md.
Agent case study: a Claude Code agent, limited to this server's tools, compares ENCODE DNase-seq signal at the BCL11A erythroid enhancer across 26 files, with a transcript and a model-free replay: examples/agent-case-study/.
Quickstart
Container (Linux x86_64 with Docker)
The image is linux/amd64. It is tested on Linux x86_64; Docker on macOS is untested. Create the data folder first; it is mounted read-only.
{
"mcpServers": {
"genomics": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"--mount", "type=bind,source=/path/to/your/data,target=/data,readonly",
"--mount", "type=volume,source=genomics-mcp-work,target=/work",
"ghcr.io/rewire-bio/genomics-mcp:0.1.0"
]
}
}
}
From source (macOS arm64, Linux x86_64)
Needs Python 3.12, uv, a C compiler, and libcurl and zlib development files (pyBigWig is built from source for remote-file support).
git clone https://github.com/rewire-bio/genomics-mcp
cd genomics-mcp && git checkout v0.1.0
uv sync --locked --no-dev
uv run --no-dev genomics-mcp --check-config
{
"mcpServers": {
"genomics": {
"command": "uv",
"args": ["--directory", "/path/to/genomics-mcp", "run", "--no-dev", "genomics-mcp"],
"env": { "GENOMICS_MCP_ALLOWED_ROOTS": "/path/to/your/data" }
}
}
}
There is no PyPI package yet. Wheel, Linux MCPB bundle, pinned uvx command, Windows (WSL2) and platform notes: docs/install.md.
Coverage
| Area | Sources and formats |
|---|---|
| Discovery | EGA, ENA (incl. SRA accessions), ENCODE, GEO, NCBI Datasets: studies, datasets, samples, phenotypes as supplied, files |
| Genomic data | BAM/CRAM, VCF/BCF, FASTA, BED/GFF3/GTF, bigWig/bigBed on local disk, HTTPS or S3; EGA regions via htsget |
| Transfers | Budgeted, resumable, checksummed downloads returned as local paths; optional SRA run to FASTQ with SRA Toolkit (unreleased) |
| Reference | HGNC, Ensembl, ClinVar, gnomAD, UniProt, Open Targets; optional AlphaGenome Atlas with your own key |
All 24 tools and the resources
| Group | Tools |
|---|---|
| Discovery | list_sources, search_datasets, describe_dataset, list_files, list_samples, get_sample_metadata |
| Transfers | fetch_file, get_transfer_status, cancel_transfer, convert_sra_run (optional, unreleased) |
| Genomics | get_reads, get_coverage, get_pileup, get_variants, get_sequence, get_features, get_signal |
| Composition | inspect_locus, compare_samples |
| Reference | resolve_identifier, normalize_variant, lookup_variant, lookup_gene, lookup_protein |
Resources: genomics://capabilities, genomics://status, genomics://schemas, genomics://schemas/{name}.
Defaults and safety
-
Limits: 1 Mb regions, 10,000 records, 1 MiB responses and a 30 s deadline; calls may lower these. Transfers are capped at 100 MiB unless a call sets a larger budget. Truncation is reported. Nothing is lifted over between assemblies.
-
Local only: stdio, or Streamable HTTP with a bearer token on 127.0.0.1. There is no hosted service. Local reads are limited to the folders you allow, and source files are never modified.
-
Credentials and egress: ambient AWS credentials are never used; private S3 and EGA need explicit configuration. Values from files not marked
publicgo to external APIs only when a call setsallow_external_annotation. -
Cache (unreleased; development checkout only, not in v0.1.0): a bounded in-memory cache reuses byte ranges of public HTTPS files marked
public(revalidated by ETag on every call) and public API responses. It is never used for private, signed or authenticated requests. Turn it off with[cache] enabled = false; restarting clears it. Details and measurements: performance. -
SRA Toolkit (unreleased; optional):
convert_sra_runturns a public SRR/ERR/DRR run into local FASTQ files with NCBI'sprefetchandfasterq-dump, as a budgeted, cancellable job. It is never started by discovery. ENA FASTQ files need no toolkit. Installation, container variant, limits and current verification status: SRA Toolkit.
Configuration: config.example.toml. Scope and known limits: PRD.md. Directory and PyPI status: publication ledger. Technical details: data access, archives, references, composition. Security: SECURITY.md.
Development
uv sync --locked
uv run ruff check . && uv run ruff format --check .
uv run pytest
Licence
MIT. See LICENSE. Data from each source is subject to that source's own terms.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.