Skip to main content
Most AI tools forget you the moment the tab closes. You re-explain preferences, restate project context, and re-teach the same lessons in Claude, Cursor, ChatGPT, and everything else. Supermemory MCP is a single memory layer that plugs into any MCP-compatible client. Connect once, and the same long-term memory follows you across tools — coding agents, chat apps, IDEs, and whatever you add next.

What you get

  • Unified memory across tools — Facts you save in Claude are available in Cursor (and vice versa). One brain, many surfaces.
  • Memory that compounds — Preferences, decisions, and project knowledge accumulate instead of resetting every session.
  • Profiles that stay current — Supermemory builds a living user profile from what you share, so assistants start with who you are — not a blank slate.
  • Project-scoped context — Keep work, personal, and client work separate with optional project tags.
  • Works where you already work — Claude (Connectors), Cursor, Windsurf, VS Code, Cline, and any client that speaks MCP.

Why a small tool surface is intentional

Supermemory MCP exposes a minimal set of tools on purpose. Assistants don’t need a kitchen-sink API to remember well. They need a few durable actions: save what matters, recall what’s relevant, and know who the user is. Fewer tools means less confusion for the model, clearer behavior, and more reliable use in production. That’s enough for agents to build real continuity — without tool sprawl.

How it fits together

  1. You connect your client to https://mcp.supermemory.ai/mcp (OAuth or API key).
  2. During conversations, the model stores important facts with memory.
  3. When context is needed, recall (and the profile) pull the right history back in.
  4. Switch tools tomorrow — same account, same memory.
Under the hood, the server runs on Cloudflare Workers with Durable Objects for scalable, sticky sessions. Your data is isolated per account; open-source implementation is on GitHub.

Connect

Server URL:
Add it to your MCP client config:
The server uses OAuth by default. Your client discovers the authorization server via /.well-known/oauth-protected-resource and prompts you to sign in. For Claude (Settings → Connectors), see Claude Desktop. For client-specific examples, see Setup and Usage.

API Key Authentication (Alternative)

If you prefer API keys over OAuth, get one from app.supermemory.ai and pass it in the Authorization header:
API keys start with sm_ and skip OAuth when provided.

Project Scoping

Scope all operations to a specific project with x-sm-project:

Tools

memory

Save or forget information about the user.

recall

Search memories and get user profile.

whoAmI

Get the current logged-in user’s information. Returns { userId, email, name, client, sessionId }.

Resources

Prompts

context

Inject user profile and preferences as system context for AI conversations. Returns a formatted message with the user’s stable preferences and recent activity. In Cursor and Claude Code you can often invoke this with /context, which gives the model enough profile context to use and query Supermemory effectively. Purpose: Unlike the recall tool (search for specific information) or the profile resource (raw data), the context prompt is a pre-formatted system message for conversation start. Output format:
  • Instructions to save new memories using the memory tool
  • Stable Preferences: Long-term user facts and preferences
  • Recent Activity: Recent interactions and context (when includeRecent is true)
  • Fallback message when no profile exists yet
When to use:
  • context prompt — automatic system context at conversation start
  • recall tool — search for specific information
  • profile resource — raw profile data for custom processing

Setup and Usage

Client configs, API keys, and project scoping.

MCP Server Source

Open-source implementation.