LeakCanary MCP Server

A standalone Kotlin/JVM MCP server that automates Android memory leak detection using LeakCanary and adb logcat. It parses leak traces, classifies root causes, assigns priority levels, suggests fixes, and tracks leak history across sessions -- all exposed as MCP tools for use in Cursor, VS Code, and Android Studio.

Prerequisites

• Java 17+ installed and available on PATH
• adb installed (Android SDK Platform-Tools) -- the server auto-detects adb from ANDROID_HOME, ANDROID_SDK_ROOT, or common SDK install locations
• An Android device or emulator connected via USB/WiFi with LeakCanary integrated in the debug build

Repository Link: https://github.com/ravisharma46/Leak-Canary-Mcp-Server.git

Quick Install (Recommended)

The fastest and most universally compatible way to use the MCP server across Windows, macOS, and Linux. It requires zero path configuration.

Add this directly to your ~/.cursor/mcp.json:

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

Restart Cursor and the 12 tools will appear in the MCP tools panel.

Setup in VS Code

Make sure you have GitHub Copilot extension installed with Agent mode enabled (VS Code 1.99+).

Option A — Workspace level (.vscode/mcp.json in your project root):

{
  "servers": {
    "leakcanary": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "leakcanary-mcp"]
    }
  }
}

Option B — User level (VS Code settings.json):

{
  "mcp": {
    "servers": {
      "leakcanary": {
        "type": "stdio",
        "command": "npx",
        "args": ["-y", "leakcanary-mcp"]
      }
    }
  }
}

Open Copilot Chat → Agent mode and the LeakCanary tools will be available.

Setup in Android Studio

Android Studio supports MCP servers through the Gemini plugin (Android Studio Meerkat 2024.3+ or later).

1. Open Settings → Tools → AI Assistant → MCP Servers
2. Click + Add and configure:

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

Alternatively, add a mcp.json file in the .idea folder of your project:

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

Restart Android Studio and the tools will appear under Gemini → MCP Tools.

Note: All setups use npx to dynamically execute the wrapper. The wrapper auto-downloads and updates the server JAR for you on each run.

Database-First Data Strategy

The server reads leak data directly from the app's LeakCanary SQLite database as the primary source, not from adb logcat. This means leak data is always available -- even after reboots, logcat buffer clears, or the next day.

How it works

1. Primary: App Database (BLOB deserialization) -- Pulls the app's leaks.db to the host and deserializes the HeapAnalysisSuccess Java objects stored as BLOBs using the shark library. This provides the full analysis -- complete reference chains, retained sizes, leak status per node, GC roots, heap metadata, and device info. Identical quality to what you see in the LeakCanary app.
2. Fallback: Logcat -- If the database isn't accessible (app not debuggable, not installed, etc.), falls back to reading adb logcat -s LeakCanary.
3. Auto-Discovery -- When no package_name is provided, the server automatically scans all installed apps on the device to find ones with a LeakCanary database. If multiple apps are found, it prompts you to choose. If only one app is found, it reads leaks directly.

T

... View full README on GitHub