Browse MCP tools for persistent memory, knowledge graphs, and context management in AI agent workflows.
MCP Memory & Knowledge tools are AI-powered software designed to help developers and teams tackle mcp memory & knowledge-related tasks more efficiently. These tools are typically published as open-source projects on GitHub and can be integrated into existing workflows via MCP (Model Context Protocol), Claude Skills, or standalone agent frameworks. On Agent Skills Hub, we index 10 quality-scored mcp memory & knowledge tools across languages including Python, JavaScript, TypeScript.
In 2026, the AI agent ecosystem is maturing rapidly. MCP Memory & Knowledge tools can significantly boost development efficiency by automating repetitive tasks, reducing human error, and providing intelligent suggestions. The top 3 tools — Dragon-Brain, mcp-knowledge-graph, caura-memclaw — have earned an average of 1,246 GitHub stars, reflecting strong community validation. 9 of the listed tools come with clear open-source licenses, ensuring freedom to use and modify.
When choosing a mcp memory & knowledge tool, consider these factors: 1) Community activity — GitHub stars and recent commit frequency indicate reliability; 2) Integration method — check if it supports MCP, Claude, or your preferred agent framework; 3) Language compatibility — the most common language in this list is Python; 4) Quality score — Agent Skills Hub's composite score evaluates code quality, documentation completeness, and maintenance activity. Our recommendation: start with Dragon-Brain — it ranks highest in both star count and quality score.
Dragon Brain — persistent long-term memory for AI agents via MCP (Model Context Protocol). Knowledge graph (FalkorDB) + vector search (Qdrant) + CUDA GPU embeddings. Works with Claude, Gemini CLI, Cursor, Windsurf, VS Code Copilot. 30 tools, 1121 tests.
MCP server enabling persistent memory for Claude through a local knowledge graph - fork focused on local development
Governed shared memory for AI agent fleets — multi-agent, multi-tenant, MCP-native. Trust tiers, keystone policies, audit trails, knowledge graph, self-improving retrieval. Apache 2.0.
Context engineering for AI agents. ~80% fewer tokens. Fix tool overload. Skills and memory with in-process BM25 retrieval. No vector DB. No embeddings.
Self-evolving memory OS for LLM & AI Agents: ultra-persistent memory, hybrid-retrieval, and cross-task skill reuse, with 35.24% token savings
Your AI has amnesia. Persistent memory and cognitive context for AI. 25 MCP tools. 12ms recall.
Agentic AI memory with Ebbinghaus forgetting curve decay. +16pp better recall than Mem0 on LoCoMo.
Human-like memory for AI agents — semantic, episodic & procedural. Experience-driven procedures that learn from failures. Free API, Python & JS SDKs, LangChain, CrewAI & OpenClaw integrations.
The local-first LLM Wiki: open-source knowledge graph builder, RAG knowledge base, and agent memory store. Built on Andrej Karpathy's pattern. An Obsidian alternative for personal knowledge management, AI second brain, and durable Claude Code / Codex / OpenClaw memory.
| Tool | Stars | Language | License | Score |
|---|---|---|---|---|
| Dragon-Brain | ★ 50 | Python | MIT | 44 |
| mcp-knowledge-graph | ★ 863 | JavaScript | MIT | 52 |
| caura-memclaw | ★ 178 | Python | Apache-2.0 | 45 |
| omega-memory | ★ 170 | Python | Apache-2.0 | 44 |
| ratel | ★ 139 | TypeScript | MIT | 43 |
| MemOS | ★ 10.0k | TypeScript | Apache-2.0 | 50 |
| brain-mcp | ★ 53 | Python | MIT | 38 |
| YourMemory | ★ 248 | Python | — | 44 |
| mengram | ★ 178 | Python | Apache-2.0 | 43 |
| swarmvault | ★ 541 | TypeScript | MIT | 45 |
The top mcp memory & knowledge tools in 2026 are Dragon-Brain, mcp-knowledge-graph, caura-memclaw. Agent Skills Hub ranks 10 options by GitHub stars, quality score (6 dimensions including completeness, examples, and agent readiness), and recent activity. The list is rebuilt every 8 hours from live GitHub data.
Dragon-Brain (50 stars) is the most adopted choice for general mcp memory & knowledge workflows, written in Python. mcp-knowledge-graph (863 stars) is a strong alternative and uses JavaScript instead. Pick by your existing stack: match the language and runtime your team already uses to minimize integration cost. If unsure, start with Dragon-Brain — it has the deepest community and the most examples online.
Avoid pre-built mcp memory & knowledge tools when (1) your use case requires deep customization that the tool's plugin system doesn't support, (2) you have strict compliance requirements that ban third-party dependencies, (3) the tool's maintenance is inactive (last commit >6 months ago), or (4) your data volume is small enough that a 50-line custom script is cheaper than learning the tool. For most production workflows above 100 requests/day, the time savings from a maintained tool outweigh the customization loss.
MCP Memory & Knowledge focuses specifically on browse mcp tools for persistent memory, knowledge graphs, and context management in ai agent workflows. Semantic Search is a related but distinct category — see https://agentskillshub.top/best/semantic-search/ for those tools. The two often appear in the same agent pipeline but solve different problems: choose mcp memory & knowledge when your primary goal is the specific task, and semantic search when the workflow is broader.
For most teams, yes. Dragon-Brain has 50 stars worth of community testing, handles edge cases you haven't thought of, and ships with documentation. Build your own only when (1) your requirements are deeply non-standard, (2) you have a security/compliance reason to avoid OSS dependencies, or (3) the maintenance burden is small enough (<200 lines of code) that you'll save time long-term. The break-even point is usually around 2-3 weeks of dev time saved.
Most mcp memory & knowledge tools listed are open source under permissive licenses (MIT, Apache 2.0). A handful offer paid managed/cloud versions on top of free self-hosted core. Always check the LICENSE file on each tool's GitHub repository before commercial use — some use AGPL or non-commercial restrictions that may not fit your deployment model.