Medical Terminologies MCP
Let your agent resolve clinical codes (ICD-11, SNOMED, LOINC, RxNorm, and more) while you build health,.fhir, or compliance features.
Overview
Medical Terminologies MCP is a MCP server for the Build phase that provides 37 unified lookup tools across major clinical and drug terminologies for coding agents.
What is this MCP server?
- 37 MCP tools across ICD-11, SNOMED, LOINC, RxNorm, MeSH, ATC, and CID-10
- Stdio npm package plus optional streamable-http remote at medical-terminologies-mcp.sidneybissoli.workers.dev
- ICD-11 subset (5 tools) uses WHO_CLIENT_ID; other terminologies work without that credential
- MIT-licensed unified search and lookup instead of per-vocabulary custom clients
- Environment-variable gate so the server starts even when WHO credentials are not yet configured
- 37 MCP tools documented in the server description
- Seven terminology systems: ICD-11, SNOMED, LOINC, RxNorm, MeSH, ATC, CID-10
- Five ICD-11 tools require WHO_CLIENT_ID; server version 1.5.1
Community signal: 3 GitHub stars.
What problem does it solve?
Health-oriented solo builders drown in separate terminology APIs when they only need fast code search and normalization inside the IDE.
Who is it for?
Indie devs building health charting, billing helpers, literature tools, or agent copilots that must cite standard medical codes accurately.
Skip if: Non-clinical apps with no coding vocabulary needs, or regulated teams that require on-prem-only terminology without cloud MCP remotes.
What do I get? / Deliverables
After registration, your agent can query ICD, SNOMED, LOINC, RxNorm, and related systems through one MCP surface while you implement features and tests.
- 37 registered MCP tools spanning seven terminology families
- Agent-resolvable standard codes for schemas, prompts, and API payloads
- Optional remote MCP endpoint without local npm install
Recommended MCP Servers
Journey fit
Medical coding belongs in Build when you wire real terminology services into backends, agents, and documentation—not when you are only brainstorming unrelated apps. Unified lookup across 37 tools is an integration layer that replaces bespoke HTTP glue to WHO, NIH, and related code systems.
How it compares
Terminology lookup MCP with 37 tools, not an EHR, not clinical decision support, and not a single-vocabulary SDK.
Common Questions / FAQ
Who is medical-terminologies-mcp for?
Solo builders and small teams creating health-tech or research tools who want agent-driven lookup across ICD-11, SNOMED, LOINC, RxNorm, MeSH, ATC, and CID-10.
When should I use medical-terminologies-mcp?
Use it during build and integration work when you map diagnoses, labs, medications, or literature terms to standard codes in your API or UI.
How do I add medical-terminologies-mcp to my agent?
Add the npm stdio server medical-terminologies-mcp to your MCP config, set WHO_CLIENT_ID only if you need ICD-11 tools, or point at the streamable-http remote URL from the manifest.