In-depth architectural comparison of the Memorydetective and Kill Process MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Memorydetective
OS Automation · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Kill Process MCP
OS Automation · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Memorydetective if you need specialized OS Automation tools running via a local process. Choose Kill Process MCP if your workspace requires OS Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Memorydetective when:
You need dedicated capabilities in the OS Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: MEMORYDETECTIVE_SUPPRESS_PLATFORM_ADVISORY.
Primary tools included: Reads leaks(1) .memgraph and xctrace .trace files, Classifies retain cycles with a 34-pattern catalog, Provides fixTemplate Swift code snippets per leak pattern.
iOS 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.
List and terminate OS processes via natural language queries
Tools & Capabilities Breakdown
Memorydetective Tools (6)
Reads leaks(1) .memgraph and xctrace .trace files
Classifies retain cycles with a 34-pattern catalog
Provides fixTemplate Swift code snippets per leak pattern
Bridges to source code via SourceKit-LSP
Includes 42 MCP tools for memory and performance analysis
Supports CI gating with verifyFix and compareTracesByPattern
Kill Process MCP Tools (2)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Memorydetective is categorized under OS Automation and uses a local stdio subprocess. In contrast, Kill Process MCP belongs to OS Automation using local stdio subprocess. Select Memorydetective when you need capabilities focused on os automation and Kill Process MCP when you require tools for os automation.
Lists running processes sorted by CPU or memory with optional name, user, status, CPU/memory thresholds, system-process filtering, sort order and limit
process_kill
Terminates the selected process (with extreme prejudice!)