English Français العربية

Hgnc

Official registry Other

HGNC (HUGO Gene Nomenclature Committee) MCP.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http hgnc 'https://gateway.pipeworx.io/hgnc/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "hgnc": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/hgnc/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-hgnc
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-hgnc

HGNC (HUGO Gene Nomenclature Committee) MCP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1881+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
get_geneExact lookup of an approved human gene by its official HGNC symbol — returns the full authoritative record: approved name, locus type, chromosomal location, alias/previous symbols, gene groups, and cross-references (Entrez, Ensembl, UniProt, OMIM, RefSeq, UCSC, CCDS). Use search_genes first if you only have a name fragment or aren't sure of the exact symbol. Keyless.
search_genesFuzzy search across approved symbols, names, and aliases — e.g. "breast cancer", "p53", "tumor protein". Returns lightweight matches (hgnc_id, symbol, relevance score) ranked by score; call get_gene with a returned symbol for the full record. Keyless.
resolve_xrefReverse-lookup: map an external database id to its canonical HGNC gene. "What gene is Entrez 672?" -> BRCA1. Accepts entrez_id, ensembl_gene_id, uniprot_ids, omim_id, refseq_accession, or ucsc_id and returns the same full record as get_gene. Keyless.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "hgnc": {
      "url": "https://gateway.pipeworx.io/hgnc/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/hgnc/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1881+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/hgnc_get_gene \
  -H 'Content-Type: application/json' \
  -d '{"symbol":"BRCA1"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/hgnc_get_gene. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "hgnc": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-hgnc"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-hgnc

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Hgnc data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Frequently asked questions

What is Hgnc?

HGNC (HUGO Gene Nomenclature Committee) MCP.

How do I install Hgnc?

It runs as a remote server. In Claude Code: claude mcp add --transport http hgnc 'https://gateway.pipeworx.io/hgnc/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Hgnc need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Hgnc open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Hgnc?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.