hpo-link
MCP server that provides tools for querying the Human Phenotype Ontology (HPO) including term lookup, hierarchy exploration, cross-ontology mappings, and gene-phenotype-disease associations, all grounded in a local SQLite database for fast offline lookups.
README
hpo-link
MCP/API server that grounds phenotype work in the Human Phenotype Ontology (HPO).
hpo-link builds a local SQLite database from the HPO OBO release and HPOA
gene/disease annotation files (served via OBO PURLs and the HPO GitHub
releases) and serves a read-only MCP + REST surface for phenotype term
lookup, the is_a hierarchy (ancestors/descendants via a transitive closure),
cross-ontology mapping, and gene↔phenotype↔disease association queries. There
is no live API — the local database is the only source, so lookups are fast
and offline.
Every response is grounded in the local database and cites the HPO id + HPO release version. Research use only; not clinical decision support.
Tools
Discovery
| Tool | Signature |
|---|---|
get_server_capabilities |
get_server_capabilities(detail=) — discovery surface (tools, workflows, error taxonomy, limits). |
get_diagnostics |
get_diagnostics() — database status, loaded HPO release, counts. |
Phenotype term lookup
| Tool | Signature |
|---|---|
resolve_term |
resolve_term(query, response_mode=) — label/synonym/HP id/xref → canonical term + match_type. |
search_terms |
search_terms(query, limit=, include_obsolete=, response_mode=) — FTS over name/synonyms/definition. |
get_term |
get_term(term, response_mode=) — definition, synonyms, grouped xrefs, parents/children, obsolescence. |
Hierarchy
| Tool | Signature |
|---|---|
get_term_ancestors |
get_term_ancestors(term, limit=, response_mode=) — transitive is_a ancestors. |
get_term_descendants |
get_term_descendants(term, limit=, response_mode=) — transitive is_a descendants. |
get_term_parents |
get_term_parents(term, response_mode=) — direct is_a parents. |
get_term_children |
get_term_children(term, response_mode=) — direct is_a children. |
Cross-ontology mapping
| Tool | Signature |
|---|---|
resolve_xref |
resolve_xref(xref_id, limit=, response_mode=) — external CURIE → HP ids, ranked by predicate. |
map_cross_ontology |
map_cross_ontology(term, prefixes=, response_mode=) — an HP term → mappings grouped by prefix. |
Gene ↔ Phenotype ↔ Disease associations (HPOA)
| Tool | Signature |
|---|---|
get_phenotypes_for_gene |
get_phenotypes_for_gene(gene, response_mode=) — HPO terms annotated to a gene. |
get_genes_for_phenotype |
get_genes_for_phenotype(term, response_mode=) — genes annotated to an HPO term. |
get_phenotypes_for_disease |
get_phenotypes_for_disease(disease_id, response_mode=) — HPO terms annotated to a disease. |
get_diseases_for_phenotype |
get_diseases_for_phenotype(term, response_mode=) — diseases annotated to an HPO term. |
get_genes_for_disease |
get_genes_for_disease(disease_id, response_mode=) — genes associated with a disease. |
get_diseases_for_gene |
get_diseases_for_gene(gene, response_mode=) — diseases associated with a gene. |
Every response carries _meta.next_commands (ready-to-call follow-ups). Ids are
normalised to HP:NNNNNNN. response_mode ∈ minimal | compact | standard | full (default compact).
Tools are unprefixed here (serverInfo.name = hpo-link); the GeneFoundry
router applies the canonical gateway namespace token hpo at mount time.
Quickstart
uv sync --group dev # install dependencies
uv run hpo-link-data build # download HPO (OBO + HPOA) and build the local database
uv run hpo-link-data status # print the loaded HPO release + counts
uv run hpo-link-mcp # stdio MCP server (for Claude Desktop)
uv run hpo-link # unified REST + MCP server on http://127.0.0.1:8000
Or via make:
make install # uv sync --group dev
make data # build the local HPO database
make data-status # print loaded release + counts
make dev # unified REST + MCP server
make mcp-serve # stdio MCP server
MCP client setup
HTTP (unified server exposes /mcp alongside /health):
claude mcp add --transport http hpo-link --scope user http://127.0.0.1:8000/mcp
stdio (Claude Desktop and similar):
make mcp-serve # runs mcp_server.py on stdio (stdout is reserved for the protocol)
Data provenance
The database is built from:
- HPO ontology (
hp.json) — downloaded from the HPO GitHub releases via the OBO PURL (http://purl.obolibrary.org/obo/hp.json). Contains ~19,800 active phenotype terms (HPO v2026-06-06). Fetched via conditional GET (ETag / Last-Modified); a304reuses the local file. - HPOA annotations (
phenotype.hpoa) — the HPO phenotype-to-disease annotation file linking HPO terms to OMIM/Orphanet/DECIPHER diseases, and gene associations derived from those annotations.
The build is atomic (temp file + os.replace) under a lock, and records
provenance in a meta table (HPO release version, source validators, counts).
get_diagnostics and get_server_capabilities report the loaded release.
Prebuilt artifact distribution
To skip the build step, set HPO_LINK_DATA__PREBUILT_DB_URL to the URL of a
prebuilt SQLite artifact (e.g., from a GitHub Release). The entrypoint will
download and verify it before serving. If absent, the server builds from
source automatically (HPO_LINK_DATA__AUTO_BOOTSTRAP=true).
Documentation
- docs/architecture.md — the two planes, ingest pipeline, SQLite schema, request lifecycle.
- docs/usage.md — per-tool examples and workflows.
- docs/deployment.md — Docker, environment variables, refresh.
- AGENTS.md / CLAUDE.md — contributor + agent guide.
License & citation
Code: MIT.
Data: HPO is distributed under a custom license for research and educational use. See https://hpo.jax.org/app/license for details. Attribution required.
Citation: Köhler S, Gargano M, Matentzoglu N, et al. The Human Phenotype Ontology in 2021. Nucleic Acids Research 2021;49(D1):D1207–D1217. doi:10.1093/nar/gkaa1043.
For the most recent release cite: Gargano MA, Matentzoglu N, Coleman B, et al. The Human Phenotype Ontology in 2024: phenotypes around the world. Nucleic Acids Research 2024;52(D1):D1333–D1346. doi:10.1093/nar/gkad1005.
Research use only; not for diagnosis, treatment, triage, or patient management.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。