← Claude plugins
CLAUDE PLUGIN

memorydetective

Publisher not specified · Claude Code

What this plugin does

Hunt iOS memory leaks and investigate runtime performance from inside Claude Code. memorydetective bundles an MCP server with 28 tools for analyzing .memgraph and .trace files, plus
a /perf-investigate skill that routes you to the right playbook based on symptoms (leak, hang, jank, slow launch).

Key features:
- 34-pattern retain-cycle classifier covering SwiftUI (incl. @Observable, SwiftData, NavigationStack), Swift Concurrency, Combine, UIKit, Core Data, RxSwift, Realm, and Coordinator
pattern
- Every classification ships fixHint + staticAnalysisHint + a Swift before/after fixTemplate snippet
- Trace analysis: hangs, animation hitches, allocations, app launch, time profile
- compareTracesByPattern for CI gating against perf regressions
- 5 SourceKit-LSP-backed Swift source-bridging tools (find references, hover, definitions)
- macOS unified logging (logShow / logStream)
- 5 slash commands for direct invocation: /investigate-leak, /investigate-hangs, /investigate-jank, /investigate-launch, /verify-cycle-fix

Reads memgraphs exported from Xcode's Memory Graph Debugger and traces from xctrace. Ships as both a Claude Code plugin and a standalone npm package, so the same MCP server works in
Cursor, Cline, Claude Desktop, and Continue.

Catalog observations

Sources
Community
Works with
Claude Code
Reported installs
Not provided
First observed
2026-10-03 22:13 UTC
Last observed
2026-10-11 06:00 UTC

Installation counts are reported by Claude Marketplace, not independently verified active users. Observation dates are not release dates. Pricing and account requirements must be checked with the publisher.

Install in Claude Code

Choose a source and review what the plugin adds before installing.

Community

/plugin marketplace add anthropics/claude-plugins-community
/plugin install memorydetective@claude-community

Claude Code installation documentation

Source evidence

Listing and manifest JSON

Descriptions and compatibility labels come from the linked sources. Where both sources match, the GitHub description is used because web summaries may be shortened. We have not independently tested the declared capabilities.