In-depth architectural comparison of the Agentkits Memory and Contextforge 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
Agentkits Memory
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Contextforge MCP
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Agentkits Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Contextforge 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 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: SQLite-backed local persistence, FTS5 and vector semantic search, Automatic session and tool-usage capture.
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.
Persistent memory for Claude Code, Cursor, and GitHub Copilot via MCP. Semantic search, Git commit/PR sync, project-based organization, team collaboration. Free tier available. npx contextforge-mcp
Category & Scope
Tools & Capabilities Breakdown
Agentkits Memory Tools (6)
SQLite-backed local persistence
FTS5 and vector semantic search
Automatic session and tool-usage capture
Nine MCP memory-management tools
Local multilingual embeddings
Web viewer for memory administration
Contextforge MCP Tools (41)
memory_ingest
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, Contextforge MCP belongs to Knowledge & Memory using local stdio subprocess. Select Agentkits Memory when you need capabilities focused on knowledge & memory and Contextforge MCP when you require tools for knowledge & memory.