Axint vs Memorydetective — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Axint vs Memorydetective
In-depth architectural comparison of the Axint 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
Axint
OS Automation · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Memorydetective
OS Automation · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Axint 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 Axint 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: Compiles TypeScript to Swift for Apple platforms, Runs Xcode build and test processes locally, Performs static analysis integrated with Apple tooling.
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.
Apple-native execution layer for AI agents. Compiles TypeScript to validated Swift — App Intents, SwiftUI views, WidgetKit widgets, and full apps. 13 MCP tools, 150 diagnostics, 500 tests.
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
Axint Tools (6)
Compiles TypeScript to Swift for Apple platforms
Runs Xcode build and test processes locally
Performs static analysis integrated with Apple tooling
Generates signed proof receipts without uploading source
Supports deterministic code rewrites and repair loops
Provides detailed diagnostics and fix packets
Memorydetective Tools (6)
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).
Axint is categorized under OS Automation and uses a local stdio subprocess. In contrast, Memorydetective belongs to OS Automation using local stdio subprocess. Select Axint when you need capabilities focused on os automation and Memorydetective when you require tools for os automation.