Skip to main content
Glama
gnomAD MCP Server

gnomAD MCP Server

by shukwong

gnomAD MCP Server

A Model Context Protocol (MCP) server that provides access to the gnomAD (Genome Aggregation Database) GraphQL API. This server enables AI assistants to query genetic variant data, gene constraints, and population genetics information from gnomAD.

Features

  • ๐Ÿงฌ Gene Information: Search and retrieve detailed gene data including constraint scores

  • ๐Ÿ”ฌ Variant Analysis: Query specific variants and their population frequencies

  • ๐Ÿ“Š Population Genetics: Access allele frequencies across different populations

  • ๐Ÿงฎ Constraint Scores: Get pLI, LOEUF, and other constraint metrics

  • ๐Ÿ” Region Queries: Find variants within specific genomic regions

  • ๐Ÿงช Transcript Data: Access transcript-specific information and constraints

  • ๐Ÿ“ˆ Coverage Data: Retrieve sequencing coverage statistics

  • ๐Ÿ”„ Structural Variants: Query structural variant data

  • ๐Ÿงฒ Mitochondrial Variants: Access mitochondrial genome variants

Related MCP server: Open Targets Platform MCP

Installation

Prerequisites

  • Node.js 18 or higher

  • npm or yarn

Install from source

git clone https://github.com/yourusername/gnomad-mcp-server.git
cd gnomad-mcp-server
npm install
npm run build

Configuration

Claude Desktop

Add to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "gnomad": {
      "command": "node",
      "args": ["/path/to/gnomad-mcp-server/dist/index.js"]
    }
  }
}

With MCP CLI

npx @modelcontextprotocol/cli gnomad-mcp-server

Available Tools

1. search

Search for genes, variants, or regions in gnomAD.

Parameters:

  • query (required): Search query (gene symbol, gene ID, variant ID, rsID)

  • reference_genome: Reference genome (GRCh37 or GRCh38, default: GRCh38)

  • dataset: Dataset ID (gnomad_r4, gnomad_r3, gnomad_r2_1, etc., default: gnomad_r4)

Example:

{
  "query": "TP53",
  "reference_genome": "GRCh38"
}

2. get_gene

Get detailed information about a gene including constraint scores.

Parameters:

  • gene_id: Ensembl gene ID (e.g., ENSG00000141510)

  • gene_symbol: Gene symbol (e.g., TP53)

  • reference_genome: Reference genome (default: GRCh38)

Example:

{
  "gene_symbol": "BRCA1",
  "reference_genome": "GRCh38"
}

3. get_variant

Get detailed information about a specific variant.

Parameters:

  • variant_id (required): Variant ID in format: chr-pos-ref-alt (e

Available Tools

9 tools
get_coverageC

Get coverage information for a gene

Inputs: gene_id, gene_symbol, dataset, reference_genome.

get_geneC

Get detailed information about a gene including constraint scores

Inputs: gene_id, gene_symbol, reference_genome.

get_mitochondrial_variantsC

Get mitochondrial variants

Inputs: dataset.

get_region_variantsC

Get variants in a specific genomic region

Inputs: chrom (required), start (required), stop (required), dataset, +1 more.

get_structural_variantsC

Get structural variants in a genomic region

Inputs: chrom (required), start (required), stop (required), dataset, +1 more.

get_transcriptC

Get information about a specific transcript

Inputs: transcript_id (required), reference_genome.

get_variantC

Get detailed information about a specific variant

Inputs: variant_id (required), dataset.

get_variants_in_geneC

Get all variants in a specific gene

Inputs: gene_id, gene_symbol, dataset, reference_genome.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    B3.1/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific genomic entities (e.g., genes, variants, regions), but some overlap exists between 'get_variants_in_gene' and 'get_region_variants' which could cause confusion when querying gene regions. The descriptions help clarify, but the boundaries aren't perfectly clear.

    Naming Consistency5/5

    All tool names follow a consistent 'verb_noun' pattern with 'get_' or 'search' prefixes, using snake_case uniformly. This predictability makes it easy for agents to understand and select tools without naming confusion.

    Tool Count5/5

    With 9 tools, this server is well-scoped for querying genomic data from gnomAD. Each tool serves a specific purpose (e.g., coverage, genes, variants), and the count aligns with the domain's complexity without being overwhelming or insufficient.

    Completeness4/5

    The toolset covers core query operations for genes, variants, transcripts, and regions, with a general search function. Minor gaps exist, such as no explicit tools for filtering or aggregating results, but agents can work around this using the provided tools for most workflows.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with the Open Targets Platform API to search and retrieve comprehensive data about target-disease associations, drugs, genes, and drug discovery information through GraphQL queries.
      5
      37
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Provides a programmatic interface to the Genome Aggregation Database (gnomAD) API across versions v2.1.1, v3.1.2, and v4.1.0. It enables users to query gene metadata, variant information, population frequencies, and ClinVar data through a unified schema.
      12
      7
      Apache 2.0
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to query gene annotations, expression, pathways, variants, and more via the MyGene.info API, supporting batch operations and multiple biological data sources.
      26
      MIT