Source: raw/This_Setup_Gives_Your_Team_the_Same_Claude_Memory_Steal_it.md
Creator: Simon Scrapes (YouTube) · URL: https://www.youtube.com/watch?v=PzaC81yCJg0 · Duration: 20:36 · Uploaded: 2026-07-30 · Platform: YouTube
A three-layer setup for a team that works in the Claude desktop app with shared documents, shared tools and shared memory, built only from existing services: Notion for permissioned context, Composio for tool access without sharing keys, and Supermemory for a shared memory container. Simon says nearly 70% of his community wanted to use Claude as a team and that Claude memory, third-party memory frameworks and MCP logins are all single-user. He calls it “80% of a Claude team system for about 20% of the work” and names two privacy gaps. The step-by-step guide sits in his paid community, where he is building his own “Team OS” to replace this.
Key Takeaways
- Treat context as shared infrastructure, not per-person. Each person’s Claude should read the same documents, use the same tools without seeing the keys, and recall the same decisions.
- Layer 1, shared context: Notion. Each member connects the built-in Notion connector with their own login, so Claude can read and write only what that person can in Notion. Permissions are set per page (for example the voice profile view-only for most of the team). Put the team-context page URL in the instructions or
CLAUDE.md: “When accessing team context or files, first check this Notion URL.” Google Drive or any permissioned cloud store works the same way. He rejects copying folders between machines (goes stale) and GitHub (too technical for business users). - Layer 2, shared tools: Composio. Each member adds Composio as a custom connector (its remote MCP URL), signs in, joins the team workspace, and connects their own accounts among about 1,052 apps. No key leaves Composio’s vault. One connector can hold several Gmail accounts, which the built-in Gmail connector can’t.
- Shared accounts. Best: give each person a seat with the right permissions inside the app (for example the accounting software) and let them sign in through Composio. For a single shared login with no seats (scheduler, affiliate dashboard, company LinkedIn), the Composio MCP gateway creates a scoped server per tool via one API call and returns an MCP URL to add as a custom connector. There was no dashboard for this at the time.
- Layer 3, shared memory: Supermemory. Claude’s built-in memory is per account and, in his view, weak. Supermemory’s plugin pulls relevant memories at session start and saves what was learned at the end, into a container. Point everyone at one container tag (“team OS”) and the team shares one memory.
- Two gaps he found. Memory outlives permissions: if someone pulled a Notion page into a session and it was saved to memory, revoking the Notion page doesn’t remove it from memory. And everything goes into the shared bucket: the plugin captures every session with no personal-versus-shared split, so keep client-sensitive work out of folders that write to the team container. He also notes the Supermemory admin can see all memories, including personal ones.
Supermemory setup (as shown)
- Admin creates the Supermemory workspace and invites teammates first; someone who signs up alone gets a private workspace instead.
- Claude desktop → Settings → Plugins → Add marketplace → from repository →
supermemoryai/claude-supermemory→ sync. The plugin adds seven skills (project config, save, search and others). - Run
/project-config: add an API key (created in the Supermemory console, full access, expiry), then set the project container tag (his:team-os-demo, hyphens, no spaces). - If saving is blocked, add
api.supermemory.aito the allow list under Settings → Capabilities. - Work from one shared project folder. The config is written to the session workspace, and inside a repo it falls back to per-repo tags, so set the tag in the folder everyone uses.
- Each teammate creates their own API key and runs the same config with the same container tag. Test with
/supermemory saveand check the container in the console.
Implementation
Tool/Service: Notion connector, Composio (custom remote MCP connector), Supermemory plugin for Claude. Setup: As above. Composio custom connector: Settings → Connectors → Add custom connector → Composio’s remote MCP server URL. Cost: Composio pricing he quotes from 15 August 2026: free plan with 20,000 tool calls a month and three team members; 19 a month for team use, with a free tier to try. His figures; check current pricing. Integration notes: The same Composio pattern solves cloud scheduled tasks that need several inboxes (Cloud Scheduled Tasks). Anthropic’s redesigned projects later added shared project context with view and edit permissions for Team and Enterprise (Projects), which may cover layer 1.
Try It
- Move your team’s voice profile, positioning and ICP into one Notion page tree and set who can edit each page.
- Have each member connect Notion in Claude with their own login and add the page URL to shared instructions.
- Trial Composio’s free plan for one shared tool before anything with financial access.
- Pilot Supermemory with two people on a non-sensitive project folder; check the console to see what got captured.
- Decide which folders must never write to the shared container before rolling it out.
Open Questions
- Supermemory’s Slack integration (which he says supports segmented private memory) was not shown.
- Whether the Supermemory plugin can split personal and shared memory automatically was not covered beyond his “no split” finding.
- The Y Combinator request-for-startups item on team agent infrastructure is mentioned without a link.
Related
- Claude Code Memory Architectures Compared — the single-user memory systems this extends.
- Connectors — built-in and custom MCP connectors.
- Claude Memory, Three Levels — built-in memory options.
- GBrain — team-scoped memory with source citations.
- Team Skills Plugin Marketplace — sharing skills across a team.
- Projects — first-party shared project context.