Browse / Second brain / neurostack

neurostack

raphasouthall

Local RAG layer and optimizer for your Markdown knowledge base.

Open raphasouthall/neurostack → On the boundary of the four rules.

ai-memoryknowledge-baseknowledge-graphlocal-ailocal-firstmarkdownmcpmcp-serverobsidianopen-sourcepkmpython

Works with any agent

ships AGENTS.md, the cross-tool instruction file.

In its own words

Aboutraphasouthall/neurostack

CLI + MCP server: grounded answers for any AI client, stale-note detection, session harvesting into memories. Local-first.

README.md

Not a note-taking app. A memory layer for the notes you already have.

Your AI assistant forgets everything when the conversation ends. You ask it about the paper you summarised last week — it has no idea. You ask it to continue the chapter outline you built together — it starts from scratch.

And even when it does find your notes, it might find the wrong version. The thesis argument you reversed, the runbook endpoint you deprecated, the decision you made in April that you overturned in June. It cites these confidently. It has no idea they're wrong.

NeuroStack reads your existing Markdown notes — from Obsidian, Logseq, Notion exports, or any folder of .md files — indexes them into a searchable knowledge graph, and connects that graph to your AI. It detects when notes have gone stale before your AI cites them. Indexing never modifies your files; optional MCP write tools let an AI client author or edit notes through your git history when you want it to.

Works with Claude, Cursor, Windsurf, Gemini CLI, VS Code, and Codex — anything that supports MCP.

Your notes, in your control

By default, NeuroStack is a read-only indexing layer:

  • Indexing, search, summaries, and graph analysis never modify your Markdown files
  • All index data lives in NeuroStack's own separate database
  • To remove it completely: neurostack uninstall — your notes are untouched
  • Nothing ever leaves your machine, unless you configure a third-party LLM provider for summaries and embeddings

The repository's own description, then 14% of its README. Read the rest on GitHub ↗

Read from the repository's git tree on 2026-08-17.