Memory Mcp
Give Claude Code or Cursor persistent Letta-backed memory so long-running agent projects remember users, decisions, and context across sessions.
Overview
com.letta/memory-mcp is a MCP server for the build phase that manages persistent AI memory through Letta via standard stdio MCP tools.
What is this MCP server?
- Standard MCP memory tools backed by Letta’s memory management API
- npm package @letta-ai/memory-mcp version 2.0.2 with stdio transport
- Required LETTA_API_KEY and optional LETTA_USER_ID for per-user memory scopes
- Open-source memory-mcp repo on GitHub under letta-ai
- Fits multi-session coding agents that must recall preferences and project facts
- Package version 2.0.2
- Transport: stdio via npm @letta-ai/memory-mcp
- LETTA_API_KEY required; LETTA_USER_ID optional
What problem does it solve?
Coding agents forget project context between sessions, forcing solo builders to repeat constraints and re-paste specs on every run.
Who is it for?
Indie builders shipping personal agents, support bots, or long-horizon Claude Code projects that need Letta-backed recall.
Skip if: Teams that only need ephemeral chat with no persistence, or builders unwilling to run a local stdio MCP process and manage Letta API keys.
What do I get? / Deliverables
After installing the Letta memory MCP with your API key, agents read and write durable memories so multi-day builds stay consistent without manual context dumps.
- MCP tools for storing and retrieving Letta-managed memories
- Per-user memory isolation when LETTA_USER_ID is set
- Repeatable local MCP config for agent projects
Recommended MCP Servers
Journey fit
Memory MCP servers sit in build agent-tooling because solo builders attach them while shaping autonomous agents, not when drafting a landing page. Agent-tooling is correct: npm package @letta-ai/memory-mcp runs stdio locally and syncs memory operations to Letta with API keys.
How it compares
Letta-backed memory MCP stdio server, not a journey-wide planning skill or hosted-only search remote.
Common Questions / FAQ
Who is com.letta/memory-mcp for?
It is for solo developers and agent builders who use Letta and want standard MCP memory tools inside Claude Code, Cursor, or other stdio-capable clients.
When should I use com.letta/memory-mcp?
Use it during build when your agent product needs cross-session memory for users, projects, or decisions instead of stuffing everything into the context window.
How do I add com.letta/memory-mcp to my agent?
Install @letta-ai/memory-mcp from npm, set LETTA_API_KEY and optional LETTA_USER_ID in the MCP server env, and register the stdio server in your client’s MCP configuration.