Vertiso Memory

One durable memory store for every AI tool: facts, decisions, preferences and handoffs across Claude, Codex and Cursor.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Vertiso Memory connector does

Vertiso Memory is a hosted memory layer giving Claude, ChatGPT, Codex, Cursor and any MCP client one shared store of durable facts, decisions and project state. Anthropic's directory lists 14 tools that write memories, retrieve them by meaning, and hand a session from one tool to the next. Sign-in is browser OAuth, or a bearer token.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Vertiso Memory tools (14)

  • archive_memory
  • forget
  • get_memory
  • goodbye
  • handoff
  • handoff_resume
  • hello
  • list_recent
  • recall
  • remember
  • search
  • unarchive_memory
  • update_memory
  • whoami

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • There is no vendor tool reference. Vertiso's documentation nav links MCP Reference, CLI Reference and API to one placeholder page. The 14 names come from Anthropic's directory, and two of them — forget and unarchive_memory — appear in no Vertiso document we could find. This is the "no vendor enumeration" case, which is weaker than a clean diff: there is no second list to check the first against.
  • The tool list is a floor. Vertiso's own shipped skills call complete_action, list_actions and work_status, none of which Anthropic lists. We did not verify them against the live server, because doing so would require calling a tool.
  • complete_action toggles when called without an argument. Vertiso's wrap-up skill warns that passing neither closed nor status flips the current state and "would reopen an action already closed elsewhere." That warning exists only inside a skill file; an MCP-only client never sees it.
  • The only OAuth scope is a wildcard. mcp names no object and no verb, so consent cannot separate recalling a memory from forgetting one. The boundary a reader would most want — between the routine write and the irreversible one — does not exist.
  • Secret stripping is an instruction to a model, not a filter. Vertiso says so itself: automated detection "can miss sensitive material, so do not rely on it as a substitute for sharing carefully." If you point a capture skill at a repository whose tool output carries credentials, redaction depends on the model noticing.
  • The CLI installer writes a hook the marketplace plugin does not. Vertiso's guarantee about no automatic transcript upload is scoped to marketplace plugins. vmem mcp install can add a user-scoped SessionStart hook, extra skill copies and a second MCP entry. Do not run it for a client that already has the plugin.
  • vmem installs by piping a remote script to a shell. curl -fsSL https://memory.vertiso.ai/install.sh | sh is Vertiso's documented path.
  • Free-tier caps are small. 100 stored memories at 4,000 characters each. No tool reads the remaining count, so an agent cannot check before it writes.
  • Revision history, shared team memory, SSO and audit logs are not available. They sit on Teams, marked "Coming soon", and Enterprise, marked "Contact us".
  • Memory content reaches Google Gemini. Vertiso names it as the subprocessor for memory structuring, retrieval and embeddings, stating Google does not train on paid-API submissions. Enterprise bring-your-own-inference is listed as not included on every self-serve plan.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request on 2026-08-23. Every parameter named on this page comes from Vertiso's skill sources, not from the server.
  • Retention is indefinite by default and deletion is not self-service for the account. Individual memories can be deleted from the web app, but account and Memory Data deletion is an email request to Vertiso, completed within 30 days and unrecoverable once begun.
  • The robots.txt carries a Content-Signal of search=yes, ai-train=no, use=reference. It expresses no ai-input preference either way. We honoured ai-train=no, treated use=reference as the reason to cite and link rather than reproduce, and synthesised no vendor prose verbatim.

Frequently asked questions

What does the Vertiso Memory MCP server actually store?

Durable facts your assistant decides are worth keeping, plus anything you explicitly ask it to save. Vertiso's guide names the memory types: decision, project, constraint, action, intent, observation, event and lesson. Its skills also send attributed verbatim excerpts of your conversation when exact wording preserves a decision better than a paraphrase would.

Can the Vertiso Memory connector delete my memories permanently?

One of the 14 tools is named forget, and Vertiso documents no such tool anywhere. Its guide distinguishes archiving, which keeps a memory but marks it inactive, from deleting, which removes it for good, and the vmem CLI ships an explicit vmem rm command. We could not read the tool schema, so treat forget as irreversible until Vertiso publishes its reference.

What OAuth permissions does the Vertiso Memory MCP server request?

Exactly one, and it is a wildcard. The server's RFC 9728 descriptor, its authorization server metadata and its 401 challenge all advertise a single scope named mcp on 2026-08-23. It names no object and no verb, so granting it grants whatever the server implements now and whatever it implements later.

Does the Vertiso Memory plugin upload my Claude Code transcripts automatically?

No. The only hook the Claude plugin ships is a SessionStart shell script that runs vmem hello with a source and a client name, then exits zero. We read its source on 2026-08-23. Vertiso's Trust page states the marketplace plugin installs no pre-compaction transcript hook and does not continuously upload conversations.

Do the Vertiso Memory skills read my session transcript?

Yes, when you invoke one. The checkpoint skill instructs the agent to read the Claude Code .jsonl session transcript and quote from it rather than from working memory, so quotes stay exact. All three capture skills require you to invoke them or accept an offer first, and each carries a secret-stripping step covering tokens, keys and connection strings.

How many tools does the Vertiso Memory MCP server have?

Anthropic lists 14 and Vertiso publishes no list of its own. Its documentation nav links MCP Reference to a placeholder page reading Coming soon. Vertiso's own plugin skills additionally name complete_action, list_actions and work_status, which are absent from the 14, so 14 is a floor rather than a total.

Does Vertiso Memory train AI models on my memories?

No, and its privacy policy commits to that twice. It states Vertiso does not use your Content or Memory Data to train, fine-tune or otherwise develop models. Memories do reach Google Gemini for structuring, retrieval and embeddings, under paid-API terms Vertiso states exclude training. Google is one of seven named subprocessors.

How long does Vertiso Memory keep my data?

Indefinitely while your account exists. Vertiso's retention table gives Content and Memory Data no expiry during an active account, and keeps it on the Free plan after a paid subscription ends. Deletion happens within 30 days of a confirmed account deletion, and Vertiso states data is inaccessible and unrecoverable once deletion begins.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Vertiso Memory to work.

Connect Vertiso Memory once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.