MemoraEU

io.github.pquattroPublished by GitHub account pquattrov0.1.6Updated Oct 27, 2026

Zero-knowledge persistent memory layer for AI agents. Encrypted client-side, hosted in France.

VerifiedSTDIODesktop onlyKnowledge & MemorySecurity & Monitoring

Overview

AI-generated overview

MemoraEU is a local MCP server giving AI agents a zero-knowledge, client-side encrypted persistent memory hosted in France.

What you can do
  • Provides a persistent memory layer that an AI agent can use to store and recall context across sessions.
  • Encrypts memory data on the user's machine before it leaves, using a key derived locally from the account password.
  • Connects to a hosted memory service in France through a configurable API base URL.
  • No individual tools are documented in the supplied material, so exact operations are not listed.
When to use it
Consider it when you want an assistant to keep long-term memory between conversations and you prefer that memory to be encrypted on your own machine rather than readable by the hosting provider.
Requirements
Runs locally as a Python package (memoraeu-mcp) launched with uvx, so a Python/uv runtime is needed. Requires a MemoraEU account and three secrets: MEMORAEU_API_KEY (bearer token from the provider's app), MEMORAEU_SALT (per-account KDF salt given at registration) and MEMORAEU_SECRET (the account password). MEMORAEU_API_URL optionally sets the API base URL. Network access to the hosted service is required. Desktop only.
Before you install
Three secrets are required: MEMORAEU_API_KEY, MEMORAEU_SALT and MEMORAEU_SECRET. The password in MEMORAEU_SECRET is used locally to derive the AES-256 key and is stated never to be sent to the server, but losing it or the salt likely makes stored memory unrecoverable. Memory content is sent to a third-party hosted service in France, encrypted client-side. The server writes and stores data, so review what an assistant is allowed to persist.

Installation

In SourceWeft

  1. Open MemoraEU 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.6LatestSep 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.