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

Related MCP server: opentargets-mcp

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.

Resources: molecare://knowledge/* — ABCDE criteria, Fitzpatrick skin types, prevention, when to see a dermatologist, SNOMED CT and ICD-10 references.

MoleCare product data — needs an API

Returns labelled mock data until MOLECARE_API_URL is set.

These exist because MoleCare operates this stack from an assistant. They are of little use outside that context, and all of them return mock data unless the matching backend is configured.

The AWS tools need @aws-sdk/client-ec2 and @aws-sdk/client-cloudwatch, which are optional peer dependencies — they are not installed by default, because they add 33 MB that nobody wanting the dermatology tools should have to download. Install them yourself if you want live AWS data:

npm i @aws-sdk/client-ec2 @aws-sdk/client-cloudwatch

Architecture

Claude / Cursor / MCP client
        │ stdio (JSON-RPC)
        ▼
  molecare-mcp
   ├─ medical KB (local)
   ├─ MoleCare API client (optional)
   ├─ ontology / MLflow / Feast clients (optional)
   └─ AWS / CI clients (optional, mock if unset)
        │
        └─ optional HTTP GET /health  (Docker / ECS)

Docker

docker build -t molecare-mcp .
docker run --rm -p 3000:3000 molecare-mcp
curl http://localhost:3000/health

Security

• Never commit .env files or API keys — see SECURITY.md to report a vulnerability

• Prefer mock mode for demos and screenshots

• Tools that accept userId can return PHI only if you point them at a real backend with real auth — treat that as production

• Rate-limit and auth belong on your API, not only on the MCP process

Medical disclaimer

MoleCare MCP provides educational information and developer tooling. It does not diagnose melanoma or any disease. Always consult a qualified clinician for medical concerns.

Development

git clone https://github.com/MoleCare/molecare-mcp.git
cd molecare-mcp
npm install
npm run build
npm run dev      # auto-reload
npm run inspect  # browse tools in MCP Inspector

Contributions are welcome. Read CONTRIBUTING.md first — it covers the mock-first rule, the clinical-safety boundary for anything touching medical content, and how to pick up a good first issue.

Please keep secrets out of examples and prefer localhost defaults.

Related

Environment variables: .env.example is the authoritative list (all 27 variables read by the source). Regenerate the ground truth with grep -rhoE "process\.env\.[A-Z_0-9]+" src/. ONTOLOGY_API_URL and FEAST_REPO_PATH are not read by any source file.

• Model Context Protocol

• MoleCare

• MoleCare-ML — melanoma classification service and training notebooks

License

Apache-2.0 © MoleCare LTD