Genefoundry
One gateway to 22 biomedical MCP servers: gnomAD, ClinVar, HPO, UniProt and more
- Platforms
- API, self-hosted
- Runs
- Remotely
- Version
- 0.10.17
- Listing updated
- today
Similar MCP servers
About Genefoundry
Genefoundry is an MCP server for health and science. It runs as a hosted remote server, so there is nothing to install locally.
Hosts that mounted every biomedical backend directly would face hundreds of tools. GeneFoundry puts them behind a single endpoint and replaces the flat list with search: the model searches for a tool by intent, then calls it by its namespace_tool name. Each backend's main entry point stays pinned and visible.
The federated fleet is listed as 22 backends and 285 tools, among them gnomAD (22 tools), ClinVar, ClinGen, the Human Phenotype Ontology, UniProt, PubTator3, Orphanet and MaveDB. The router never rewrites a backend's data and does not forward the caller's token upstream.
It is for research only and not clinical decision support. A browser sign-in is required, and the router itself is a FastMCP 3 aggregator that can be run against the live fleet.
Install
Run in a terminal
claude mcp add --transport http genefoundry https://genefoundry.org/mcpAdd to Settings → Connectors → Add custom connector
https://genefoundry.org/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"genefoundry": {
"url": "https://genefoundry.org/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"genefoundry": {
"type": "http",
"url": "https://genefoundry.org/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"genefoundry": {
"serverUrl": "https://genefoundry.org/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"genefoundry": {
"type": "http",
"url": "https://genefoundry.org/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (2)
Taken from the project documentation; the running server may differ.
- search_tools
- Relevance search over the whole federated catalog.
- call_tool
- Call a catalog tool by its namespace_tool name.
What it does
- Single endpoint
- Federates 22 backends behind one Streamable HTTP URL.
- Search-based discovery
- Finds the right tool by intent instead of scrolling a huge catalogue.
- Namespaced tools
- Avoids collisions with names such as gnomad_search_genes.
- Source records
- Example answers link back to the original ClinVar and ClinGen records.
- Token isolation
- The caller's token is not forwarded to the backends.
- Self-run router
- The router can run locally against the live fleet.
Good for
- Look up gene constraint metrics and ClinVar variants for a gene
- Find genes shared by two phenotype terms
- Check ClinGen gene-disease validity evidence
- Search biomedical literature annotations
Genefoundry FAQ
Is it suitable for clinical decisions?
No. It states research use only, not for diagnosis, treatment, triage or patient management.
How many tools does it expose?
Three kinds: search_tools, call_tool and each backend's pinned entry point; the catalog behind them lists 285 tools.
Do I need to sign in?
Yes, the site notes a browser sign-in is required when you connect.
How do I add Genefoundry to Claude Code?
Run this command in your terminal: claude mcp add --transport http genefoundry https://genefoundry.org/mcp
What are the best alternatives to Genefoundry?
The closest alternatives to Genefoundry are Tooluniverse, Oya Browser, Midplane, BasalFit and Complex Portal.
Where this comes from
- Description: written from the project's README and the project's website.
- Install steps: from the official MCP Registry entry.
