akasha-mcp

# akasha A local knowledge base that gives coding agents a memory, served over MCP. ## The problem Every agent session starts from zero. Yesterday an agent spent an hour working out why a test fails one run in twenty: two tests share a fixture directory and the cleanup of one races the setup of the other. It fixed the test and the session ended. The reasoning lived in a context window, and the window is gone. Today another agent meets the same flake, reads the same files and derives the same answer, spending the same time and context to get there. What you already know is not missing, it is scattered. Some of it sits in Claude Code project memory, some in Serena memories, some in a notes folder, some in markdown files inside repos. Each agent writes to its own corner, and none of them searches the others. Pasting notes into prompts does not scale: context is the scarce resource, and every pasted page crowds out the work. Conventions ("migrations are reviewed before merge", "never mock the database in integration tests") get retyped at the start of session after session. ## How akasha fixes it akasha builds one local index over the markdown you already have. It is read-only by default and copies nothing: your files stay the source of truth, and the SQLite index derived from them can be deleted and rebuilt at any time. Agents search it through MCP before they start investigating, and write what they find back as ordinary markdown with `knowledge_write` and `knowledge_append`. The next session starts where the last one ended. Search is keyword (BM25) and, if enabled, dense retrieval, fused by reciprocal rank. Results are sized for a context window: a handful of capped hits, with `knowledge_get` to page into a document only when one is worth reading. Conventions are documents of `kind=convention`. They are delivered automatically at session start and are read-only to agents; only the CLI can create or change one. Hooks keep the index fresh without anyone thinki…