In-depth architectural comparison of the Robrain and A Mem 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
Robrain
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
A Mem MCP
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Robrain if you need specialized Knowledge & Memory tools running via a local process. Choose A Mem 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 Robrain when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: ANTHROPIC_API_KEY, OPENAI_API_KEY, PERCEPTION_API_KEY, POSTGRES_PASSWORD.
Primary tools included: Passive capture of session turns and decisions, Structured rejected[] field for vetoed alternatives, Corpus-wide contradiction and stance drift detection.
Self-hosted decision memory for AI coding agents. Passively captures architectural decisions with the alternatives you rejected (structured rejected[]), then warns the agent before it re-proposes a rejected approach. Postgres + pgvector; cross-tool across Claude Code, Cursor, Copilot, and Codex. Install: npx robrain up && npx robrain install.
Robrain is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, A Mem MCP belongs to Knowledge & Memory using local stdio subprocess. Select Robrain when you need capabilities focused on knowledge & memory and A Mem MCP when you require tools for knowledge & memory.