Agent Device vs Memorydetective — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agent Device vs Memorydetective
In-depth architectural comparison of the Agent Device and Memorydetective 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
Agent Device
OS Automation · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Memorydetective
OS Automation · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Agent Device if you need specialized OS Automation tools running via a local process. Choose Memorydetective 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 Agent Device 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).
Primary tools included: Cross-platform support for iOS, Android, tvOS, macOS, Linux, and web, Accessibility tree snapshots with token-efficient element references, UI actions including press, fill, scroll, wait, and alert handling.
Discovery router for the agent-device CLI. Exposes status, install guidance, version-matched help, prompts, and resources for iOS, Android, tvOS, macOS, and Linux automation workflows.
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.
Tools & Capabilities Breakdown
Agent Device Tools (5)
Cross-platform support for iOS, Android, tvOS, macOS, Linux, and web
Accessibility tree snapshots with token-efficient element references
UI actions including press, fill, scroll, wait, and alert handling
Evidence capture: screenshots, video, logs, traces, and network data
Replayable workflows with script export and integration with agent terminals
Memorydetective Tools (6)
Reads leaks(1) .memgraph and xctrace .trace files
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).
Agent Device is categorized under OS Automation and uses a local stdio subprocess. In contrast, Memorydetective belongs to OS Automation using local stdio subprocess. Select Agent Device when you need capabilities focused on os automation and Memorydetective when you require tools for os automation.
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.