A side-by-side look at the Hpo Api and Medical Codes MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hpo Api for biology & bioinformatics work as a local process; choose Medical Codes MCP Server for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
term, search, term_children.medcode_get_code, medcode_search_codes, medcode_check_code.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 60/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 7 | 6 |
| Full listing | View Hpo Api | View Medical Codes MCP Server |
term"What does HP:[N] mean" / "look up HPO phenotype [ID]" — fetch a single Human Phenotype Ontology (HPO) term by ID. HPO is the standard ontology for clinical phenotypes used in rare-disease research. Returns label, definition, synonyms, cross-references. Example ID: HP:0001250 (Seizure).search"HPO term for [symptom]" / "phenotype code for [clinical sign]" / "find HPO IDs about [feature]" / "what's the HPO for seizures / autism / short stature" — text search the Human Phenotype Ontology (HPO). Returns ranked terms with HP: IDs. Use to map clinical descriptions to standard ontology terms for rare-disease workups, genomics, or clinical phenotype databases.term_children"More specific HPO phenotypes under [HP:N]" / "child terms of [phenotype]" — direct children of an HPO term in the ontology graph. Use to narrow from a general phenotype (e.g. "Abnormality of the nervous system") to specifics (seizures, ataxia, etc).term_parents"What broader phenotype is [HP:N] under" / "parent term of [HPO ID]" — direct parents of an HPO term in the ontology graph. Use to walk up to a more general phenotype class.term_descendants"All phenotypes under [HP:N]" / "full subtree of [HPO term]" — transitive descendants (children, grandchildren, …) of an HPO term. Use for exhaustive coverage (e.g. "every cardiac phenotype" via descendants of HP:0001626).gene_diseases"What diseases is gene [NCBIGene:N] associated with" / "diseases linked to gene [X]" / "TP53 disease associations" — fetch diseases associated with a gene ID (NCBIGene:N format). Use for gene-to-disease lookups in rare-disease research, variant prioritization. Example ID: NCBIGene:7157 (TP53).disease_phenotypes"What symptoms / clinical features does [disease] cause" / "HPO phenotypes for [OMIM N]" / "clinical signs of [rare disease]" — list HPO phenotype terms for a disease ID (OMIM:N, ORPHA:N, or MONDO:N format). Use to enumerate clinical features of rare diseases. Example ID: OMIM:154700 (Marfan syndrome).medcode_get_codeDecode 1–50 codes to their official descriptions. Auto-detects the system per code; partial-success `found` / `notFound`.medcode_search_codesFull-text search over official descriptions — go from a clinical description to the code.medcode_check_codeValidate a code's existence, currency, and billability, with a `whyNot` for non-billable/terminated cases.medcode_map_codesCrosswalk a code within its hierarchy (`parents`/`children`), a drug across RxNorm (name ↔ RXCUI, NDC ↔ RXCUI, RXCUI → ingredients/brands), or a drug to its RxClass classes and a class to its member drugs.medcode_browse_hierarchyWalk a system's hierarchy for discovery without a search term.medcode_list_systemsList bundled systems with release identifiers, effective dates, and code counts, and the RxClass layer with each source's version (provenance).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.
{
"mcpServers": {
"hpo-api": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-hpo-api"
]
}
}
}
{
"mcpServers": {
"medical-codes-mcp-server": {
"command": "bunx",
"args": [
"@cyanheads/medical-codes-mcp-server@latest"
]
}
}
}