In-depth architectural comparison of the MCP Memory Gateway and Memorylens 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
MCP Memory Gateway
Knowledge & Memory · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Memorylens MCP
Knowledge & Memory · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Memory Gateway if you need specialized Knowledge & Memory tools running via a local process. Choose Memorylens MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Memory Gateway when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: PreToolUse and pre-action checks, Stdio MCP gate_check capability, Local feedback and lesson capture.
Pre-action gates that prevent AI coding agents from repeating known mistakes. Captures explicit feedback, auto-promotes failures into prevention rules, and enforces them via hooks.
⃣ 🏠 🪟 - On-demand .NET memory profiling MCP server. Wraps JetBrains dotMemory with a heuristic rule engine (10 rules) to detect memory leaks, LOH fragmentation, and anti-patterns, providing AI-actionable code fix suggestions.
Category & Scope
Tools & Capabilities Breakdown
MCP Memory Gateway Tools (6)
PreToolUse and pre-action checks
Stdio MCP gate_check capability
Local feedback and lesson capture
Strict enforcement mode
Automatic prevention-rule promotion
Local dashboard and evaluation reports
Memorylens MCP Tools (5)
list_processes
Lists running .NET processes available for profiling, discovered from their diagnostic IPC endpoints
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).
MCP Memory Gateway is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memorylens MCP belongs to Knowledge & Memory using local stdio subprocess. Select MCP Memory Gateway when you need capabilities focused on knowledge & memory and Memorylens MCP when you require tools for knowledge & memory.