Memory

com.leapmemoryPublished by leapmemory.comOfficial publisherv1.0.0Updated Oct 27, 2026

Long-term memory for AI assistants. Isolated per-user storage, recall across conversations.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Remote MCP server that gives an AI assistant long-term memory, storing information per user and recalling it across conversations.

What you can do
  • Store information in a long-term memory tied to the signed-in user.
  • Recall stored context across separate conversations.
  • Keep each user's memory isolated from other users' memory.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Useful when you want an assistant to remember preferences, facts or earlier context between sessions instead of starting fresh each time, and when several users share one assistant but should not see each other's stored memory.
Requirements
A remote MCP endpoint at api.leapmemory.com over streamable HTTP; no local package or runtime. OAuth authentication is required, so a LeapMemory account and a client that supports the OAuth flow are needed. Network access to the endpoint.
Before you install
Conversation content is stored on a third-party service and persists beyond the session, so avoid sending secrets or sensitive personal data. Access is granted through OAuth to your account; review the scopes the client requests. No tool list is published, so what can be written, read or deleted is not documented here.

Installation

In SourceWeft

  1. Open Memory in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.leapmemory%2Fmemory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "memory": {
      "type": "http",
      "url": "https://api.leapmemory.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.