findVariantsLABSCO SUMMARY
The compute happens at the store, not in the model.
Burden scoring, AlphaMissense averaging and kinship are tools rather than something an agent assembles from raw genotype dumps — which is what makes questions spanning a whole cohort answerable at all. Two deliberate choices show the same instinct: HGVSp is restricted to canonical transcripts specifically to reduce what the model has to hold, and the population tools exist so cohort structure can be established before variants are pulled. The example prompts in the README are unusually demanding, and they are the honest indication of what this is for.
What it is
A remote MCP service over the 1000 Genomes Project dataset held in the Dnaerys variant store: 3202 samples sequenced and aligned by the New York Genome Center, 2504 unrelated from the phase three panel plus 698 from 602 family trios. Variants come annotated by VEP 115 against GENCODE 49, with ClinVar clinical significance, gnomAD frequencies and AlphaMissense scores and classes.
What you get
- Variant and genotype selection —
findVariantsandfindVariantsInSamples, filtered by coordinates, annotations, zygosity and population - Sample-side queries:
findSamples,findSamplesHomozygousReference,findSamplesByPopulation,getSampleMetadata - Cohort computations run server-side —
computeAlphaMissenseAvgandcomputeVariantBurden, plusgetKinshipDegreefor relatedness - Population reference data through
listPopulations,listSuperpopulations,getPopulationStatsandgetSuperpopulationSummary getDatasetInfofor what the store actually contains- Returned variants carry HGVSp annotations restricted to canonical transcripts, gnomAD exome and genome frequencies, AlphaMissense scores and cohort-wide statistics; samples carry family id, gender, parental ids, relationship, children, population, superpopulation and the phase three indicator
Requirements
Nothing — the hosted service is at https://db.dnaerys.org/mcp over Streamable HTTP, with no authentication and no user data collected. Running it yourself needs JRE 21 and a Maven build producing onekgpd-mcp-runner.jar as an uber-jar; the dev profile enables both stdio and HTTP transports, with HTTP on port 9000. Claude Desktop should use the stdio route against the local jar — the README notes it will not work against the local HTTP option. Apache 2.0.
Setup effort
Build from source — git clone https://github.com/dnaerys/OneKGPd-MCP.git
USE CASES
Finding who in the cohort carries a variant
Query by coordinates or by gene annotation, filter on zygosity and population, and get the samples alongside the variant records.
Scoring pathogenic burden across a gene set
Compute variant burden and average AlphaMissense scores server-side rather than pulling genotypes and aggregating them yourself.
Controlling for population structure
List the populations and superpopulations and read their statistics before interpreting an allele frequency.
Working with the family trios
Pull sample metadata with parental ids and relationships, and check relatedness where it matters.
Establishing a reference set
Find the samples that are homozygous reference at your loci, to compare against the carriers.
14 tools
Listed in project docs. Your client may show a different list.
findVariantsInSamplesfindSamplesfindSamplesHomozygousReferencegetDatasetInfogetKinshipDegreecomputeAlphaMissenseAvgcomputeVariantBurdenlistPopulationslistSuperpopulationsgetPopulationStatsgetSuperpopulationSummarygetSampleMetadatafindSamplesByPopulationBEFORE YOU INSTALL
What to know first
Tools you get
14 tools named in the project's documentation.
Requires
JDK 21 (to build; the jar runs on Java 21)
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
Setup
git clone https://github.com/dnaerys/OneKGPd-MCP.git
cd OneKGPd-MCP
./mvnw clean package -DskipTests -Dquarkus.package.jar.type=uber-jarThe jar is written to target/onekgpd-mcp-runner.jar and includes all dependencies
Hosted endpoint
https://db.dnaerys.org/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Claude Desktop
{
"mcpServers": {
"OneKGPd": {
"command": "java",
"args": [
"-Dquarkus.profile=dev",
"-jar",
"<YOUR_FULL_PATH>/onekgpd-mcp-runner.jar"
]
}
}
}Any MCP client — remote HTTP
{
"mcpServers": {
"onekgpd-mcp": {
"url": "https://db.dnaerys.org/mcp"
}
}
}Any MCP client — Local HTTP
Start the server locally and keep it running
Both stdio and HTTP transports are on with the dev profile; HTTP listens on port 9000.
java -Dquarkus.profile=dev -jar <YOUR_FULL_PATH>/onekgpd-mcp-runner.jarThen add this endpoint to a client that connects over HTTP
<YOUR_FULL_PATH> is the target folder of your clone. Claude Desktop does not work with this localhost URL; use the stdio block for it.
http://localhost:9000/mcp