Onekgpd MCP Server

Most team communication work still happens through a UI a human drives. Onekgpd MCP MCP server moves it into the conversation instead. Natural language access to 1000 Genomes Project dataset, hosted online in Dnaerys variant store.

The short version

• real-time access to 138 044 723 unique variants and ~442 billion individual genotypes
• variant, sample and genotype selection based on coordinates, annotations, zygosity, population
• filtering by VEP (impact, biotype, feature type, variant class, consequences), ClinVar Clinical Significance (202502),
• annotated with VEP 115 / GENCODE 49
• GENCODE Primary set transcripts
• full annotation composition

The tools it exposes

The server publishes 7 tools. What each one is for:

• Email — mcp@dnaerys.org
• Component — Type
• DnaerysClient — Unit
• OneKGPdMCPServer — Unit
• Other — Unit
• Total — The Total tool exposed by this server
• Verification — The Verification tool exposed by this server

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Onekgpd MCP's toolset — Email, Component, DnaerysClient and 4 more — is a fair guide to whether it matches your workflow. It is maintained by dnaerys; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.