All MCP Servers
AI & MemoryMCP RegistrynpmB · 63

memory-mcp

com.letta · Updated

MCP server for AI memory management using Letta - Standard MCP format

At a glance

memory-mcp is an MCP server in the AI & Memory category. It runs locally over stdio via `npx -y @letta-ai/memory-mcp`, and needs LETTA_API_KEY. It scores B (63/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install memory-mcp in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install memory-mcp in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add memory-mcp -e 'LETTA_API_KEY=<LETTA_API_KEY>' -- npx -y @letta-ai/memory-mcp
  2. Fill in your credentials

    Replace <LETTA_API_KEY> with your real value. Keep secrets out of any config file you commit.

  3. Verify it's connected

    bash
    claude mcp list
  4. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  5. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What does memory-mcp need from you?

API key — Letta API key for memory operations

  • LETTA_API_KEYrequiredsecretEnvironment variable

    Letta API key for memory operations

  • LETTA_USER_IDoptionalEnvironment variable

    Unique user identifier for associated memories

Pass secrets through your shell environment rather than committing them into a config file.

What tools does memory-mcp expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Read from the published package source — never executed. Parsed 1 of 1 source file.

This server can read your environment variables.

How it was published

  • No provenance attestation — there is nothing linking this published artifact to a specific source commit.
  • 4 npm maintainers · last published by sarahwooders.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Package last published 1 year ago — No release in over a year.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 63

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%not measurable

    No commit history available.

  • Adoption20%not measurable

    No usage data available.

  • Transparency20%25%

    1/4: ✓ public source repo, ✗ declared license, ✗ documentation, ✗ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%100%

    Publishes a pinned version (2.0.2).

Maintain memory-mcp? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![memory-mcp on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/com-letta-memory-mcp)](https://mcp-skills-hub.vercel.app/mcps/com-letta-memory-mcp)

Catalog data refreshed . Something wrong? Report it.