Robrain vs Agentkits Memory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Robrain vs Agentkits Memory
In-depth architectural comparison of the Robrain and Agentkits Memory 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: 49/100 (Fair) | Auth: API Key required
Agentkits Memory
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Robrain if you need specialized Knowledge & Memory tools running via a local process. Choose Agentkits Memory 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.
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: 100% local SQLite database storage with no cloud or API keys, Hybrid search: full-text (FTS5) plus vector embeddings for semantic similarity, Automatic session tracking and context injection via hooks.
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.
Persistent memory for AI coding assistants with hybrid search (FTS5 + vector embeddings), session tracking, automatic context hooks, and web viewer. SQLite-based with no daemon process — works with Claude Code, Cursor, Windsurf, and any MCP client.
Category & Scope
Tools & Capabilities Breakdown
Robrain Tools (6)
Passive capture of session turns and decisions
Structured rejected[] field for vetoed alternatives
Corpus-wide contradiction and stance drift detection
Postgres + pgvector backend for persistent storage
Cross-tool integration with Claude Code, Cursor, Copilot, Codex CLI
Self-hosted or managed cloud deployment options
Agentkits Memory 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).
Robrain is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Agentkits Memory belongs to Knowledge & Memory using local stdio subprocess. Select Robrain when you need capabilities focused on knowledge & memory and Agentkits Memory when you require tools for knowledge & memory.