
Memorykit
io.github.rapozoantonioPublished by GitHub account rapozoantoniov1.4.2Updated Oct 24, 2026
Cognitive memory for AI coding assistants — persistent memory across sessions
Overview
A local MCP server that gives AI coding assistants persistent, layered memory across sessions, so preferences and past context carry over.
- What you can do
- Persist conversation context and user preferences across sessions through a multi-layer memory model (working, semantic, episodic, procedural). Score and consolidate memories by importance, with automatic fact extraction and pattern learning. Plan which memory layers to query based on the intent of a question. The README describes a REST API with conversation, message and query endpoints, but the manifest lists no tools, so the exact MCP tool surface is not documented.
- When to use it
- Worth adding when you want a coding assistant to remember your preferences, past decisions and earlier sessions instead of starting from a blank context each time, and you are willing to run and configure the backing service yourself.
- Requirements
- Runs as a local stdio process from the npm package memorykit-mcp-server, so Node.js is needed. The README describes a .NET 9 backend with Azure services (Redis, Table Storage, Blob Storage, AI Search, Azure OpenAI) and API key authentication; no environment variables or headers are declared in the manifest.
Installation
In SourceWeft
- Open Memorykit in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
🧠 MemoryKit
[CI/CD Pipeline] [License: MIT] [.NET] [PRs Welcome]
Enterprise-grade, neuroscience-inspired memory infrastructure for LLM applications
Because your AI shouldn't have the memory of a goldfish 🐠
🐠 The Goldfish Problem
Modern LLMs like GPT-4 and Claude have a critical flaw: they're stateless. Every conversation requires reloading the entire context, leading to:
The Cost Problem:
For a typical enterprise chatbot with 100-turn conversations:
MemoryKit solves this. Inspired by how the human brain actually works.
🧠 The Neuroscience Solution
Humans don't recall every conversation verbatim. Instead, we use a hierarchical memory system:
The Human Brain Architecture
MemoryKit's Brain-Inspired Architecture
Intelligent Query Planning
The Prefrontal Controller decides which layers to query based on intent:
Result: You only load what you need, when you need it. Just like a human brain.
🎯 What Makes MemoryKit Different?
vs. Existing Solutions
Unique Innovations
🧠 First neuroscience-backed memory system for LLMs
⚡ Procedural memory - learns user workflows and preferences
🎯 Importance scoring - Amygdala-inspired emotional tagging
🏗️ Clean Architecture - Enterprise-grade from day one
💰 Highest cost savings - 98-99% reduction vs. naive approaches
🔒 Production-hardened - Security, monitoring, rate limiting built-in
🚀 Quick Start
Your First Query
👉 See QUICKSTART.md for detailed setup.
🏗️ Architecture Highlights
Clean Architecture
Memory Consolidation (Sleep-Inspired)
Just like humans consolidate memories during sleep, MemoryKit runs background consolidation:
📊 Performance & Scale
Latency Targets (All Met ✅)
Production Scale
- 10,000+ concurrent conversations
- 1,000+ messages/second
- 500+ queries/second
- Total infrastructure cost: ~$453/month (for 10K users)
🎨 Core Features
Memory Operations
✅ Multi-layer storage (Working, Semantic, Episodic, Procedural)
✅ Intelligent query planning (Prefrontal Controller)
✅ Importance scoring (Amygdala Engine)
✅ Automatic fact extraction
✅ Pattern learning and matching
✅ Memory consolidation (background jobs)
Production-Ready
✅ API key authentication
✅ Rate limiting (fixed, sliding, concurrent)
✅ Health checks (live, ready, deep)
✅ Application Insights monitoring
✅ Docker + Docker Compose
✅ Azure Bicep IaC templates
✅ CI/CD with GitHub Actions
Enterprise Features
✅ GDPR-compliant deletion
✅ Multi-tenancy isolation
✅ Comprehensive audit logging
✅ Performance benchmarks (BenchmarkDotNet)
✅ Security hardening (OWASP compliance)
📚 Documentation
Getting Started
- Quick Start - 5-minute setup guide
- Project Status - Current state & roadmap
- Contributing - How to contribute
- Changelog - Version history
Technical Deep-Dives
- Architecture - System design & patterns
- Cognitive Model - Neuroscience mappings
- Scientific Overview - Research background
- API Reference - REST endpoints & SDK
- Deployment - Azure production setup
- Development Guide - Contributor workflow
🔧 Technology Stack
Backend
- .NET 9.0 (C# 13)
- ASP.NET Core Web API
- MediatR (CQRS)
- FluentValidation
Azure Services
- Redis Cache (Working Memory)
- Table Storage (Semantic/Procedural)
- Blob Storage + AI Search (Episodic)
- Azure OpenAI (Embeddings + LLM)
Architecture
- Clean Architecture
- Domain-Driven Design
- SOLID Principles
- Dependency Injection
Testing & Quality
- xUnit (Unit/Integration tests)
- BenchmarkDotNet (Performance)
- Moq (Mocking)
- FluentAssertions
🤝 Contributing
We'd love your help making MemoryKit even better!
Quick Start for Contributors
Resources for Contributors
- CONTRIBUTING.md - Guidelines & code of conduct
- DEVELOPMENT_GUIDE.md - Development workflow
- Architecture Docs - System design
- PROJECT_STATUS.md - What needs work
📈 Project Status
Version: 1.0.0
What's Complete ✅
- ✅ Four-layer memory architecture
- ✅ Neuroscience-inspired cognitive components
- ✅ Clean Architecture (zero circular dependencies)
- ✅ CQRS with MediatR
- ✅ In-memory implementations
- ✅ REST API with Swagger
- ✅ Production hardening (auth, rate limiting, monitoring)
- ✅ Comprehensive documentation
What's Next 🚧
- ⚠️ Azure service implementations (Redis, Tables, Blob, AI Search)
- ⚠️ Real Azure OpenAI integration
- ⚠️ Comprehensive test coverage
- 📋 Client SDKs (.NET, Python, JS)
- 📋 Background consolidation jobs
- 📋 Advanced analytics dashboard
See PROJECT_STATUS.md for full details.
🎓 Learn More
Research & Inspiration
MemoryKit is built on decades of cognitive neuroscience research:
- Baddeley & Hitch (1974) - Working memory model
- Tulving (1972) - Episodic vs. semantic memory
- Squire (2004) - Memory systems of the brain
- McGaugh (2000) - Memory consolidation
- Miller (1956) - The magical number 7±2
See docs/SCIENTIFIC_OVERVIEW.md for the full scientific background.
Why This Matters
Traditional LLM memory solutions treat memory as a flat vector database. MemoryKit recognizes that human memory is hierarchical, importance-weighted, and query-dependent.
By mimicking how the brain actually works, we achieve:
- Better relevance - Only retrieve what matters
- Lower cost - Don't load irrelevant history
- Faster response - Parallel layer retrieval
- Procedural learning - Remember user preferences
- Emotional context - Important messages remembered better
🔒 Security
We take security seriously:
- API Key Authentication - Secure access control
- Rate Limiting - Prevent abuse
- Input Validation - Prevent injection attacks
- HTTPS Only - Encrypted in transit
- Azure Security - Encryption at rest
- GDPR Compliant - User data deletion
- Regular Scans - Trivy + CodeQL
See SECURITY.md for security policy and reporting.
📝 License
This project is licensed under the MIT License - see LICENSE for details.
TL;DR: Free to use commercially, modify, distribute. Just keep the copyright notice.
🌟 Show Your Support
If MemoryKit helps your project, please consider:
- ⭐ Star this repo on GitHub
- 🐦 Tweet about it - help others discover it
- 📝 Write a blog post - share your experience
- 🤝 Contribute - PRs are welcome!
- 💬 Provide feedback - open an issue or discussion
📞 Contact & Support
- 📧 Email: [email protected]
- 🐛 Issues: GitHub Issues
- 💬 Discussions: GitHub Discussions
- 📖 Documentation: docs/
- 🔒 Security: [email protected]
🎯 Ready to give your AI a real memory?
Get Started · Read the Docs · Join the Discussion
Made with 🧠 and ❤️ by Antonio Rapozo
Inspired by 50+ years of cognitive neuroscience research
Source: README.md at commit 35e85fa
Tools
0Version history
1- v1.4.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts