hgnc-link
hgnc-link is a gene nomenclature server that grounds gene symbol and ID lookups in the HGNC dataset, enabling canonical resolution, cross-reference mapping, and gene family browsing. It is accessible via MCP or HTTP.
Resolve gene symbols/IDs (
resolve_symbol): Convert any gene symbol (current, previous/withdrawn, or alias) or HGNC ID into a canonical{hgnc_id, approved_symbol, match_type}— ambiguous aliases are flagged explicitly rather than silently collapsed.Batch resolve symbols (
resolve_symbols_batch): Resolve up to 200 gene symbols or HGNC IDs in a single call; individual misses never fail the entire batch.Get full gene records (
get_gene): Retrieve the complete HGNC record including name, status, locus group/type, genomic location, aliases, previous symbols, gene groups, and all cross-references.Search genes by free text (
search_genes): Relevance-ranked full-text search across gene symbols, names, aliases, and previous symbols.Get gene cross-references (
get_gene_cross_references): Retrieve external database identifiers (NCBI Gene, Ensembl, UniProt, RefSeq, OMIM, UCSC, CCDS, MGI, RGD, Orphanet, COSMIC, PubMed, etc.) with optional filtering by database.Reverse cross-reference lookup (
resolve_gene_by_xref): Find the HGNC gene(s) corresponding to an external database ID (e.g., an Ensembl ID or UniProt accession).Browse gene groups/families (
get_gene_group): List member genes of a HGNC gene group by numeric ID or name, with pagination support.Discover server capabilities (
get_server_capabilities): Retrieve the full tool list with signatures, workflows, response modes, error taxonomy, vocabularies, and the cross-reference database catalogue.Check data freshness/diagnostics (
get_hgnc_diagnostics): Inspect the local HGNC index status, release date, gene/withdrawn counts, schema version, and build time.Control response verbosity via
response_mode(minimal, compact, standard, full) on most tools.Chain commands via
_meta.next_commandsfor workflow automation and federation support.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hgnc-linkresolve TP53 to its canonical HGNC ID"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
hgnc-link
An MCP (Model Context Protocol) server that grounds gene-nomenclature work in the HUGO Gene Nomenclature Committee (HGNC) dataset from genenames.org, served from a local index of HGNC's bulk downloads over Streamable HTTP or stdio.
Research use only. Not clinical decision support. Do not use for diagnosis, treatment, triage, or patient management.
Why
Every downstream genetics tool needs the same thing from HGNC: turn any gene symbol —
current, outdated (previous), or alias — and any HGNC ID form into the canonical
{hgnc_id, approved_symbol}, then pull cross-references.
HGNC does publish a REST API, but it is field-scoped (/fetch/{field}/{value}): the
caller must already know whether a string is a current symbol, a previous symbol, an alias
or an ID, and query the matching field — a network round-trip per guess. It will not tell
you how a symbol matched, and it will not warn you that an alias belongs to several
genes.
hgnc-link collapses that into one local call against a SQLite index of the bulk dumps.
It runs the full cascade (HGNC ID → current → previous → alias → withdrawn redirect),
returns the match provenance in match_type, and surfaces ambiguity as an
ambiguous_query error with the candidate list rather than silently collapsing it to one
gene.
Related MCP server: GenomeMCP
Quick start
Hosted — no install:
claude mcp add --transport http hgnc https://hgnc-link.genefoundry.org/mcpLocal (Python 3.12+, uv). make data is
mandatory — the server has no data until the HGNC dumps (~33 MB) are downloaded and the
local index is built:
make install # uv sync --group dev
make data # download the HGNC dumps, build the local SQLite index
make dev # unified REST + MCP on http://127.0.0.1:8000/mcp
make mcp-serve # ...or a stdio MCP server, for Claude Desktopclaude mcp add --transport http hgnc-link --scope user http://127.0.0.1:8000/mcpFor stdio see claude-desktop-config.json. Keep the index
fresh with make data-refresh from cron — it is conditional, so an unchanged dump costs
one 304 and no rebuild (Deployment). Serving over HTTP behind a
proxy requires adding the public hostname to the exact Host allowlist — read
Configuration first.
Tools
Tool | Purpose |
| Start here. Any symbol/ID → |
| Resolve many symbols/IDs at once; never fails the batch on a miss. |
| Full HGNC record for one gene (alias- and previous-symbol aware). |
| Full-text search over symbol, name, alias and previous symbols. |
| Gene → NCBI / Ensembl / UniProt / RefSeq / MANE / OMIM / … identifiers. |
| External ID → HGNC gene (the reverse mapping). |
| Browse a gene family by group ID or name. |
| Discovery surface: tools, signatures, workflows, vocabulary. |
| Loaded release, record counts, freshness, data-source status. |
serverInfo.name is hgnc-link, and leaf tool names are intentionally unprefixed per
the GeneFoundry Tool-Naming Standard v1. The canonical gateway namespace token is hgnc:
behind genefoundry-router these
surface as hgnc_<tool> (e.g. hgnc_resolve_symbol).
Every response carries _meta.next_commands — a ready-to-call {tool, arguments} list, on
success and on error — and honours response_mode ∈ {minimal, compact, standard, full}
(default compact). See Usage.
Data & provenance
Source — the HGNC bulk downloads (
hgnc_complete_set.json+withdrawn.txt) from genenames.org, built into a local SQLite index. Queries are served from that index; there are no per-request REST round-trips.Refresh — HGNC publishes Tuesdays and Fridays.
hgnc-link-data refreshis the cron entry point and is conditional (an unchanged dump returns304, so no rebuild); the in-app scheduler is off by default. See Data.Licence — HGNC data is released with no usage restrictions (effectively public domain / CC0). Attribution is requested but not required.
Citation — Seal RL, Braschi B, Gray K, Jones TEM, Tweedie S, Haim-Vilmovsky L, Bruford EA. Genenames.org: the HGNC resources in 2023. Nucleic Acids Res. 2023;51(D1):D1003-D1009. doi:10.1093/nar/gkac888. RRID:SCR_002827.
Documentation
Usage — canonical workflows,
response_mode, chaining, ambiguity and withdrawn-ID semantics, thehgnc://resources.Configuration — every
HGNC_LINK_*variable, the transports, and the Host / Origin / CORS boundary.Data — the bulk dumps, the index build, freshness, and the (unwired) live REST client.
Deployment — cron and systemd refresh, and the Docker path.
Architecture — the ingest → SQLite → service → MCP planes, and the schema.
Design spec — why it is shaped this way.
Contributing
See AGENTS.md for engineering conventions — the error taxonomy, the
next_commands contract, and how to add a tool. make ci-local is the definition-of-done
gate: format, lint, line budget, README standard, mypy strict, and tests.
License
MIT © hgnc-link contributors. HGNC data carries no usage restrictions (effectively CC0); the attribution cited above is requested but not required.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/berntpopp/hgnc-link'
If you have feedback or need assistance with the MCP directory API, please join our Discord server