Memorydetective vs Figma Context MCP

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
M
Memorydetective
carloshpdoc
💻 Developer Tools
F
💻 Developer Tools
SummaryiOS leak hunting and performance investigation. Reads .memgraph (leaks(1)) and .trace (xctrace) files, classifies retain cycles against a 34-pattern catalog (SwiftUI, Combine, Swift Concurrency, UIKit, Core Animation, Core Data, SwiftData, RxSwift, Realm), surfaces a Swift fixTemplate snippet for each match, and bridges to source via SourceKit-LSP. Single-call build+boot+launch fixes the macOS 26.x leaks --outputGraph regression; replayScenario + captureScenarioState close the verify-fix loop. 31 MCP tools, 34 catalog resources, 5 investigation prompts. CI-gateable via verifyFix and compareTracesByPattern. Apache 2.0.Provide coding agents direct access to Figma data to help them one-shot design implementation.
Quality signal24/100 (Emerging)29/100 (Emerging)
Install pathnpx · lowRemote · high
Engagement 1 0 0 0 0 0 15,565
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView MemorydetectiveView Figma Context MCP
More alternatives to MemorydetectiveMore alternatives to Figma Context MCPDeveloper Tools category

Other servers like Memorydetective