Medical Terminologies MCP Server

Unified MCP server for seven medical terminologies (ICD-11, SNOMED CT, LOINC, RxNorm, MeSH, ATC, CID-10) with authoritative WHO ICD-10→ICD-11 mapping. 37 tools, hosted endpoint available, MIT. The medical terminologies mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

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

• 31 default tools (37 with SNOMED enabled) for medical terminology lookup
• 3 MCP Prompts that orchestrate tool calls into named workflows (find-medical-code, drug-info, cid10-portuguese-lookup) — clients render these as one-click user actions
• 4 MCP Resources for in-process reference content (info://server, info://cid10/chapters, info://licenses, info://stats) — sub-millisecond reads (except info://stats which round-trips to the StatsCounter Durable Object on the hosted endpoint)
• Multi-terminology support in a single server
• Cross-terminology mapping and search
• Built-in caching for improved performance

Its toolset

Everything the assistant can do here goes through one of these:

• icd11_search — Search ICD-11 by term
• icd11_lookup — Get entity details by code/URI
• icd11_hierarchy — Navigate parent/child relationships
• icd11_chapters — List all ICD-11 chapters
• icd11_postcoordination — Get postcoordination axes
• loinc_search — Search lab tests and observations
• loinc_details — Get full LOINC code details
• loinc_answers — Get answer list for surveys
• loinc_panels — Get panel/form structure
• rxnorm_search — Search drugs by name
• rxnorm_concept — Get drug concept details
• rxnorm_ingredients — Get active ingredients

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 6 environment variables: WHO_CLIENT_ID, WHO_CLIENT_SECRET, ENABLE_SNOMED_TOOLS, SNOMED_BASE_URL, SNOMED_LANGUAGE, WHO_ICD11_RELEASE_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Medical Terminologies MCP's toolset — icd11_search, icd11_lookup, icd11_hierarchy and 11 more — is a fair guide to whether it matches your workflow. It is maintained by sidneybissoli; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Medical Terminologies MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the medical terminologies mcp mcp server does with a few real requests.