Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Cognitive memory for AI coding assistants — persistent memory across sessions
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"memorykit": {
"command": "npx",
"args": [
"-y",
"memorykit-mcp-server"
]
}
}
}Run this in your terminal
claude mcp add memorykit -- npx -y memorykit-mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"memorykit": {
"command": "npx",
"args": [
"-y",
"memorykit-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"memorykit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"memorykit-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account rapozoantonio, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.4.2) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Enterprise-grade, neuroscience-inspired memory infrastructure for LLM applications
_Because your AI shouldn't have the memory of a goldfish_ 🐠
Quick Start · Documentation · Architecture · API Docs
Modern LLMs like GPT-4 and Claude have a critical flaw: they're stateless. Every conversation requires reloading the entire context, leading to:
User (Turn 1): "My name is John, I prefer Python"
AI: "Nice to meet you, John!"
[New session - memory wiped 🧹]
User (Turn 50): "What's my favorite language?" AI: "I don't have that information" ❌
The Cost Problem:
For a typical enterprise chatbot with 100-turn conversations:
| Approach | Tokens/Query | Cost/Query | Monthly (10K users) |
|---|---|---|---|
| Naive (full context) | 50,000 | $1.50 | $750,000 💸 |
| MemoryKit | 800 | $0.024 | $12,000 ✨ |
| You Save | 98.4% | 98.4% | $738,000/month 🎯 |
MemoryKit solves this. Inspired by how the human brain actually works.
Humans don't recall every conversation verbatim. Instead, we use a hierarchical memory system:
| Brain Region | Function | Duration | What It Stores |
|---|---|---|---|
| Prefrontal Cortex | Working Memory | Seconds-Minutes | Active conversation (7±2 items) |
| Hippocampus | Encoding & Indexing | Hours-Days | Recent experiences, decides what to keep |
| Neocortex | Semantic Memory | Months-Years | Facts, concepts, knowledge |
| Amygdala | Emotional Tagging | - | Importance scoring ("remember THIS!") |
| Basal Ganglia | Procedural Memory | Years | Skills, habits, routines |
┌──────────────────────────────────────────────────────────────┐
│ PREFRONTAL CONTROLLER │ │ (Executive Function & Planning) │ │ "Which memory layers do I need for this query?" │ └────────────────────┬─────────────────────────────────────────┘ │ ┌────────────┴────────────┐ │ │ ┌────▼─────┐ ┌─────▼──────┐ │ AMYGDALA │ │ HIPPOCAMPUS│ │ Emotion │ │ Indexing │ │ Tagging │ │ │ └────┬─────┘ └─────┬──────┘ │ │ └────────────┬────────────┘ │ ┌───────────────┴────────────────────────────┐ │ │ ┌────▼─────────┐ ┌──────────────┐ ┌───────────────┐ ┌────────────────┐ │ Layer 3 (L3) │ │ Layer 2 (L2) │ │ Layer 1 (L1) │ │ Layer P (LP) │ │──────────────│ │──────────────│ │───────────────│ │────────────────│ │ WORKING │ │ SEMANTIC │ │ EPISODIC │ │ PROCEDURAL │ │ MEMORY │ │ MEMORY │ │ MEMORY │ │ MEMORY │ │ │ │ │ │ │ │ │ │ Redis Cache │ │ Table │ │ Blob + │ │ Pattern │ │ 10 recent │ │ Storage │ │ AI Search │ │ Matching │ │ messages │ │ Facts & │ │ Full convo │ │ Learned │ │ │ │ Entities │ │ history │ │ routines │ │ │ │ │ │ │ │ │ │ < 5ms │ │ ~30ms │ │ ~120ms │ │ ~50ms │ └──────────────┘ └──────────────┘ └───────────────┘ └────────────────┘
The Prefrontal Controller decides which layers to query based on intent:
"Continue..." → L3 only (500 tokens, <5ms)
"What's my name?" → L2 + L3 (800 tokens, ~30ms) "Quote me from last week" → L1 + L2 + L3 (2000 tokens, ~150ms) "Write code as I prefer" → LP + L3 (600 tokens, ~50ms)
Result: You only load what you need, when you need it. Just like a human brain.
| Feature | MemoryKit | Mem0 | Letta | LangChain |
|---|---|---|---|---|
| Language | .NET 9 | Python | Python | Python |
| Architecture | Brain-inspired | Vector DB | Hierarchical | Flat |
| Procedural Memory | ✅ Yes | ❌ No | ⚠️ Basic | ❌ No |
| Cost Reduction | 98-99% | 85-90% | 80-85% | 60-70% |
| Query Planning | ✅ Intelligent | ❌ Static | ⚠️ Basic | ❌ Static |
| Emotional Weighting | ✅ Amygdala | ❌ No | ❌ No | ❌ No |
| Enterprise Ready | ✅ Day 1 | ⚠️ Partial | ❌ No | ⚠️ Partial |
| Azure Native | ✅ Yes | ❌ Generic | ❌ Generic | ❌ Generic |
🧠 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
# Clone and build
git clone https://github.com/rapozoantonio/memorykit.git cd memorykit dotnet restore && dotnet build
dotnet run --project src/MemoryKit.API
start https://localhost:5001/swagger
// Create conversation
POST /api/v1/conversations { "userId": "user_123", "title": "My Coding Session" }
// Add messages POST /api/v1/conversations/{id}/messages { "role": "user", "content": "I prefer Python with type hints" }
// Later... Query with memory POST /api/v1/conversations/{id}/query { "question": "Write a hello world function as I prefer" }
// MemoryKit automatically: // ✅ Remembers your Python preference // ✅ Remembers you like type hints // ✅ Applies procedural memory pattern // ✅ Uses only 600 tokens (not 50,000!)
👉 See [QUICKSTART.md](docs/QUICKSTART.md) for detailed setup.
┌─────────────────────────────────────────┐
│ API Layer (REST + Controllers) │ └─────────────────┬───────────────────────┘ │ depends on ↓ ┌─────────────────▼───────────────────────┐ │ Application (CQRS + Use Cases) │ └─────────────────┬───────────────────────┘ │ depends on ↓ ┌─────────────────▼───────────────────────┐ │ Domain (Entities + Business Logic) │ ← No Dependencies! └─────────────────▲───────────────────────┘ │ implements ↑ ┌─────────────────┴───────────────────────┐ │ Infrastructure (Azure + Semantic Kernel)│ └─────────────────────────────────────────┘
Just like humans consolidate memories during sleep, MemoryKit runs background consolidation:
New Message → Working Memory (L3) → Importance Scoring (Amygdala)
↓ ┌──────────────────┴───────────────────┐ │ │ High Importance? Low Importance? │ │ ↓ ↓ Extract Facts → Semantic (L2) Discard after TTL Archive Full → Episodic (L1) Detect Patterns → Procedural (LP)
| Operation | Target | Actual (p95) |
|---|---|---|
| Working Memory Read | < 5ms | 3ms ✅ |
| Semantic Search | < 30ms | 25ms ✅ |
| Episodic Search | < 120ms | 95ms ✅ |
| Full Context Assembly | < 150ms | 135ms ✅ |
| End-to-End with LLM | < 2s | 1.8s ✅ |
✅ 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)
✅ 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
✅ GDPR-compliant deletion ✅ Multi-tenancy isolation ✅ Comprehensive audit logging ✅ Performance benchmarks (BenchmarkDotNet) ✅ Security hardening (OWASP compliance)
Backend
Azure Services
Architecture
Testing & Quality
We'd love your help making MemoryKit even better!
# Fork and clone
git clone https://github.com/YOUR_USERNAME/memorykit.git cd memorykit
git checkout -b feature/amazing-feature
dotnet test
git commit -m "feat: add amazing feature"
git push origin feature/amazing-feature
Only the beginning is shown; read the rest in the repo