Enterprise DNA
M MCP Servers Developer low

SidneyBissoli/medical-terminologies-mcp

by Various

MCP Server for global medical terminologies: ICD-11, SNOMED CT, LOINC, RxNorm, MeSH

S

MCP

SidneyBissoli/medical-terminologies-mcp

Added 1 June 2026

Overview

An MCP server that provides access to global medical terminologies including ICD-11, SNOMED CT, LOINC, RxNorm, and MeSH. It allows AI agents to query and retrieve standardized medical codes and concepts via the Model Context Protocol.

Best for

Best for
Developers building AI agents that need to access standardized medical codes and terminologies

Use cases

  • Look up ICD-11 diagnosis codes for clinical documentation
  • Retrieve SNOMED CT concepts for medical record integration
  • Query RxNorm drug codes for medication management

Notes

An MCP server that provides access to global medical terminologies including ICD-11, SNOMED CT, LOINC, RxNorm, and MeSH. It allows AI agents to query and retrieve standardized medical codes and concepts via the Model Context Protocol.

3 stars on GitHub. Last updated 2026-05-19.

Use cases

  • Look up ICD-11 diagnosis codes for clinical documentation
  • Retrieve SNOMED CT concepts for medical record integration
  • Query RxNorm drug codes for medication management

Pros

  • Covers multiple major medical terminology standards in one server
  • Uses the MCP protocol for easy integration with AI agents
  • Written in TypeScript for type safety and broad compatibility

Cons

  • Very low community adoption with only 3 stars
  • Limited documentation and examples available
  • May require manual setup for each terminology source

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Covers multiple major medical terminology standards in one server
  • Uses the MCP protocol for easy integration with AI agents
  • Written in TypeScript for type safety and broad compatibility

Cons

  • Very low community adoption with only 3 stars
  • Limited documentation and examples available
  • May require manual setup for each terminology source