MIND vs — ComparisonMIND vs MemGPT
Memory any AI can read vs Historic agent-memory framework — now maintained as Letta
The research project and open-source framework (2023) that first proposed OS-inspired virtual context management for LLM agents — paging facts between a small always-visible context and larger recall/archival storage. The codebase is now maintained as Letta.
By Anthony Conti, Astra AI, LLC · Last updated September 7, 2026 · Facts about MemGPT sourced from its own site — see Sources below.
Side-by-side
| Capability | MIND | MemGPT |
|---|
| Self-hosting | By request only — VPC or fully air-gapped for regulated/enterprise customers, not a self-serve download | The original MemGPT project is archived; its living code is now Letta, which is Apache 2.0 and free to self-host |
| API / SDK surface | REST API + a native MCP server + a TypeScript client — every tool maps 1:1 to a REST endpoint | Historic: a Python framework for OS-inspired virtual context management. Current: Letta's SDK plus its ADE |
| MCP support | Yes — MCP is the primary integration surface, not an add-on | Not part of the original MemGPT paper/repo; its successor Letta supports MCP |
| Storage model | Knowledge graph plus vector retrieval, unified — you don't choose one or the other | The idea that started it all — tiered memory (core context, recall storage, archival storage) managed by the agent via function calls, like an OS paging memory in and out |
| Open source | No — the graph engine is closed; the MCP client SDK is open | Yes — was and remains open source, now maintained as Letta |
| End-user product on top | Yes — a mobile app, a web app, and daily use by a person, not just a service other software calls | No |
| Free tier | Yes — a real free tier for a person's own memory, not a metered trial credit | N/A — free and open source; the maintained fork, Letta, is likewise free to self-host |
What MemGPT is
The research project and open-source framework (2023) that first proposed OS-inspired virtual context management for LLM agents — paging facts between a small always-visible context and larger recall/archival storage. The codebase is now maintained as Letta.
• Introduced the core/recall/archival memory-tier model for LLM agents
• Agent-triggered function calls to page memory in and out of context, like an OS managing RAM
• Original repository now archived; active development moved to Letta
• The MemGPT name is still what most people search for the underlying idea
• Concepts carried forward into Letta's self-editing memory blocks
The honest comparison
If you're reading this page, you're probably searching MemGPT out of habit — it's still the name a lot of the agent-memory conversation uses, even though the project itself has been renamed and folded into Letta. The idea MemGPT introduced in 2023 is worth understanding on its own terms, separate from whatever the current product is called: LLMs have a small, fixed context window, so treat that window the way an operating system treats RAM — keep the most relevant things in core context, and let the agent explicitly page other facts in from recall and archival storage via function calls when it needs them. That's a genuinely elegant answer to a real constraint, and a huge share of what agent memory means today traces back to that paper.
What's changed since is mostly branding and maturity, not the core idea: the original repository is now effectively a landing page pointing to Letta, where the OS-inspired memory tiers live on as self-editing memory blocks with a real product, an ADE for visual debugging, and Apache 2.0 self-hosting. MIND didn't descend from this lineage at all — it wasn't built to solve an LLM's context-window constraint, it was built to be a person's memory that any model can read. Those are related problems, both are versions of how do you not lose what mattered when context is limited or resets, but MIND's answer doesn't involve an agent explicitly deciding to page a fact in or out; it decides what mattered when you add it, the way your own memory works, not the way a paging algorithm works.
So the honest version of MIND versus MemGPT is really two comparisons in one: against the original research idea, MIND is a different design philosophy, automatic and person-facing rather than agent-managed and developer-facing. Against what MemGPT actually is today, the fair comparison to run is MIND versus Letta, which is its own page on this site with current pricing and features, because that's where the maintained code and the real product both live now.
How MIND is different
MemGPT was a research idea about paging memory in and out of context. MIND is a shipped product a person uses every day, with that same don't-lose-what-mattered problem solved differently.
If you're looking for MemGPT today, you're looking for Letta — the maintained fork. MIND isn't a fork of anything. it's a separate approach built for a person's memory, not an agent's context window.
MemGPT's tiered-memory idea assumes a developer designs the tiers. MIND assumes nobody wants to design tiers, and works out what belongs where on its own.
When MemGPT is the better choice
If you found this page because you specifically want the framework MemGPT described — open-source, self-hosted, OS-inspired memory tiers a developer configures — go to Letta, its maintained successor. That's genuinely the right tool for building an agent with that model of memory, and it's free to self-host.
Moving between the two
There's no migration path from the archived MemGPT repository itself; anyone still running the original code should look at Letta's own migration guidance first, since that's where active maintenance lives. From either, memory content exported as text imports into MIND as documents the same way any other memory-tool export does.
Frequently asked
What's the difference between MIND and MemGPT?
MemGPT was a research idea about paging memory in and out of context; MIND is a shipped product a person uses every day, with that same don't-lose-what-mattered problem solved differently.
Can I use MIND alongside MemGPT?
Yes, and plenty of people do. MIND is the memory underneath — the thing Claude and ChatGPT read from — so it sits alongside MemGPT rather than replacing it.
Is MIND a MemGPT alternative?
Not exactly. Both help you get things down. The difference is what happens next: whichever AI you open tomorrow can read your MIND, and it comes with you when you change your mind about models.
How does MIND's pricing compare to MemGPT?
MIND has a free tier and paid plans built around one person's memory, not metered API calls. MemGPT's current pricing: Free and open source (the original repository); its maintained successor, Letta, is likewise Apache 2.0 and free to self-host, with an optional paid managed cloud. Check MemGPT's own pricing page, linked in Sources below, for the latest numbers — pricing in this space changes often.
Sources
MemGPT pricing: Free and open source (the original repository); its maintained successor, Letta, is likewise Apache 2.0 and free to self-host, with an optional paid managed cloud. Details about other apps come from their own public pages; features and prices change, so check theirs before deciding.
Related reading
One memory. Every AI.
MIND is the persistent knowledge graph your AI reads from — across every model and agent you use. Start free.
Try MIND free →