Agentkits Memory vs Sessionmem — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agentkits Memory vs Sessionmem
In-depth architectural comparison of the Agentkits Memory and Sessionmem 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
Agentkits Memory
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Sessionmem
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Agentkits Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Sessionmem 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 Agentkits Memory 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: 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.
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: Local SQLite storage of session memories, Automatic summary generation of key session points, Context injection at the start of new sessions.
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.
Local-first memory layer for AI coding assistants. Watches your coding sessions and injects a compact summary at the start of each new session. No cloud, no account, just a SQLite file on your machine. Works with Claude Code, Cursor, Cline, Windsurf, and any other MCP host.
Category & Scope
Tools & Capabilities Breakdown
Agentkits Memory Tools (6)
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
Background workers for AI enrichment and data compression
Web viewer UI for browsing, searching, and editing memories
Cross-platform compatibility with multiple AI coding MCP clients
Sessionmem 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).
Agentkits Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Sessionmem belongs to Knowledge & Memory using local stdio subprocess. Select Agentkits Memory when you need capabilities focused on knowledge & memory and Sessionmem when you require tools for knowledge & memory.