Connect Claude to a shared team memory

Connect Claude to a shared team memory.

Claude is brilliant for one conversation and blank the next. The fix is not a bigger context window; it is a durable memory outside the chat that your assistant reads and writes like a team member. Here is how that works and how to set it up in about five minutes.

The missing piece is a place, not a prompt

Pasting background into every chat is memory by hand. What you want is a vault of plain files that persists between sessions, that your teammates can read and correct, and that the assistant treats as ground truth. When the memory lives in files, three good things follow: humans can audit it, several tools can share it, and you can take it with you.

MCP in one paragraph

MCP (Model Context Protocol) is the open standard that lets AI tools call outside systems. A memory vault that speaks MCP can hand any compatible assistant a small set of verbs: list the notes, read one, search, write one. Claude supports it on the web, on desktop, and in Claude Code; so do most serious agent tools. One protocol, every assistant.

The five-minute setup, concretely

1

Claude, web or desktop

Settings, then Connectors, then "Add custom connector". Paste your vault's connection URL. Done.

2

Claude Code

One command in the terminal registers the vault as an MCP server for every session.

3

Anything else

The same URL works in editors and agent frameworks. The memory does not care which assistant is asking.

Ask the permission questions first

An assistant with write access to team knowledge is a team member, and you should onboard it like one. Where exactly may it write? Can it read the folder with salaries in it? Is every edit attributed to the agent by name, and reversible? Can you see what it read, not just what it wrote?

If the answers are shrugs, do not connect the tool to anything real.

Connect AI
assistant · Connected · 11 calls on record (7 updated, 4 read)
Your agent's endpoint: https://memava.com/o/YOUR-TEAM/mcp/YOUR-AGENT-TOKEN Works in Claude, ChatGPT, Codex, Cursor, and any tool that speaks MCP.
Reads and searches included: you see what your AI looked at, not just what it wrote.

What good looks like

Set up well, the loop is quietly wonderful: your assistant takes meeting notes into the vault, a teammate corrects a detail, and the next session the assistant already knows. The memory compounds instead of resetting.

Memava is a shared vault built for exactly this: any MCP assistant joins as a named, permissioned member, every action is attributed and reversible, and there is an audit of what it read.

Keep reading: MCP security: what to check before you connect AI to your notes · One memory across Claude, Cursor and ChatGPT · Own your knowledge base: why plain files win