medical-terminologies-mcp MCP Server

A Model Context Protocol (MCP) server providing unified access to major global medical terminologies:

Local serverstdioMIT

What is the medical-terminologies-mcp Server?

medical-terminologies-mcp is an MCP project maintained in the sidneybissoli/medical-terminologies-mcp repository. The maintainer describes its purpose as “A Model Context Protocol (MCP) server providing unified access to major global medical terminologies”. Read the project documentation for the complete scope.

Installation

The documented npm package is medical-terminologies-mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.

Configuration values

The example declares WHO_CLIENT_ID, WHO_CLIENT_SECRET. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
CID10 is natively Portuguese: cid10_search / cid10_lookup / cid10_chapter(s) serve the DataSUS V2008 dataset (the CID-10 the Brazilian SUS uses operationally).
ICD11 in official Portuguese: pass language: "pt" to icd11_search / icd11_lookup to search and read WHO's official pt-BR linearization labels.
MeSHpass language: "pt" to mesh_search / mesh_descriptor to request NLM's official translations where they exist.
icd11_searchSearch ICD-11 by term
icd11_lookupGet entity details by code/URI
icd11_hierarchyNavigate parent/child relationships
icd11_chaptersList all ICD-11 chapters
icd11_postcoordinationGet postcoordination axes
loinc_searchSearch lab tests and observations
loinc_detailsGet full LOINC code details
loinc_answersAnswer list of a questionnaire item: LA code, text, order and score (PHQ-9 items: 0-3); empty for codes without a list, "not found" for unknown codes
loinc_panelsPanel/form structure: member items in form order
rxnorm_searchSearch drugs by name
rxnorm_conceptGet drug concept details
rxnorm_ingredientsGet active ingredients
rxnorm_classesGet therapeutic classes
rxnorm_ndcMap between RxCUI and NDC
mesh_searchSearch MeSH descriptors
mesh_descriptorGet descriptor details
mesh_treeGet tree hierarchy location
mesh_qualifiersGet allowed qualifiers
map_icd10_to_icd11Authoritative ICD-10 → ICD-11 mapping via bundled WHO transition tables; returns primary code + chapter + URIs and any WHO-documented alternatives
validate_codesBatch-validate up to 50 codes across ICD-11, LOINC, RxNorm, MeSH, ATC, CID-10; returns per-code valid/invalid + display name
find_equivalentRanked unified search across terminologies: server-computed match_score/rank per candidate plus cross-terminology groups of lexically identical titles
harmonize_termsBatch-map up to 50 free-text terms to standard codes: diagnosis → ICD-11, drug → RxNorm (+ ATC classes), lab → LOINC. Per term: ranked candidates with…
atc_classifyDrug name → ATC code(s)
atc_lookupATC code (level 1-4) → name + level type
atc_membersATC class → member drugs
cid10_searchPortuguese text search (diacritic-insensitive, AND between words; everyday words resolved to CID-10 wording, and the response says so)
cid10_lookupCode → official Portuguese name
cid10_chaptersList the 22 CID-10 chapters
cid10_chapterChapter detail with constituent groups
AVC0
atropelamento0
aids0
terminology_versionsList all 8 supported terminologies with current version, release date, publisher, source URL, and update cadence
terminology_diffReport what diff data is available between two versions of a terminology (real cross-revision stats for ICD-10 → ICD-11; guidance otherwise)
searchSearches the catalog (CID-10, ICD-11, LOINC, RxNorm, MeSH, terminology versions) and returns { id, title, url } ranked by relevance
fetchReturns the full document of an id from search ({ id, title, text, url, metadata }), rendered by the terminology's lookup tool

How to install the medical-terminologies-mcp Server

{
  "mcpServers": {
    "medical-terminologies": {
      "command": "npx",
      "args": [
        "-y",
        "medical-terminologies-mcp"
      ],
      "env": {
        "WHO_CLIENT_ID": "your-who-client-id",
        "WHO_CLIENT_SECRET": "YOUR_WHO_CLIENT_SECRET"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

VariableDescriptionRequired
WHO_CLIENT_IDDeclared in the maintainer’s client configuration.Check documentation
WHO_CLIENT_SECRETDeclared in the maintainer’s client configuration.Check documentation