brain-mcp

brain-mcp

A private, local AI second brain for Markdown notes, providing hybrid search and read/write tools for MCP-compatible AI clients like Claude and Cursor.

Category
访问服务器

README

brain-mcp

A local, private, free AI "second brain". Point it at any folder of Markdown notes (built for Obsidian vaults, works on any Markdown folder) and it becomes a searchable knowledge base for any MCP-compatible AI client — Claude Code, Claude Desktop, Cursor, etc. Hybrid search (semantic + keyword), incremental self-healing indexing, read/write tools. No API keys. No cloud. Nothing leaves your machine.

Quick start

  1. Clone this repo.
  2. Open the folder in Claude Code.
  3. Say "set up the brain" (or run /setup-brain).

That's it. The agent reads SETUP.md and does everything: installs deps, ensures Ollama, auto-detects your Obsidian vault, registers the MCP server user-scoped, indexes, and verifies.

Manual install (fallback)

python -m venv .venv
# Windows:  .venv\Scripts\python -m pip install -r requirements.txt
# macOS/Linux:  .venv/bin/pip install -r requirements.txt

# Install Ollama from https://ollama.com, then:
ollama pull nomic-embed-text

python brain_cli.py setup

How it works

Markdown notes folder (the "vault")
   │
   ├─ chunk_file()   ── split by H1/H2 headings. Frontmatter + heading prefixed
   │                     onto every chunk so each is self-contextual.
   │                     CHUNK_CHARS=1600, OVERLAP_CHARS=200. sha256 per chunk.
   ├─ ollama_embed() ── batches of 32 → nomic-embed-text vectors
   ├─ Chroma (cosine HNSW) ← embeddings + {path, heading}
   └─ SQLite: chunks + chunks_fts (FTS5 porter unicode61), trigger-synced

semantic_search (Chroma) and keyword_search (FTS5) are merged with Reciprocal Rank Fusion (k=60). hybrid_search is the primary tool. Indexing is incremental (per-chunk sha256), self-healing (startup mtime scan, background reindex on writes, orphan cleanup), and concurrency-safe.

MCP tools

Tool Purpose
hybrid_search_tool(query, top_k=5) Primary — RRF-merged semantic + keyword search
semantic_search_tool(query, top_k=5) Vector similarity only
keyword_search_tool(query, top_k=10) FTS5 keyword only
read_note_tool(path) Read a note's full content
list_recent_tool(days=7) Recently modified notes
append_to_note_tool(path, content) Append to an existing note
create_note_tool(path, content) Create a new note
save_conversation_tool(title, gist) Save a conversation to 06 Conversations/
ingest_file_tool(source) Ingest a URL / PDF / document as a reference note
reindex_tool(path=None) Reindex one file or the whole vault

Where data lives

The brain's own storage is decoupled from your notes. Index, database, config, and logs live in ~/.brain/ (override with the BRAIN_HOME env var) — never inside your notes folder.

Point at a different vault:

brain config --vault /path/to/notes      # persisted to ~/.brain/config.json
# or, ephemeral:
BRAIN_VAULT=/path/to/notes brain index

Vault resolution order: BRAIN_VAULT env → ~/.brain/config.json → Obsidian auto-detect → error.

Use it with other AI tools

setup registers the brain for Claude, then offers to also register it for Codex, Gemini CLI, Cursor, and Windsurf. Do it any time:

brain mcp                                  # interactive picker
brain mcp --client codex --client cursor   # non-interactive

It merges into each tool's MCP config without disturbing your other servers.

Performance

The embedding model is kept resident (keep_alive=-1 on every call and OLLAMA_KEEP_ALIVE=-1 persisted + passed to the MCP server). Without this, Ollama unloads the model after ~4 min idle and the next tool call stalls 10–30s on a cold reload. brain setup configures this automatically. Warm embedding latency is ~38ms vs ~2.2s cold. (size_vram=0 in ollama ps is a known reporting bug — judge by latency, not that field.)

Privacy

Everything runs locally. Embeddings are computed by Ollama on your machine. Chroma and SQLite are local files. No API keys, no telemetry, no cloud fallback. Nothing leaves your computer.

License

MIT — see LICENSE.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选