Molecare MCP

What molecare-mcp MCP server does

The molecare-mcp MCP server exposes dermatology reference material and mole-related operations through MCP. Its bundled knowledge tools work offline and require no account, database, or network connection. They support searches across dermatology content, terminology lookup, SNOMED CT to ICD-10 mapping, lesion feature descriptions, and educational risk-factor guidance.

The public package also includes optional tools for a MoleCare-compatible backend. These cover a user's moles, analysis payloads, mole change history, risk factors, and comparisons between two moles. Those operations are useful for prototyping assistant flows around longitudinal mole tracking, but they depend on a configured backend for real data.

Outputs are educational or operational aids. The package is not a medical device and should not be used to diagnose conditions, determine treatment, assign urgency, or replace clinical judgment.

How it works

The package runs as an MCP server over standard input and output. A client starts it with npx -y molecare-mcp, after which it waits for MCP requests. The dermatology reference tools read from data bundled with the published package, so they are available immediately after installation.

Terminology coverage is intentionally limited. The bundled SNOMED CT set contains seven concepts, including melanoma, melanoma in situ, basal cell carcinoma, squamous cell carcinoma, actinic keratosis, dysplastic naevus, and melanocytic naevus. The package also includes 25 WHO ICD-10 categories and nine SNOMED-to-ICD-10 mapping rows. A request outside the supported subset returns coverage information rather than an unqualified result.

Three reusable prompts are available for walking through ABCDE observations, preparing for a dermatology appointment, and explaining a SNOMED CT code. These prompts include a non-diagnostic disclaimer; the terminology prompt requires a SNOMED CT code.

Setup and configuration

A minimal client configuration starts the server without environment variables:

{
  "mcpServers": {
    "molecare": {
      "command": "npx",
      "args": ["-y", "molecare-mcp"]
    }
  }
}

The same command can be run directly to verify that the process starts. It waits on stdio and normally produces no output while idle.

Set MOLECARE_API_URL and MOLECARE_API_KEY only when connecting to a MoleCare-compatible API. Without those settings, backend-dependent operations use clearly labelled mock product data, while the knowledge tools continue to function locally. LOG_LEVEL, MCP_HEALTH_PORT, PORT, PRIVACY_GATE_URL, and PRIVACY_GATE_TIMEOUT_MS are optional shared settings described by the project.

Tools and capabilities

The main tool groups include:

• Search dermatology information and conditions by name or description.
• Look up SNOMED CT concepts and map supported SNOMED codes to ICD-10.
• Describe lesion characteristics using ABCDE-style features.
• Retrieve named condition risk factors, user risk factors, and typical progression stages.
• List malignant skin conditions included in the reference data.
• Retrieve user moles, analysis payloads, mole changes, and compare two moles when backend access is available.

The package also provides molecare://knowledge/* and molecare://ontology/* resources for reference content, including ABCDE criteria, Fitzpatrick skin types, prevention guidance, dermatologist-visit guidance, terminology lists, mappings, and provenance metadata.

Limitations and notes

The molecare-mcp MCP server does not provide a diagnostic model or a medical risk score. assess_risk_from_factors identifies named educational factors rather than calculating an overall score. Backend tools are only representative when no API credentials and compatible service are configured.

The repository separately describes molecare-ops-mcp, an operations binary with mock-first infrastructure and MLOps tools. That separate binary is not part of the public dermatology tool set described here. Protect API keys and avoid placing production credentials in client configuration files that synchronize to shared cloud storage.