English Français العربية

io.github.pcmedsinge/mcp-terminology

Registre officiel Santé

LOINC/SNOMED CT/RxNorm/ICD-10 lookup, search, translation and ValueSet expansion via FHIR.

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

PYPI package mcp-terminology
Claude Code 
claude mcp add mcp-terminology -e 'TERMINOLOGY_BASE_URL=<TERMINOLOGY_BASE_URL>' -- uvx mcp-terminology==1.0.0
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "mcp-terminology": {
            "command": "uvx",
            "args": [
                "mcp-terminology==1.0.0"
            ],
            "env": {
                "TERMINOLOGY_BASE_URL": "<TERMINOLOGY_BASE_URL>"
            }
        }
    }
}

Variables d'environnement

  • TERMINOLOGY_BASE_URL Base URL of the FHIR terminology server (default: https://tx.fhir.org/r4)

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. fhir-mcp-suite
  2. What's in the suite
  3. Why this suite is different
  4. Quick start — mcp-fhir
  5. Local dev stack
  6. Repo layout
  7. Releases
  8. Contributing

fhir-mcp-suite

Three coherent MCP servers for clinical AI — FHIR R4, terminologies, and clinical reasoning.

What's in the suite

ServerStatusInstallWhat it does
mcp-fhir✅ v1.1.1 on PyPIuvx mcp-fhirFHIR R4 read/search + HAPI profile validation
mcp-terminology✅ v1.0 on PyPIuvx mcp-terminologyUnified LOINC / SNOMED / RxNorm / ICD-10 lookup + ValueSet expansion
mcp-clinical-reasoner✅ v1.0 on PyPIuvx mcp-clinical-reasonerDrug interactions (OpenFDA), dose check, allergy conflicts

Why this suite is different

Every FHIR MCP server available today (June 2026) is a read proxy — they retrieve resources but never tell you whether the resource is valid. mcp-fhir adds HAPI profile validation as a first-class MCP tool. Composing fhir_read → validate_against_profile in one Claude session enables clinical AI pipelines that are actually safe.

Three sharp differentiators:

  1. Profile validation built into mcp-fhir — HAPI validator sidecar, US Core + IPS profiles supported out of the box
  2. Composable suite — three coherent servers sharing one install, one config convention, one eval harness
  3. Production rigor — latency benchmarks, golden-query eval suite, structured JSON logs, /health + LangFuse traces

Quick start — mcp-fhir

# 1-command install (requires Python 3.12+)
uvx mcp-fhir

# Validate a Patient against US Core
# (requires HAPI validator sidecar — see docker-compose.yml)
uvx mcp-fhir --transport sse  # or set MCP_TRANSPORT=sse
Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json
(Windows: %APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "fhir": {
      "command": "uvx",
      "args": ["mcp-fhir"],
      "env": {
        "FHIR_BASE_URL": "https://hapi.fhir.org/baseR4"
      }
    },
    "terminology": {
      "command": "uvx",
      "args": ["mcp-terminology"]
    },
    "clinical-reasoner": {
      "command": "uvx",
      "args": ["mcp-clinical-reasoner"]
    }
  }
}

Local dev stack

# Start HAPI FHIR + validator + Postgres
docker compose up hapi-fhir hapi-validator postgres

# Install workspace
uv sync

# Run unit tests
uv run pytest -m "not integration and not eval"

# Run mcp-fhir locally (stdio, points at local HAPI)
FHIR_BASE_URL=http://localhost:8081/fhir \
HAPI_VALIDATOR_URL=http://localhost:8082 \
  uv run mcp-fhir

Repo layout

fhir-mcp-suite/
├── packages/
│   ├── mcp-fhir/              # PyPI: mcp-fhir          ✅ v1.1
│   ├── mcp-terminology/       # PyPI: mcp-terminology   ✅ v1.0
│   └── mcp-clinical-reasoner/ # PyPI: mcp-clinical-reasoner ✅ v1.0
├── shared/                    # structlog, LangFuse, base Pydantic models, eval harness
├── evals/                     # golden query sets per server
├── docs/                      # MkDocs Material site
├── .github/workflows/         # ci.yml (matrix) + release.yml (per-package PyPI on tag)
├── docker-compose.yml         # all 3 + HAPI validator + Postgres
├── pyproject.toml             # uv workspace root
└── mkdocs.yml

Releases

PackageVersionReleased
mcp-fhirv1.1June 2026
mcp-terminologyv1.0June 2026
mcp-clinical-reasonerv1.0June 2026

Contributing

See CONTRIBUTING.md. Apache-2.0 licensed — PRs welcome.

Questions fréquentes

Qu'est-ce que io.github.pcmedsinge/mcp-terminology ?

LOINC/SNOMED CT/RxNorm/ICD-10 lookup, search, translation and ValueSet expansion via FHIR.

Comment installer io.github.pcmedsinge/mcp-terminology ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add mcp-terminology -e 'TERMINOLOGY_BASE_URL=<TERMINOLOGY_BASE_URL>' -- uvx mcp-terminology==1.0.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.pcmedsinge/mcp-terminology ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.pcmedsinge/mcp-terminology est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient io.github.pcmedsinge/mcp-terminology ?

Il est publié par pcmedsinge. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.