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 — shipped as a separate binary, molecare-ops-mcp (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

One command, no API key, no database. Real output from the published package.

---

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.

Claude Code plugin

This repository is also a Claude Code plugin: the same server, plus a skill that tells Claude when to use it and to never diagnose.

claude plugin marketplace add MoleCare/molecare-mcp