Memorydetective
Debug iOS memory leaks and performance regressions inside your agent with memgraph cycles, Instruments-style traces, and SourceKit-LSP context.
Overview
MemoryDetective is a MCP server for the Ship phase that debugs iOS memory leaks and performance via memgraph cycles, .trace analysis, and SourceKit-LSP bridging.
What is this MCP server?
- iOS-focused leak and performance debugging over MCP
- Memgraph cycle detection for retain graphs and memory issues
- .trace file analysis for performance investigation
- SourceKit-LSP bridging so agents reason with Swift/UIKit context
- npm stdio package memorydetective v1.9.0
- npm package memorydetective version 1.9.0
- stdio MCP transport
- 3 core capabilities: memgraph cycles, .trace analysis, SourceKit-LSP bridge
Community signal: 11 GitHub stars.
What problem does it solve?
Indie iOS devs struggle to turn memgraphs and trace files into fixable retain-cycle and perf issues without bouncing between Instruments and the editor alone.
Who is it for?
Solo iOS engineers on macOS using Claude Code or Cursor who already profile with Instruments and want agent-assisted interpretation of leaks and traces.
Skip if: Web-only or Android-only projects, beginners without Xcode profiling basics, or teams that do not store memgraph/.trace outputs locally.
What do I get? / Deliverables
After adding the stdio server, your agent can ingest memgraph and trace artifacts plus LSP context to propose targeted Swift fixes before you ship.
- Agent-readable analysis of retain cycles and trace hotspots
- Actionable Swift/UIKit fix suggestions tied to LSP project context
Recommended MCP Servers
Journey fit
Ship perf work is where leak-free, responsive iOS builds gate release; MemoryDetective exposes native debugging artifacts to the agent before you call a build done. Perf subphase covers profiling and leak analysis rather than security review, App Store copy, or production incident response.
How it compares
iOS profiling and leak-analysis MCP, not a cross-platform APM SaaS or generic linter skill.
Common Questions / FAQ
Who is MemoryDetective for?
Solo and indie iOS developers who profile memory and performance in Xcode and want agents to analyze memgraphs, traces, and Swift LSP context.
When should I use MemoryDetective?
Use it during Ship perf hardening when retain cycles, memory growth, or trace hotspots block release-quality builds.
How do I add MemoryDetective to my agent?
Install the memorydetective npm MCP package, configure stdio in your agent on macOS with Xcode/SourceKit available, and pass memgraph or .trace artifacts into agent prompts.