Memory Store (now MemStore)
Renamed MemStore (memory.store now redirects to mem.store); YC Spring 2026. Shared memory layer delivered as an MCP server: a team's AI agents record decisions/progress across sessions and recall from teammates' stores with sources attached; daily email rollup.
Renamed · Verified 2026-10-23 · fresh as of 2026-10-23 · 25 cited facts, 14 with a third-party source · 2 recorded changes · Suggest a correction
At a glance
- Type
- Cross-agent shared episodic + preference memory third-party fix
- Tier
- T2
- Section
- Dedicated memory layers
- Created
- searched not found fix
- Latest release
- not applicable — not OSS fix
- License
- not applicable — not OSS fix
- GitHub
- not applicable — no GitHub repo fix
- Pricing
- $150 per team member/mo after 7-day trial (single plan) vendor fix
- Funding
- searched not found fix
- Freshness
- 2026-10-23 fix
- Layer
- agent-infra repo fix
- Licensing
- commercial vendor fix
- Protocols
- mcp-server vendor fix
Memory taxonomy
- storage
- vector
- retrieval
- similarity
- persistence
- cross-session
- update
- extraction
- unit
- episode
- governance
- opaque
- conflict
- none
When to use
Optimised for: cross-agent shared episodic + preference memory
Anti-fit: searched not found
Pros & cons
Pros
Lightweight key-value memory abstraction; minimal complexity for simple agents.
Cons
Limited capability ceiling; not appropriate for sophisticated agent memory needs.
Claims & capabilities
YC P26. Very early stage.
Technical surface
- API surface
- searched not found
- Backend storage
- searched not found
- Deployment
- Managed-only (hosted; no self-host option documented)
- Embedding model
- searched not found
- Multi-tenancy
- searched not found
- MCP
- yes — is an MCP server (checkin/record/recall tools) at mem.store/mcp for Claude, Claude Code, ChatGPT, Codex, any MCP client
- A2A
- not documented publicly
- OpenTelemetry
- not documented publicly
Alternatives to Memory Store (now MemStore) → live options ranked by shared design, licence, hosting and MCP support
Similar systems
Other dedicated memory layers in the catalog, ranked by inbound references.
- Mem0 T1
Universal memory layer for AI agents. Three concurrent stores (vector + graph + KV); LLM-extracted facts; concurrent retrieval via ThreadPoolExecutor.
- Zep & Graphiti T1
Bi-temporal knowledge graph (event time + ingestion time). Strong on chronological reasoning and contradiction tracking. Graphiti is the open-source core.
- Cognee T1
"Extract–Cognify–Load" pipeline that turns raw input into a typed, queryable knowledge graph for agent recall.
- Hindsight (Vectorize) T1
Standalone memory service from Vectorize. Open source. Biomimetic four-network design (World, Bank, Observation, Opinion). Ships an MCP memory server.
- Letta / MemGPT T1
Originated as MemGPT (UC Berkeley), where the model pages its own memory between context, recall and archival tiers. The product now centres on Letta Code, a stateful agent harness whose agents rewrite their own memory, skills and prompts over time.
- Memori T2
Structured, persistent memory layer for AI agents. Open source.
Sources (24 cited facts, 14 third-party)
Each fact links to the page it came from; the badge says who published it (how to read sources).
- What it is Cross-agent shared episodic + preference memory third-party
- What it does & what's distinct Renamed MemStore (memory.store now redirects to mem.store); YC Spring 2026. Shared memor… vendor
- Claims / benefits YC P26. Very early stage. third-party
- Modalities text third-party
- Pricing $150 per team member/mo after 7-day trial (single plan) vendor
- Deployment Managed-only (hosted; no self-host option documented) vendor
- Memory volume / scale no scale claim vendor
- Schema evolution schema with migration third-party
- Namespace primitives per-tenant third-party
- Contradiction handling LLM resolves and overwrites third-party
- MCP support yes — is an MCP server (checkin/record/recall tools) at mem.store/mcp for Claude, Claude… vendor
- Integration count 0 third-party
- Orchestration both third-party
- Validated verticals consumer / individual, agent developers (early-stage YC P26) third-party
- Optimised for cross-agent shared episodic + preference memory third-party
- Pros Lightweight key-value memory abstraction; minimal complexity for simple agents. third-party
- Cons Limited capability ceiling; not appropriate for sophisticated agent memory needs. third-party
- Project & sources YC page memory.store third-party
- adoption-accelerator yc-p26 third-party
- architecture-deployment-locus cloud vendor
- licensing-bucket commercial vendor
- positioning-platform-vs-product product vendor
- taxonomy-three-layer-rollup agent-infra repo
- protocol-support mcp-server vendor
What changed
Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)
- 2026-10-23
- Name “Memory Store” → “Memory Store (now MemStore)”
- Homepage “https://www.ycombinator.com/companies/memory-store” → “https://mem.store/”
- 2026-10-22
- Pricing first recorded as “$150 per team member/mo after 7-day trial (single plan)” source
- Deployment first recorded as “Managed-only (hosted; no self-host option documented)” source
- MCP support first recorded as “yes — is an MCP server (checkin/record/recall tools) at mem.store/mcp for Claude, Claude Code, ChatGPT, Codex, any MCP client” source