Resources · Claude connector

Claude Memory connectorWhat Claude can do in your Memory account.

The Claude Memory connector exposes 12 tools. 5 read tools recall memories, rooms and secret aliases, 5 write tools save, rate or share, 2 stay undocumented. Below: what Claude keeps for you, and why you need to tell it to use it.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

A memory that doesn't reset with every chat

Memory, from the publisher Mnemoverse, keeps your preferences, decisions and lessons learned in a hosted space tied to your account. Connected to Claude Desktop, it lets you recall tomorrow what you noted today, even from another tool linked to the same account.

Stop re-explaining your rules every Monday. You tell Claude that staging deploys go through one specific command. memory_write saves it, and later memory_read finds it by the meaning of your question.

Catch up after a break. memory_list_recent walks back through the newest memories, no query needed, so you see everything that was noted while you were away, not just the closest match.

Share a team memory. memory_create_room creates a pool shared across accounts, memory_invite_to_room mints an invite code, and memory_join_room lets a colleague join.

What the connector won't do: connecting the tools doesn't make Claude use them, and Mnemoverse says so plainly. You have to add memory rules to its instructions. The two delete tools on the sheet are described by no source. And nothing runs in the background. For unattended chains of steps, the Integrations hub gathers tools that do a different job.

Vocabulary

Words to know before connecting Memory

Five terms, explained once.

Connector
The bridge you set up once between Claude and a service you already use, so Claude can work with it while answering you.
Tool
A named capability the connector opens to Claude. Claude picks what it needs on its own; the directory sheet lists every one.
Authorization
The service's own screen where you hand Claude the access it will use. Granted once per person, and revocable.
Approval
The confirmation Claude waits for before an action that changes something in an account, shown in the chat at the right moment.
MCP
The open standard connectors are built on: it lets an assistant like Claude hold a conversation with an outside service.
Connect

Connect the Claude Memory connector

  1. 01

    Find Memory in Claude Desktop

    Memory is a desktop extension: it installs on Claude Desktop. In the app, open Customize, then Connectors, and spot Memory. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector for the organization first.

  2. 02

    Start from its row

    Click Connect on the Memory row and follow what the screen shows. No source we read describes this extension's own flow. If the link ever breaks, hit Disconnect and connect again from the same row.

  3. 03

    Check what you grant

    If the service shows an authorization screen, read it before you accept: it, not Claude, sets what the access covers. Per Mnemoverse, memory is tied to the account behind the key you use.

Tools

Memory's 12 tools: recall, save, share

MCP Memory gives Claude 12 tools: 5 that read your account, 5 that change something in it, and 2 no official source describes.

Ten tools described in Mnemoverse's documentation, two with no description. Names stay in English, as Claude shows them.

  • 5 read
  • 5 write
  • 2 not documented

What Claude recalls (5)

5 tools

Five tools that look up your memory, your rooms and your secret aliases.

memory_read

Searches your memories with a plain-language question, newest first or within a time range if you want. Ranking goes by meaning, not exact words.

When it helps
you ask Claude how your team deploys staging, and it finds the rule you saved.
Watch out
unless told otherwise, the search skips shared rooms.

Sourcemnemoverse.com · September 28, 2026 ↗

memory_list_recent

Lists the newest memories first, with no query, so you catch up on what happened. Nothing gets filtered out for relevance. Mnemoverse points to it when you want a complete recent list rather than the closest match.

When it helps
after a break, you want the latest saved items, including in a shared room.

Sourcemnemoverse.com · September 28, 2026 ↗

memory_stats

Tells you how many memories are stored in your account. A plain counter, handy to confirm that saving actually works before you rely on recall.

When it helps
you just connected the tool and want to be sure Claude has started keeping things.

Sourcemnemoverse.com · September 28, 2026 ↗

memory_list_rooms

Finds the shared rooms you belong to, in a fresh session. A room is a memory pool shared across several accounts.

When it helps
you open a new chat and want to pick up a room without hunting for its address.

Sourcemnemoverse.com · September 28, 2026 ↗

vault_list

Lists the aliases of secrets you've stored. Per Mnemoverse, the values never come back: Claude only sees the names.

When it helps
you want to know what name an access key was filed under without exposing it in the chat.

Sourcemnemoverse.com · September 28, 2026 ↗

What Claude saves or shares (5)

5 tools

Five tools that add to your memory or touch shared rooms. No source describes their confirmation, so the general rule below applies.

memory_write

Approval: see the rule

Saves a preference, decision or lesson into your memory, tied to your key's account. It stays available in your other tools linked to that account.

What Claude asks for
no source describes a dedicated confirmation; the general approval rule applies.
When it helps
you want Claude to keep a decision made on a project so you don't explain it again.

Sourcemnemoverse.com · September 28, 2026 ↗

memory_feedback

Approval: see the rule

Flags a memory as helpful (+1) or wrong (-1). You can point it at a shared room to rate what came from there.

What Claude asks for
nothing specific is described; the default approval rule applies.
When it helps
a memory Claude brought up was wrong and you want to flag it.

Sourcemnemoverse.com · September 28, 2026 ↗

memory_create_room

Approval: see the rule

Creates a room, meaning a memory pool shared across accounts. Other accounts then get in with an invite code.

What Claude asks for
no source specifies a confirmation; see the general rule.
When it helps
several accounts need to share the same working memory.

Sourcemnemoverse.com · September 28, 2026 ↗

memory_invite_to_room

Approval: see the rule

Mints a shareable invite code for a room. Per Mnemoverse, each code expires and works once, unless minted for several uses.

What Claude asks for
no dedicated confirmation is described; the general rule applies.
When it helps
someone needs to join an existing room.

Sourcemnemoverse.com · September 28, 2026 ↗

memory_join_room

Approval: see the rule

Redeems an invite code to join a room. The code comes from memory_invite_to_room and, per the publisher, expires.

What Claude asks for
no specific rule is described; the default approval rule applies.
When it helps
a colleague sent you a code and you want their team's decisions.

Sourcemnemoverse.com · September 28, 2026 ↗

Undocumented (2)

2 tools

The sheet publishes these two names, no source describes them, and the publisher's docs contradict them. This page guesses nothing from a name.

memory_delete

No source documents this tool: the sheet names it, nothing more. Mnemoverse's documentation says two delete tools were removed in version 0.9.0, without naming them: hence the disagreement laid out in the limits.

Watch out
the general approval rule covers it if it's ever called.

memory_delete_domain

A second name on the sheet with no public description. No source says what it targets; the publisher's docs don't name it and only mention two removed delete tools. Nothing is claimed here from its label.

Watch out
it also falls under the general approval rule.
Approvals

What Claude asks first, and who can switch Memory off

By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. No source describes a dedicated confirmation for the five tools that save or share.

On Team and Enterprise, workspace owners decide whether a member may let certain actions through without being asked again. They can also limit what Memory may do for the whole organization, keeping reading open and closing writes for example, with a setting nobody bypasses from their own account. Finally, Claude works with the connected person's rights: what that person can't reach, Claude can't reach either.

Plans

Which plans include it

None of the 819 directory sheets shows plan availability. Connector by connector, that information isn't published anywhere: it's a real gap in the catalogue.

The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization first. For the current status on your account, the only reference is the Memory sheet in the official directory, which the button on this page opens.

Limits

Where Memory stops inside Claude

A connector isn't an automation: Claude calls these tools while answering you. This connector is a desktop extension for Claude Desktop, and only Mnemoverse, the publisher, documents it.

The tool list is an observed floor, not a promise: an admin can open capabilities missing from public sheets. The directory badge isn't a security audit, and Anthropic notes on every sheet that it doesn't control a publisher's tools. A connected community connector has exactly the same access as any other. Here, the sheet and the docs don't even list the same tools. Other connectors are gathered on the Claude connectors page.

Two official sources disagree

Can Claude delete memories with Memory?

  • Claude directory sheet ↗October 2026The sheet lists memory_delete and memory_delete_domain among its 12 tools.
  • Mnemoverse documentation ↗September 2026The publisher writes that two delete tools were removed in version 0.9.0 and that deletion is now an administrative operation.

What this page followsThe publisher's documentation, tied to a dated release, says the delete tools are gone; the directory sheet still lists them. So this page promises no deletion from Claude and files both names under undocumented. Check the directory sheet on your own account.

Need help

Need help connecting MCP Memory to Claude?

A person reads every message.

FAQ

Claude Memory connector: common questions

01What can Claude do with the Memory connector?
Claude can save a preference, decision or lesson into your Mnemoverse memory, find it later by the meaning of a question, list recent memories, count what's stored and rate a memory as useful or wrong. It also handles rooms shared across accounts: creating, inviting, joining and listing them. Finally, it can list the aliases of your stored secrets, never their values. Two tools on the sheet are described nowhere. All of it is scoped to the account behind your key.
02Can Claude erase memories in Memory?
Nothing supports that claim, and the directory sheet on your account remains the reference for the current state. The sheet lists memory_delete and memory_delete_domain, but no source describes them, and Mnemoverse's documentation says its delete tools were removed in version 0.9.0, with deletion becoming an administrative operation. To fix a wrong memory from the assistant, the publisher suggests writing a corrected one. On the write side, five documented tools save, rate or manage rooms.
03Does Claude ask before saving a memory?
No source describes a confirmation specific to memory_write, memory_feedback or the room tools. None describes one for the two undetermined tools on the sheet either. So the default rule applies: Claude asks before each action it takes on an account for you. On a Team or Enterprise workspace, owners decide whether members can let certain actions through without a prompt, and they can close writes for the whole organization with one setting.
04Which Claude plans support the Memory connector?
No official source publishes plan availability connector by connector, and the sheet doesn't show it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. Memory is a desktop extension. On Team and Enterprise, an Owner or Primary Owner enables the connector first. Check the directory sheet on your account for the current status before rolling it out.
05Does Claude see the whole team's memories?
No, only those of the account tied to your key and those of rooms you belong to. Mnemoverse states memory is scoped to the key's account: keys from two different accounts mean two separate memories. On Claude's side, the general rule holds: it works with the connected person's rights and nothing more. To share, you go through a room and an invite code. Nothing in the sources describes a wider view.
06Why doesn't Claude remember anything after connecting?
Because connecting adds the tools without making Claude use them: by default, it answers from its own context. Mnemoverse recommends adding memory rules to its instructions. Also check that your tools use the same key, and ask for memory_list_recent rather than a meaning-based search when you want to see everything that was noted. A read with no scope doesn't search shared rooms either, and keys from two different accounts mean two separate memories.
07Claude or an automation tool for Memory?
They do different jobs, so it depends on the use. Claude with Memory keeps and recalls context across conversations, when you ask or following the rules you give it. An automation tool is built to chain steps that run unattended. This connector starts nothing in the background: no tool fires unless Claude picks it while answering you. Each tool runs only inside the chat you're having, and stops when the chat does.