MoleCare MCP Server

Model Context Protocol (MCP) server that gives Claude and other MCP clients access to:

1. Dermatology knowledge — ABCDE education, SNOMED CT / ICD-10 helpers, risk-factor prompts
2. Optional MoleCare API tools — moles, trends, analysis (your backend + API key)
3. Optional MLOps / ops tools — health checks, MLflow, feature store, infra (mock-first)

Not a medical device. Outputs are educational and operational aids only. Do not use for diagnosis or treatment decisions.

Product site: molecare.co.uk · App: iOS · Android

Why this exists

MoleCare helps people track moles over time and prepare for clinician visits. This MCP server lets developers and operators:

• Query educational skin-health knowledge from Claude Desktop / Cursor
• Prototype assistant flows against a MoleCare-compatible API
• Explore MLOps tooling with safe mock data when no credentials are set

Quick start

No credentials, no database, no cloud account. Add this to your MCP client config and restart it:

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

For Claude Desktop on macOS that file is ~/Library/Application Support/Claude/claude_desktop_config.json.

The dermatology knowledge tools work immediately — they read from a knowledge base bundled in the package. Everything that talks to a backend returns clearly-labelled mock data until you configure it, so you can explore the whole tool surface before deciding whether you want any of it.

To try it without a client at all:

npx -y molecare-mcp

It starts and waits on stdio. No output means it is working.

Connecting a real backend

Only needed if you are running a MoleCare-compatible API:

{
  "mcpServers": {
    "molecare": {
      "command": "npx",
      "args": ["-y", "molecare-mcp"],
      "env": {
        "MOLECARE_API_URL": "http://localhost:8080/api",
        "MOLECARE_API_KEY": "your-local-api-key"
      }
    }
  }
}

Use localhost (or your own deployment). Do not paste production keys into config files that sync to cloud drives.

Environment variables

All optional unless you want live backends.

See .env.example.

Tools

Dermatology knowledge — no setup required

These are the reason most people install this. They answer from a bundled knowledge base and need no API, no key, and no network.

... View full README on GitHub