Memory MCP

Ragionex Memory

Context engine and self-learning memory for AI agents

Your agents save what matters on their own, fix what changed and pick up where you left off in every new session.

Keep each project in its own Vault, give every key only the access it needs, and share memory with your team.

Set Up in One Line · Quick Start · Documentation · Pricing

Requirements

• Node.js 18 or later.

Quick Start

Set Up with Your Agent

Paste this into your agent:

Set up Ragionex Memory for yourself by following the instructions at https://ragionex.com/setup.

If you are an AI agent: follow the instructions at https://ragionex.com/setup.

Set It Up Yourself

In a terminal, on Windows (PowerShell or Command Prompt):

npx.cmd -y @ragionex/memory-mcp@latest install

On macOS or Linux:

npx -y @ragionex/memory-mcp@latest install

1. Pick your agent. If the setup finds one on your computer, press Enter.
2. Press Enter to open the link in your browser, then sign in. A new account is free, no credit card needed.
3. Copy the one-time code the page shows and paste it into the terminal.
4. Quit your agent completely and open it again in a new session. From here on, just work: it uses Ragionex Memory on its own.

If your agent is not listed and has a global instructions file, choose manual setup. Run the setup once for each agent you use.

Your First Prompt

Ask your agent:

Check my Ragionex Memory connection.

It answers with your Vaults and what this agent may do in each.

Other MCP Clients

Claude Desktop, Cursor, Cline and other clients that run local MCP servers use the same tools. Create a key at app.ragionex.com/keys and add the server to the client's user-global MCP config. On Windows:

{

"mcpServers": { "ragionex-memory-mcp": { "command": "cmd", "args": ["/c", "npx", "-y", "@ragionex/memory-mcp@latest"], "env": { "RAGIONEX_MEMORY_API_KEY": "rgx_memory_..." } } } }

On macOS or Linux:

{

"mcpServers": { "ragionex-memory-mcp": { "command": "npx", "args": ["-y", "@ragionex/memory-mcp@latest"], "env": { "RAGIONEX_MEMORY_API_KEY": "rgx_memory_..." } } } }

These clients get the tools but not the memory rule, so they use memory less consistently on their own. A client with a global instructions file can get the rule through manual setup instead. On Windows:

npx.cmd -y @ragionex/memory-mcp@latest install --manual

On macOS or Linux:

npx -y @ragionex/memory-mcp@latest install --manual

See the MCP Client Notes for client-specific details.

What You Get

A Context Engine That Understands the Question. Your agent asks in plain language, and the engine understands what it means, even when it asks in different words than the memory was saved in. Even among thousands of memories, the right ones come first and arrive in milliseconds, so the agent reads only as much as it needs and its context stays lean. Memories come back exactly as they were saved: Ragionex never rewrites a memory or generates an answer.

Automatic Memory. Your agent saves what's worth keeping on its own: a document, a design decision, a preference, a project fact, something that was tried and how it turned out. It checks its memory before it answers, starts a task or asks you anything about your work, and the memory gets richer and more accurate the more you work. You can still tell it to remember or forget anything, any time.

Always Up to Date. A changed decision updates its record instead of adding a second one, and a record that turns out wrong is removed. Every change ends with one short line in the reply, so "undo that" is one sentence away. Every update carries the version its agent last read, so no agent can silently overwrite another's newer change.

Version History. Earlier versions of every memory, and deleted records in the trash, are kept for 30 days. Bring any of them back just by asking your agent, or from the dashboard.

Everything Visible in the Dashboard. Browse every memory your agents saved and see each one's status, who created or last edited it, and through which key. Open earlier versions, edit, restore or delete anything yourself, and export it all whenever you want.

Projects and Teams. Each project can keep its own memory in its own Vault, and a search never crosses into another. Every key carries its own Read, Create, Update and Delete permissions. Share a Vault with teammates, give each member their own permissions, and every member's agents draw from and add to the same memory.

Safe and Private. Memory text stored by Ragionex is kept in the EU and encrypted with AES-256. It is never sent to an outside AI service and never used to train AI models. Queued saves retry automatically.

Works Where You Work. One line sets up almost any AI agent on Windows, macOS and Linux. Other MCP clients connect too.

Vaults, Keys and Teams

A Vault is a separate set of memories. A key decides what an agent may do in it. A member is a teammate the Vault's owner shared it with. The picture above shows them working together:

The picture shows Create and Update as Write and Edit.

A Vault and Key per Project

A new account starts with My vault as its default, and every project without its own Vault uses the default. To give a project its own memory, create a Vault in the Dashboard, then ask your agent to *use my acme-app Vault for this project*, or put a RAGIONEX_MEMORY.jsonc file in the project folder:

{

// The Vault this project uses (shown by the connection check and in the dashboard) "vault_id": " ", // Optional: a key only this project uses, for example one that can only read "api_key": "rgx_memory_..." }

• The file is read on every request, so a change applies at once, with no restart.
• Only the project folder itself is checked, not its parents.
• Add the file to .gitignore before putting a key in it.
• A broken file, an unknown field or a rejected key stops the request with a clear error. Memory never falls back to another Vault or key.

Work with Your Team

• Share a Vault. In the Dashboard, the owner shares a Vault and gives each member Read, Create, Update or Delete.
• One Memory for Everyone. A decision one teammate's agent saves can be recalled by every member's agent with Read access.
• Two Locks. In a shared Vault, an action must be allowed by both the key and the member's permissions. A teammate with Read only cannot change anything, whatever their key allows.

Keys

• A key belongs to your account and works in every Vault you own or that is shared with you.
• Give each key only what its agent needs. A key with Read only can recall but never change anything.
• Keys are created with fixed permissions and revoked in the Dashboard.
• The setup creates one key per agent, named after the agent and the setup date. Running it again creates another key; earlier keys stay listed in the Dashboard, where you can revoke them.

Free Plan

Saving, editing and restoring a memory each cost 1 request, and so does each search page fetched from the service. Browsing, viewing, deleting, the trash, version history, status checks and export are free. Free is for personal projects and evaluation and is in early access, so its limits may change. Commercial use is not permitted on Free; Pro is coming soon.

Reference

Tools

Every record has id, vault_id, content, created_at, updated_at, status, revision, created_by and updated_by. New, edited and restored records must finish processing before recall can find them. Permanent deletion, export, Vault sharing, key management and account deletion live in the Dashboard.

Configuration, Updating and Uninstalling

• Project Folder. The folder the agent reports: Claude Code's project directory,