Memento Protocol

io.github.myrakrusemarkPublished by GitHub account myrakrusemarkv0.1.1Updated Oct 24, 2026

Persistent memory for AI agents. Store what matters, recall by meaning, skip the rest.

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Memento Protocol gives an AI assistant persistent memory: it stores what matters and recalls it by meaning across sessions.

What you can do
  • Save information the assistant should remember for later.
  • Recall stored memories by meaning rather than exact keywords.
  • Keep memory persistent across sessions through a hosted SaaS backend.
  • Scope stored memories to a named workspace.
When to use it
Worth adding when you want an assistant to carry context between conversations instead of restating background each time, and you are comfortable keeping that memory in a hosted service.
Requirements
Runs as a local stdio process from the npm package memento-mcp, so Node.js is needed. Requires a Memento Protocol API key in MEMENTO_API_KEY, plus MEMENTO_API_URL for the SaaS endpoint and MEMENTO_WORKSPACE for the workspace name. Network access to the service is required.
Before you install
The API key in MEMENTO_API_KEY is a secret and should be kept out of shared configuration. Stored memories are sent to a third-party SaaS service, so avoid saving sensitive or confidential content. No tool list is published, so what the assistant can write or delete is not documented here.

Installation

In SourceWeft

  1. Open Memento Protocol in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.