Every team using AI coding tools has invented their own version of the same hack.
Some put everything in CLAUDE.md and commit it to the repo. Some maintain shared Obsidian vaults. Some have a context/ folder full of markdown files that someone updates when they remember to. Some paste a summary prompt at the start of every session. Some just re-explain everything every time and accept the tax.
These all work, kind of, for one person. They all break the moment you add a second person or a second tool.
I've used all of these workarounds and eventually built to be. It's an MCP memory server with shared team workspaces, typed knowledge chunks (decision, finding, convention, state, question, reference), role-based access, and cross-tool support for Claude, Cursor, and Codex.
The honest take
CLAUDE.md and these workarounds aren't bad. They're fine for solo developers on small projects. If you're one person working on one project in one tool, CLAUDE.md plus maybe Basic Memory or claude-mem will get you 80% of the way there.
The moment you add a second person or a second tool, they collapse. That's not a criticism of these tools — they weren't designed for teams. They were designed for individual persistence, and they do that well.
The team problem is a different problem. It needs shared infrastructure, not shared files. That's the gap I'm building to fill.
Context Cloud is an MCP memory server with shared team workspaces, typed knowledge chunks, role-based access, and cross-tool support for Claude, Cursor, and Codex. Free to use.
- Website:
- MCP endpoint:
https://api.contextcloud.pro/mcp/protocol
- GitHub: github.com/abhinavala/cntxtv2
SOCIAL SHARE CARD GENERATOR