Blog·Learning

How To Make Your MCP Clients Share Context with Supermemory MCP

By Dhravya Shah·5 min read

Blog cover banner reading "How To Make Your MCP Clients Share Context" beside a stacked pyramid of retro TVs showing eyes

Let’s get practical here: have you ever dropped a PDF into Cursor, then pasted the same content into Claude just to “remind it”? Or tried to follow up on a thread, only to realize the memory lives in a different tool?

It’s annoying. It breaks your flow. And worse, it ruins your results. That’s because your memory is fragmented across tools. You don’t have one shared context; you have partial ones.

But what if your AI tools could share memory? Not just reuse the same prompt, but actually pull from the same brain?

Let’s skip the theory for a second and understand what context sharing actually looks like. You drop a file into Cursor, then ask Claude a follow-up question about it. Claude answers accurately even though it never saw the file. That’s shared memory, and that’s Supermemory.

You don't need to manually copy and paste. No prompts that start with “Recall that...”, all you need is a seamless handoff between your tools, as if they were on the same team. In the next section, we will take a look at how you can make your MCP clients share context using Supermemory.

How to Make Your MCP Clients Share Context Using Supermemory

Most developers and engineers believe this will be challenging, as they will likely need to modify the client source code, set up custom servers, or maintain API bridges between tools. However, with Supermemory, it’s literally plug-and-play.

There are two methods to accomplish this: one-click install or manual install. We will examine both methods.

One-Click Install

If you’re using Cursor, Claude Desktop, VSCode, or other AI clients, Supermemory offers a one-click install that connects your tool directly to your shared memory. You’ll be up and running in less than a minute.

This is the easiest method, simply because you will be using the Supermemory app and will take advantage of one-click installs.

Step 1

Navigate to the login URL (app.supermemory.ai/login) and sign in with your information. You can use either your email or the Google/GitHub authentication.

Supermemory login page with an email field, Google and GitHub sign-in, and the tagline "Your memory, everywhere, with you."

Step 2

You will be redirected to the app dashboard, where you can now proceed to connect Supermemory to your preferred AI tool using the Model Context Protocol (MCP). This enables your AI to interact with your memory and perform actions such as adding, searching, and utilizing it in real-time.

In the setup dashboard, you’ll see options like: Cursor, Claude Desktop, VSCode, Gemini CLI, Claude Code, Cline, or even custom MCP URLs.

Pick the client you want to connect with; let’s say Cursor.

AI client selector listing Cursor, Claude Desktop, VSCode, Cline, Gemini CLI, Claude Code, and an MCP URL option

Step 3

This is a crucial step where you must install the Supermemory MCP. You must click the “Add to Cursor” button, which automatically installs and configures Supermemory in Cursor.

Setup panel with an "Add to Cursor" button to auto-install and configure the Supermemory MCP server

After clicking on the button, you will be prompted to open up Cursor on your local machine to complete the installation.

Cursor's Install MCP Server dialog for supermemory-mcp running npx -y mcp-remote with the Supermemory MCP URL

Click on the install button. After a few minutes, you should have supermemory-mcp installed on your Cursor. The supermemory-mcp comes with four tools, which include: addMemory, search, getProjects, and whoAmI. You can enable and disable any of the tools by clicking on them.

Cursor Tools panel showing the installed supermemory-mcp server with addMemory, search, getProjects, and whoAmI tools

MCP server installation should start in Cursor. If Cursor didn't open automatically, you can manually add the MCP server with the configuration below:

MCP Server Configuration:
{
"supermemory-mcp": {
"command": "npx -y mcp-remote api.supermemory.ai/mcp"
}
}

Manual Installation

If you’re not using the one-click install, don’t worry. The manual setup only takes a minute. With a single command, you can connect Supermemory to your favorite AI tools via the Model Context Protocol (MCP).

Step 1: Pick Your AI Client

Supermemory MCP works out of the box with popular clients like: Cursor, Claude Desktop, VS Code, Gemini CLI, Cline, and Claude Code. You can also use a custom MCP URL if you're running a self-hosted setup.

AI client selector with Cursor chosen among Claude Desktop, VSCode, Cline, Gemini CLI, Claude Code, and MCP URL

Step 2: Install the MCP Adapter

Run the following command in your terminal; you only need to run it once per project.

npx -y install-mcp@latest api.supermemory.ai/mcp --client cursor --oauth=yes

Let’s break that down:

Flag

What It Does

install-mcp@latest

Installs the MCP adapter

api.supermemory.ai/mcp

The URL of the Supermemory MCP endpoint

--client cursor

Tells Supermemory which AI client you're using (e.g., cursor, vscode, claude-desktop, etc.)

--oauth=yes

Enables OAuth flow for authentication

Manual install step showing the npx install-mcp command for the Supermemory MCP with the cursor client and OAuth

What Happens After Installation?

Once installed:

  • Your AI tool can automatically save context as memories.
  • It can pull previous memory snippets when responding to prompts.
  • You’ll get contextual information from your knowledge base.
  • It works seamlessly in the background.

Relationship Inference with Graph Memory

Supermemory doesn’t just store chunks of text. It understands the relationships between people, places, actions, and ideas within your conversations.

Behind the scenes, it builds a knowledge graph from your messages and notes. That means:

  • You can ask, “Who did I talk to about onboarding workflows last week?”
  • Or filter for “All conversations where Mayowa mentioned compliance and Slack”
  • Or see a graph of what your Claude chats, Notion pages, and Gmail threads have in common

This works across all your apps and not just MCPs. Every chat, every tool is logged automatically. No need to remember what you said or where you said it. Just search, and it’s there.

And if you want to forget your memory? You control the retention window, deletion rules, and even encryption scope.Supermemory handles all of this with a unified memory layer.

Conclusion

Most people using Claude, Cursor, or any other modern client are flying half-blind. Every new thread forgets the last. Every tool has its own silo.

But it doesn’t have to be that way. With Supermemory, your MCP clients can share memories, recall important moments, and respond with actual context, not just the last five messages.

Setting it up takes just a few clicks. Works across apps. And gives you back hours of searching, repeating, and re-explaining.

Try it now atapp.supermemory.ai. Or dive deeper into what makes Supermemory tick in thedocs, demo video, andblog.

  1. An update to supermemoryWe've discontinued the supermemory company brain and Nova. Everyone who was charged has been refunded, our MCP and plugins continue to run, and we're going all in on the memory engine.
  2. SMFS: making agentic retrieval 55% cheaper AND more accurateWe launched SMFS.ai (Supermemory Filesystem) a few weeks ago, with a simple bet: We can redesign the filesystem specifically for agents, with special files, structures, and commands that it can use for it's tasks. Today, SMFS is used by hundreds of companies to power their agents.
  3. Introducing Dynamic Dreaming: supermemory now connects the dots, for you.Dreaming is magical. TLDR: We're launching Dynamic Dreaming in supermemory today, which automatically works if you're using supermemory in any way - API, OpenClaw, Hermes agent, etc.
  4. Dear reader, we just made supermemory insanely cheap... the Context CloudWhen I first started building supermemory, I had one goal: To build the best memory system for AI. I would talk to customers, and find out that memory was not the only thing they needed - They were all setting up 7-8 different vendors at the same time.
  5. Introducing @supermemory/tools v2.0.0Today we're releasing v2.0.0. This release unifies the API across all agents sdk integrations from AI SDK to Mastra, makes conversation identity a first-class concept, and ships with memory saving on by default.
  6. supermemory will make your Hermes-agent crazy powerfulToday, we are launching supermemory support to your Hermes agent TLDR: you can use supermemory now in your Hermes agent, it totally free to get started - https://supermemory.ai/docs/integrations/hermes In case you missed it: Hermes Agent is a self-improving AI agent from Nous Research.
  7. Solving the Precision-Recall Tradeoff: Search Result AggregationWhen you're building memory for AI, search is your foundational layer. The way search generally works is straightforward: the user defines a query, and then sets a limit (top-K) on how many search results they want returned. Usually, this is set to 10 or 20.
  8. Infinitely running stateful coding agentsWe built a plugin for Claude Code and OpenCode that gives your coding agent persistent memory. It remembers your preferences, learns your codebase, and never loses context mid-conversation. The result is an agent you can run for months without starting over.
  9. Why everyone is complaining about OpenClaw's memory (it sucks) - and why supermemory fixes it.TLDR: Today, we are releasing a new version of our openclaw plugin - https://github.com/supermemoryai/openclaw-supermemory. This post is going to be a bit technical, so bear with me (or bookmark for later!) In this post, I will talk about what we do about OpenClaw memory, and how we fix it.
  10. We added supermemory to Claude Code. It's INSANELY powerful now...Today, we are launching the Supermemory plugin for Claude Code! TLDR: You can use supermemory in claude code now. - https://github.com/supermemoryai/claude-supermemory Claude code has genuinely changed how I work. But there's this one thing that drives me crazy...
  11. Clawd / Molt bot's memory SUCKS. We gave it supermemory.I'm the founder of supermemory. Clawd/Molt bot is blowing up right now, with many, many use cases. I set it up, too, and have been using it through telegram. TLDR: just go to https://supermemory.ai/docs/integrations/clawdbot to set up supermemory for your clawd bot.
  12. Catch up with our UNFORGETTABLE Launch WeekOver the last year, one belief has guided almost everything we’ve built at Supermemory AI becomes meaningfully useful only when it remembers. Memory shouldn’t be something developers rebuild from scratch. It shouldn’t be fragile, expensive, or trapped inside a single tool.
  13. Empowering the Next Generation of Founders: Supermemory Startup ProgramIf there’s one thing we’ve learned while building Supermemory, it’s that most startups don’t fail because they didn't build features; they fail when infrastructure slows them down, or they built too slow.
  14. Building code-chunk: AST Aware Code ChunkingAt Supermemory, we're building context engineering infrastructure for AI. A huge part of that is dealing with code: ingesting repos, understanding structure, and making it searchable. The problem is that most code chunking solutions are terrible. We built code-chunk to fix this.
  15. Supermemory raises $3 million with the best memory engine for LLMsToday, I am excited to announce our first funding round to accelerate our mission of building an interoperable, scalable and reliable memory for LLMs and agents. Memory is one of the hardest challenges in AI right now.
  16. Unified Memory That Works Where You Work: Your Second Brain With SupermemoryHi everyone, I’m Dhravya, the founder of Supermemory. I want to start with a little story behind why this product means so much to me. You can also skip straight to what it is and how it works below.
  17. Supermemory just got faster on PlanetScaleWhat is Supermemory? Supermemory completes the missing part of the LLM puzzle: memory. Just as memory is crucial for human intelligence, it's essential for truly intelligent AI systems.
  18. Faster, smarter, reliable infinite chat: Supermemory IS context engineering.People are obsessed with prompts and prompt engineering. Sure, what you say is important, but what the model knows when you say it is the difference between a stateless text generator and an intelligent AI system. In short, context is the most crucial component.
  19. We solved AI API interoperabilityOne API to rule them all, One spec to find them, One library to bring them all and in the TypeScript, bind them. When we were building the the Infinite Chat API, initially, we only supported the OpenAI format. This was fine, until a lot of our customers started asking, asking for more.
  20. The UX and technicalities of awesome MCPsLast month, we launched the Supermemory MCP, mostly to test our own infrastructure and get some initial traction. It blew up. To my absolute surprise, the initial launch itself got half a million impressions (!!!). Then, we launched and got #2 on ProductHunt too.
  21. Architecting a memory engine inspired by the human brainLanguage is at the heart of intelligence, but what truly powers meaningful interaction is memory — the ability to accumulate, recall, and contextualize information over time. Large Language Models (LLMs) have mastered language, but memory remains their Achilles’ heel.