Gtex vs Ucsc Genome

A side-by-side look at the Gtex and Ucsc Genome MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Gtex logoGtexBiology & Bioinformatics · Local subprocess (stdio)GTEx — Genotype-Tissue Expression human gene-expression atlas41FairAuth: not declaredUcsc Genome logoUcsc GenomeBiology & Bioinformatics · Local subprocess (stdio)UCSC Genome Browser REST API — reference genome assemblies for ~250 species, the annotation tracks…53GoodAuth: not declared

Verdict: choose Gtex for biology & bioinformatics work as a local process; choose Ucsc Genome for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Gtex logoChoose Gtex when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
  • You prefer a local stdio subprocess transport.
Explore Gtex

Ucsc Genome logoChoose Ucsc Genome when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like hg38, mm39, danRer11.
Explore Ucsc Genome

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGtex logoGtexUcsc Genome logoUcsc Genome
CategoryBiology & BioinformaticsBiology & Bioinformatics
Quality signal41/100 · Fair53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listed3

Tools & capabilities

Gtex tools

No tool names declared yet. Check the project README from the listing page.

Ucsc Genome tools 3

  • hg38
  • mm39
  • danRer11

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Gtex

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gtex": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-gtex"
      ]
    }
  }
}

Ucsc Genome

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ucsc-genome": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ucsc-genome"
      ]
    }
  }
}

Frequently asked questions

Gtex is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Ucsc Genome belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Gtex for biology & bioinformatics work and Ucsc Genome for biology & bioinformatics.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Gtex has no declared pricing — check the project's own site. Ucsc Genome has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add gtex and ucsc-genome as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Gtex has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Ucsc Genome has 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars.