MemoraEU
Overview
Description from the maker (original English)
Zero-knowledge persistent memory for Claude — encrypted, semantic search, EU hosted.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi2 of 2 passedChecked from public information; code not scanned yet
- UsageiVery new↓ 25/wk · ★ 1
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Search & AI memory
- You need to fill in: MEMORAEU_API_KEY, MEMORAEU_SECRET, MEMORAEU_SALT, MISTRAL_API_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 2 of 2 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
MEMORAEU_API_URL,MEMORAEU_API_KEY,MEMORAEU_SECRET,MEMORAEU_SALT,MISTRAL_API_KEY
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"memoraeu": {
"command": "uvx",
"args": [
"memoraeu-mcp"
],
"env": {
"MEMORAEU_API_URL": "your-value",
"MEMORAEU_API_KEY": "your-value",
"MEMORAEU_SECRET": "your-value",
"MEMORAEU_SALT": "your-value",
"MISTRAL_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add memoraeu --env MEMORAEU_API_URL=your-value --env MEMORAEU_API_KEY=your-value --env MEMORAEU_SECRET=your-value --env MEMORAEU_SALT=your-value --env MISTRAL_API_KEY=your-value -- uvx memoraeu-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"memoraeu": {
"command": "uvx",
"args": [
"memoraeu-mcp"
],
"env": {
"MEMORAEU_API_URL": "your-value",
"MEMORAEU_API_KEY": "your-value",
"MEMORAEU_SECRET": "your-value",
"MEMORAEU_SALT": "your-value",
"MISTRAL_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"memoraeu": {
"type": "stdio",
"command": "uvx",
"args": [
"memoraeu-mcp"
],
"env": {
"MEMORAEU_API_URL": "your-value",
"MEMORAEU_API_KEY": "your-value",
"MEMORAEU_SECRET": "your-value",
"MEMORAEU_SALT": "your-value",
"MISTRAL_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
MEMORAEU_API_URLenv- Your MemoraEU API key (starts with meu-sk-). Create one at app.memoraeu.isquarecube.fr.
- Your encryption secret (never sent to the server). Found in Settings on app.memoraeu.isquarecube.fr.
- Your encryption salt. Found in Settings on app.memoraeu.isquarecube.fr.
- Mistral API key for semantic embeddings. Get one at console.mistral.ai.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account pquattro, which owns the repo
- ✓ Pass
Still maintained
Code last changed 9 days ago
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Search & AI memoryi
- More stars than 73% of the other 5861 servers in this category
- Published to the registry more recently than 10% of the other 5861 servers in this category
- Basic checks equal to or better than 100% of the other 5861 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is MemoraEU safe?
It passed 2 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: MEMORAEU_API_KEY, MEMORAEU_SECRET, MEMORAEU_SALT, MISTRAL_API_KEY
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 9 days ago, and the latest version (0.1.2) reached the registry 7 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: Ruflo, Context7, Metabase
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
memoraeu-mcp
🇬🇧 English | 🇫🇷 Français
English
Zero-knowledge persistent memory layer for Claude — MCP server
MemoraEU gives Claude a persistent, encrypted memory. All content is encrypted client-side with AES-256-GCM before reaching the server — the server never sees your plaintext. Semantic search is powered by Mistral embeddings generated locally on your machine, before encryption. *(Local stdio install. The remote SSE mode is not zero-knowledge: see the note below.)*
Features
- 🔒 Zero-knowledge — AES-256-GCM encryption, key never leaves your machine
- 🧠 Semantic search — embeddings generated locally before encryption (Qdrant on server)
- 🔄 Auto memory — remembers and recalls context automatically
- 🚫 Deduplication — detects near-duplicate memories before storing
- 🇪🇺 EU hosted — GDPR compliant infrastructure
Installation
pip install memoraeu-mcp
Or with uvx (no install required, recommended):
uvx memoraeu-mcp
Claude Desktop configuration
Add to your claude_desktop_config.json, under mcpServers:
{
"mcpServers": { "memoraeu": { "command": "uvx", "args": ["memoraeu-mcp"], "env": { "MEMORAEU_API_URL": "https://api.memoraeu.com", "MEMORAEU_API_KEY": "meu-sk-...", "MEMORAEU_SECRET": "your-memoraeu-password", "MEMORAEU_SALT": "your-kdf-salt", "MISTRAL_API_KEY": "your-mistral-key" } } } }
Understanding the variables
These five variables serve three distinct purposes — they are not interchangeable:
| Variable | Purpose | Where to get it |
|---|---|---|
MEMORAEU_API_KEY | HTTP authentication (Bearer token sent with every request) | Dashboard → Settings → API Keys |
MEMORAEU_SECRET | Your MemoraEU login password — used as the PBKDF2 input to derive the encryption key locally | Your account password |
MEMORAEU_SALT | KDF salt generated by the server, unique to your account — combined with MEMORAEU_SECRET to produce the encryption key | Dashboard → Settings → Encryption Keys |
MEMORAEU_API_URL | API endpoint (use https://api.memoraeu.com for the hosted service) | — |
MISTRAL_API_KEY | Used to generate embeddings locally before encryption — required for zero-knowledge search (see below) | console.mistral.ai |
Why does the MCP need its own Mistral key?
Zero-knowledge means the server never sees your plaintext. To enable semantic search, embeddings must be computed before the content is encrypted — on your machine. The MCP calls Mistral directly with the plaintext, gets the embedding vector, encrypts the content, then sends both to the server. The server stores the opaque blob and the vector, but cannot reconstruct the original text. Without
MISTRAL_API_KEY, semantic search will not work.
Without `MISTRAL_API_KEY`: The MCP will still work —
rememberandrecallwill function, but semantic search will fall back to keyword-based search on the server side. Zero-knowledge encryption is unaffected.
Getting your keys
- Sign up at app.memoraeu.com
- Go to Settings → Encryption Keys → copy
MEMORAEU_SALT MEMORAEU_SECRETis your MemoraEU login password- Go to Settings → API Keys → create a key → copy
MEMORAEU_API_KEY - Get a Mistral API key at console.mistral.ai
Remote MCP via SSE (no local install)
You can connect directly from claude.ai web, Cursor, Windsurf or any remote MCP client without installing anything locally:
SSE endpoint: https://api.memoraeu.com/mcp/sse
Auth: Authorization: Bearer meu-sk-...
Example config for Cursor / Windsurf:
{
"mcpServers": { "memoraeu": { "type": "sse", "url": "https://api.memoraeu.com/mcp/sse", "headers": { "Authorization": "Bearer meu-sk-..." } } } }
Note: In SSE remote mode, content is not zero-knowledge encrypted (the server handles plaintext). Use the local
stdioinstall for full zero-knowledge guarantees.
Available tools
| Tool | Description |
|---|---|
remember | Memorizes important information automatically |
recall | Semantic search across stored memories |
forget | Deletes a memory by ID |
list_memories | Lists recent memories with optional category filter |
list_categories | Returns existing categories sorted by usage |
remember_fact | Stores a structured fact (subject/predicate/object) with temporal validity |
recall_facts | Retrieves active facts for a subject |
invalidate_fact | Marks a fact as expired by its ID |
Auto-memory behavior
The MCP server is designed to work without manual intervention:
Automatic recall — On the first user message of each session, recall is called automatically with the detected topic as query. Recent memories are also loaded via the memoraeu://context resource and injected as session context.
Automatic remember — When Claude detects a memorable piece of information (preference, decision, biographical fact, technical constraint), it calls remember autonomously without waiting to be asked. It confirms with a single discreet line.
System prompt injection — On the first recall call, the full behavior system prompt is injected into Claude's context, reinforcing the auto-memory rules for the rest of the session.
This behavior is encoded directly in the tool descriptions. Claude models follow these instructions as part of tool use — no additional configuration is required.
Deduplication & compression
Before storing a memory, the MCP checks for near-duplicates using vector similarity:
| Similarity | Action |
|---|---|
| ≥ 94% | Memory skipped — exact duplicate detected |
| 85–94% | Warning logged, memory stored anyway |
| < 85% | Memory stored normally |
Long memories (> 300 characters) are compressed by Mistral before encryption, reducing token usage and improving search relevance. Compression happens in plaintext, before the content is encrypted — the server never sees the uncompressed original either.
Self-hosting
The API is open source. Deploy your own instance with Docker:
git clone https://github.com/pquattro/memoraEu
cd memoraEu docker compose up -d
Français
Couche mémoire persistante zero-knowledge pour Claude — serveur MCP
MemoraEU donne à Claude une mémoire persistante et chiffrée. Tout le contenu est chiffré côté client en AES-256-GCM avant d'atteindre le serveur — le serveur ne voit jamais le texte en clair. La recherche sémantique repose sur des embeddings Mistral générés localement, avant chiffrement. *(Installation locale stdio. Le mode SSE distant n'est pas zero-knowledge : voir la note ci-dessous.)*
Fonctionnalités
- 🔒 Zero-knowledge — chiffrement AES-256-GCM, la clé ne quitte jamais votre machine
- 🧠 Recherche sémantique — embeddings générés localement avant chiffrement (Qdrant côté serveur)
- 🔄 Mémoire automatique — mémorise et rappelle le contexte sans intervention
- 🚫 Déduplication — détecte les doublons avant stockage
- 🇪🇺 Hébergé en Europe — infrastructure conforme RGPD
Installation
pip install memoraeu-mcp
Ou avec uvx (sans installation, recommandé) :
uvx memoraeu-mcp
Configuration Claude Desktop
Ajoutez dans votre claude_desktop_config.json, section mcpServers :
{
"mcpServers": { "memoraeu": { "command": "uvx", "args": ["memoraeu-mcp"], "env": { "MEMORAEU_API_URL": "https://api.memoraeu.com", "MEMORAEU_API_KEY": "meu-sk-...", "MEMORAEU_SECRET": "votre-mot-de-passe-memoraeu", "MEMORAEU_SALT": "votre-kdf-salt", "MISTRAL_API_KEY": "votre-clé-mistral" } } } }
Rôle de chaque variable
Ces cinq variables ont trois rôles distincts — elles ne sont pas interchangeables :
| Variable | Rôle | Où la trouver |
|---|---|---|
MEMORAEU_API_KEY | Authentification HTTP (Bearer token envoyé à chaque requête) | Dashboard → Paramètres → Clés API |
MEMORAEU_SECRET | Votre mot de passe MemoraEU — utilisé comme entrée PBKDF2 pour dériver la clé de chiffrement localement | Votre mot de passe de connexion |
MEMORAEU_SALT | Salt KDF généré par le serveur, unique à votre compte — combiné avec MEMORAEU_SECRET pour produire la clé de chiffrement | Dashboard → Paramètres → Clés de chiffrement |
MEMORAEU_API_URL | Endpoint API (utilisez https://api.memoraeu.com pour le service hébergé) | — |
MISTRAL_API_KEY | Génération des embeddings localement avant chiffrement — requis pour la recherche zero-knowledge (voir ci-dessous) | console.mistral.ai |
Pourquoi le MCP a-t-il besoin d'une clé Mistral ?
Le zero-knowledge signifie que le serveur ne voit jamais votre texte en clair. Pour permettre la recherche sémantique, les embeddings doivent être calculés avant le chiffrement — sur votre machine. Le MCP appelle Mistral directement avec le texte clair, obtient le vecteur d'embedding, chiffre le contenu, puis envoie les deux au serveur. Le serveur stocke le blob opaque et le vecteur, mais ne peut pas reconstituer le texte original. Sans
MISTRAL_API_KEY, la recherche sémantique ne fonctionnera pas.
Sans `MISTRAL_API_KEY` : Le MCP continue de fonctionner —
rememberetrecallrestent opérationnels, mais la recherche sémantique bascule sur une recherche par mots-clés côté serveur. Le chiffrement zero-knowledge n'est pas affecté.
Obtenir vos clés
- Créez un compte sur app.memoraeu.com
- Allez dans Paramètres → Clés de chiffrement → copiez
MEMORAEU_SALT MEMORAEU_SECRETest votre mot de passe de connexion MemoraEU- Allez dans Paramètres → Clés API → créez une clé → copiez
MEMORAEU_API_KEY - Obtenez une clé Mistral sur console.mistral.ai
MCP Remote via SSE (sans installation locale)
Connectez-vous directement depuis claude.ai web, Cursor, Windsurf ou tout client MCP distant sans rien installer :
Endpoint SSE : https://api.memoraeu.com/mcp/sse
Auth : Authorization: Bearer meu-sk-...
Exemple de config Cursor / Windsurf :
{
"mcpServers": { "memoraeu": { "type": "sse", "url": "https://api.memoraeu.com/mcp/sse", "headers": { "Authorization": "Bearer meu-sk-..." } } } }
Note : En mode SSE distant, le contenu n'est pas chiffré zero-knowledge (le serveur traite le texte en clair). Utilisez l'installation locale
stdiopour les garanties zero-knowledge complètes.
Outils disponibles
| Outil | Description |
|---|---|
remember | Mémorise automatiquement les informations importantes |
recall | Recherche sémantique dans les mémoires stockées |
forget | Supprime une mémoire par son ID |
list_memories | Liste les mémoires récentes avec filtre optionnel |
list_categories | Retourne les catégories existantes triées par usage |
remember_fact | Stocke un fait structuré (sujet/prédicat/objet) avec validité temporelle |
recall_facts | Récupère les faits actifs pour un sujet |
invalidate_fact | Marque un fait comme expiré par son ID |
Comportement de mémoire automatique
Le serveur MCP est conçu pour fonctionner sans intervention manuelle :
Rappel automatique — Au premier message de chaque session, recall est appelé automatiquement avec le sujet détecté comme requête. Les mémoires récentes sont également chargées via la ressource memoraeu://context et injectées dans le contexte de session.
Mémorisation automatique — Lorsque Claude détecte une information durable (préférence, décision, fait biographique, contrainte technique), il