WHY TEAMS CHOOSE KUMBUKUM

One library your team and your AI work from.

Notes, memories, links, emails, and Git in one place. Every AI tool reads it. Some now act on it. All of it stays open, inspectable, and yours.

Open source • Git sync • Scoped access • MCP-compatible
TLDR:

Why choose Kumbukum?

Kumbukum gives teams one shared, inspectable memory layer for AI work. Instead of re-explaining project context, preferences, decisions, Git history, support knowledge, and email details in every tool, teams store that context once and make it available across Claude, Cursor, ChatGPT, Codex, Windsurf, Zed, and other MCP-compatible clients. Unlike personal assistant memory or single-tool project folders, Kumbukum is open source, team-owned, searchable, editable, graph-linked, self-hostable, and built around real work objects.

The hidden cost of scattered AI context

The Problem: AI forgets. Teams repeat themselves. Knowledge gets lost in chat, docs, and tabs. Every new session starts from zero — your AI has no idea what you decided yesterday, what your preferences are, or what your team already knows.

The Impact: Teams waste hours re-explaining context. Answers are generic instead of tailored. Decisions get re-litigated because nobody remembers the reasoning. The more AI tools you use, the worse the fragmentation gets.

How Kumbukum Solves This: Kumbukum gives your team a visible, controllable memory system. Store notes, decisions, preferences, and context once — every AI tool retrieves it automatically. No black boxes. You can inspect, edit, and organize everything your AI remembers.

What changes

Before: I use three AI tools. None of them share context.

After: One shared memory. Claude, Cursor, and ChatGPT all start with the same context.

Before: I keep repeating my preferences in every new chat.

After: Preferences are stored once and reused automatically across sessions.

Before: We made this decision last week, but nobody remembers why.

After: Decisions stay linked to notes and sources, so your team can see the full reasoning instantly.

How you save hours with Kumbukum

In this real-life example, we asked Claude to help us answers questions about an RfP (Request for Proposal) Excel sheet. Claude used our instructions to and answered all of the 87 questions accurately within 4 minutes and 32 seconds (something we couldn't do manually in under an hour).
Claude and Kumbukum saving you hours of work

Kumbukum vs ChatGPT Memory vs Claude Projects

Feature Kumbukum ChatGPT Memory Claude Projects
Works across AI tools Any MCP client ChatGPT only Claude.ai only
Open source Yes No No
Team-shared memory Yes No (per-user) Yes (Teams plan)
Edit memory Full inspection Limited list view Files only
Knowledge graph Yes No No
Bidirectional Git sync Yes No No
Browser extension capture Yes No No
Storage primitives 5 (notes, memories, URLs, Git repos, emails) Conversation memory Per-project files
Total MCP tools 44
Pricing Starter $29 / Pro $99 mo, 7-day free trial Bundled with ChatGPT plans Bundled with paid Claude plans

Measured impact on AI tool payloads

Kumbukum exposes 44 MCP tools across 5 storage primitives — notes, memories, URLs, Git repositories, and emails. We benchmarked the 3 retrieval tools (search_knowledge, recall_memory, search_notes) against the unslimmed baseline. Combined retrieval payload dropped from 14,272 tokens to 1,964 tokens — a 86.2% reduction, or 12,308 tokens saved per call.

  • search_knowledge: 7,804 → 1,313 tokens (−83%)
  • recall_memory: 2,394 → 325 tokens (−86%)
  • search_notes: 4,074 → 326 tokens (−92%)

Latency overhead stayed inside noise — combined 300ms → 321ms across all three calls (21ms total). Characters dropped from 57,086 to 7,853, a 49,233-char reduction.

Ready to remember everything?

One shared library every AI you use can read from — and write to. Notes, memories, links, emails, Git. Open source. 7-day free trial.