Claude Vertiso Memory connectorWhat Claude can do in your Vertiso Memory account.
The Claude Vertiso Memory connector exposes 14 tools. 5 read your stored memories, 5 save, change or archive something in them, and 4 are documented nowhere. Below: what Claude keeps, what it looks up, what it cannot be relied on to do, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude has a memory that persists
Each new conversation usually starts from zero. With Vertiso Memory connected, Claude can store a decision or a preference once, look it up later instead of asking you to repeat it, and leave a structured handoff when a session ends so the next one, in Claude or another tool, picks up where you stopped.
Keep what matters the moment it is settled. remember captures a durable fact, and Vertiso asks assistants to use update_memory rather than write a near-duplicate.
Answer from earlier context. recall runs a hybrid search and returns a synthesized answer, search gives a ranked list of records to scan, and get_memory opens one memory in detail.
Hand work over cleanly, even to another tool. handoff writes a record a later session can claim, and handoff_resume lists open handoffs and claims the one you pick, which archives it.
What Claude will not do on its own: Vertiso warns that connecting only puts the tools on the shelf, so Claude will not reach for them until it knows this is its memory. Four tools, including forget and whoami, have no published description, and this page makes no claim about what they do. For how assistants and automation tools split the work, the Integrations hub lists the other families.
Five words before you plug it in
The vocabulary of this page, in one minute.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can use it while it answers you.
- Tool
- One named job a connector gives Claude. Claude picks the ones it needs during an answer, and the directory sheet lists them by name.
- Authorization
- The Vertiso sign-in in your browser, where you hand Claude the access it uses afterwards. Given once per person, and revocable.
- Approval
- The confirmation Claude waits for in the conversation before something that changes your account goes ahead.
- MCP
- The open standard behind connectors: it is what lets an assistant like Claude talk to an outside service such as Vertiso Memory.
Plug the Claude Vertiso Memory connector in, in three steps
- 01
Find Vertiso Memory in your connectors
Open Claude's settings, go to Customize, then Connectors, and search for Vertiso Memory. On a Team or Enterprise workspace, an Owner or Primary Owner switches it on for the organization before each member signs in.
- 02
Sign in from the connector row
Click Connect on the Vertiso Memory line. Vertiso says registration and sign-in happen in the browser, with no API key to paste. If the link breaks later, Disconnect and connect again.
- 03
Review the authorization screen
Read what the Vertiso screen grants before you accept: that screen, not Claude, sets what the access covers. Vertiso describes the sign-in as happening in the browser, so it is the browser window that shows this screen.
The 14 tools of the Claude Vertiso Memory connector
Vertiso Memory gives Claude 14 tools: 5 that read your account, 5 that change something in it, and 4 no official source describes.
Three groups: what Claude reads, what it saves or changes, and what no official source describes. Names stay exactly as Claude shows them.
- 5 read
- 5 write
- 4 not documented
What Claude reads (5)
5 toolsFive tools that look up, open or list memories and the session primer, without changing them.
get_memory
Opens specific memories so one record can be inspected in full, rather than through the synthesized answer of recall or the ranked list of search. Vertiso names it in its directory description alongside those two lookup tools.
hello
Returns the primer Vertiso wants loaded at the start of every session, which its instructions tell Claude to treat as authoritative context. That primer can also report open handoffs waiting to be resumed.
list_recent
Lists recent memories; Vertiso's skills point to it for the memories written during the current session. It reads what is there and is not described as changing anything.
recall
Runs a hybrid search across your stored memories and gives back a synthesized answer instead of raw records. Vertiso presents it as the way to recall facts, decisions, preferences and project context kept from earlier conversations.
search
Performs a ranked lookup of records with the same hybrid approach, returning a list to scan rather than a written answer. Each record it surfaces can then be opened in full with get_memory.
What Claude saves or changes (5)
5 toolsFive tools that add, revise, archive or hand over records in your Vertiso Memory account.
archive_memory
Approval: see the ruleArchives an intent or a project, either as complete once its whole scope has shipped or as abandoned when you say it is dropped. Vertiso's wrap-up workflow only proposes this on a witnessed event, never from inactivity.
handoff
Approval: see the ruleWrites a handoff record and marks it claimable, so that handoff_resume can pick the work up in a later session. Vertiso lists handoff among the session tools meant to let work continue across sessions and devices.
handoff_resume
Approval: see the ruleCalled without an id, it returns the open handoffs; called again with the one you choose, it claims it, which archives the handoff so a parallel session cannot take it too.
remember
Approval: see the ruleCaptures a durable fact into your memory: a decision, a preference or project context, so that a later conversation does not start from scratch. Vertiso asks for update_memory rather than a near-duplicate when the fact already exists.
update_memory
Approval: see the ruleRevises an existing memory. Vertiso's standing instruction tells assistants to use it rather than write a near-duplicate, which keeps one current version of a fact instead of several drifting copies.
Not documented (4)
4 toolsThe directory lists these four names, but no Vertiso source says whether they read or change anything. We do not guess.
forget
No Vertiso source describes this tool, and none says whether it reads or changes your memories. Its name alone is not evidence of what it does.
goodbye
Vertiso's wrap-up skill labels it the session-lifecycle close. That label is all the documentation gives: nothing states whether it stores, changes or only reads, and this page does not guess.
unarchive_memory
This name appears on the directory sheet with no matching description in any Vertiso document we read, so its effect is unknown here.
whoami
Listed by name only. Neither the directory description, the install page nor the official plugin repository explains it, and this page does not fill the gap.
What Claude asks before changing your memory
No source describes a Claude confirmation for a specific Vertiso tool; the rules below come from Anthropic and from Vertiso's skills.
By default, Claude stops and asks before any action it carries out on an account for someone, and that covers the five tools that save, revise, archive or hand over records. Vertiso's handoff skill adds its own boundary: asking for a handoff authorizes one capture, not standing permission for later ones. Claude works with the access of the person who signed in. On Team and Enterprise, owners decide which actions members may let through and can restrict a connector for the whole organization.
Which plans include the Claude Vertiso Memory connector
None of the 819 directory sheets states its availability by plan, so there is no official answer for Vertiso Memory alone.
Anthropic's general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before members can connect. The Vertiso Memory sheet in the official directory is the only place that shows its current state.
What the connector does not do
This connector is documented only by its publisher: no Claude help center article and no Anthropic developer page covers it, so the limits below come from Vertiso.
A connector is not an automation: Claude calls its tools while it answers, and nothing is saved by itself when a conversation ends unless Claude does it. The directory's verification badge is not a security audit, and Anthropic states on every sheet that it does not choose a publisher's tools or guarantee how they behave. Here, 4 of the 14 tools are described by no source at all, which is one more reason to read the notes above before relying on them.
Need help connecting Vertiso Memory to Claude?
A person reads every message.
