Make0 Brain

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 API Key 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

为 Claude Code、Cursor、Codex 和所有 MCP 智能体共享 AI 记忆。一个存储在本地 SQLite 文件中的版本化记忆,离线运行,无需 API 密钥。

一句话选型结论

按资料字段整理

Make0 Brain 属于文档知识类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
npx @make0-ai/brain init

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Make0 Brain当前 未标注 stdio · 本地进程 本地部署 有 2026-11-20
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

40.2 KB
来自项目仓库与上游目录的原文,未做删改

Make0 Brain: shared AI memory for every agent

One AI memory for every agent you use. Claude Code, Claude Desktop, Cursor, Codex, Windsurf, VS Code, Gemini CLI, Hermes Agent, and OpenClaw all read and write the same memory, and every change is versioned.

A local-first, open-source AI memory server for MCP. After a one-time model download it runs offline with no API key, keeps everything in one SQLite file on your machine, and speaks the same 7 tools as the hosted Make0 Brain. It can also start full: one command imports the sessions 41 coding agents already keep on disk.

Make0 · SWE-ContextBench results · LongMemEval results

npx @make0-ai/brain init

Only using Cursor or VS Code? These buttons add the server to that one app. Run init too if you want it to download the models up front and write the custom instruction.


Why

Every agent keeps its own memory. Claude has CLAUDE.md, Cursor has rules, Codex has AGENTS.md, ChatGPT has its memory page. You end up explaining your stack, your preferences, and last week's decisions again in each one, and the copies drift apart.

Make0 Brain is one memory that all of them share:

  • Tell one agent, every agent knows. A fact saved from Cursor is found by Claude Code in the next session.
  • Nothing is overwritten silently. Every edit, from any agent, is kept as a version with who wrote it and when.
  • Contradictions are resolved. When a new memory reverses an older one, the newer one wins and the older one is archived, on every install with no key. Connect a local or hosted LLM and it gets better: it also catches reworded updates and changed values, and merges duplicates. See Context stays consistent.
  • It stays yours. One SQLite file on your machine, MIT licensed, exportable to plain Markdown.

Quick start

1. Connect your agents.```bash
npx @make0-ai/brain init


`init` finds Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Codex CLI, Gemini CLI, Hermes Agent, and OpenClaw. When more than one is installed, it shows a checklist of them, all ticked; untick any you want to leave out. Pass `--clients` to choose up front, or `--yes` to configure every detected agent without asking. It then shows what it will change, asks once, keeps a `.make0-backup` of each config file, and adds Make0 Brain to each chosen app. It downloads the two local models (about 50 MB, once) with a progress bar, so your first question to an agent doesn't wait on a download. Restart the apps afterwards.

Connecting the server is not enough. The agent also needs a custom instruction so it searches Brain before answering and saves lasting facts there. `init` writes this into the global rules file for Claude Code (`~/.claude/CLAUDE.md`), Codex (`~/.codex/AGENTS.md`), Gemini (`~/.gemini/GEMINI.md`), and Windsurf. Cursor, Claude Desktop, VS Code, Hermes Agent, and OpenClaw keep rules in settings or a persona file, so `init` prints the same text for you to paste:```text
Make0 Brain is my source of truth for durable memory. Always search it before answering about me, my work, people, preferences, or past decisions. Save lasting facts and decisions to Brain. Never guess or invent memories. Use Brain exclusively for durable memory.
App Where it goes
Claude Code ~/.claude/CLAUDE.md, written by init
Codex CLI ~/.codex/AGENTS.md, written by init
Gemini CLI ~/.gemini/GEMINI.md, written by init
Windsurf Global rules, written by init
Cursor Settings → Rules → User Rules. Paste it.
Claude Desktop Settings → Profile → personal preferences. Paste it.
VS Code .github/copilot-instructions.md in the repo. Paste it.
Hermes Agent ~/.hermes/SOUL.md. Paste it.
OpenClaw ~/.openclaw/workspace/AGENTS.md. Paste it.

Skip the rule with init --no-rules.

2. Bring in the context you already have.```bash
npx @make0-ai/brain import --detect # CLAUDE.md, AGENTS.md, Cursor/Windsurf/Copilot rules
npx @make0-ai/brain import --sessions # past sessions from 41 coding agents, one digest each
npx @make0-ai/brain import ~/Documents/MyVault # an Obsidian vault or any Markdown folder
pbpaste | npx @make0-ai/brain import - # e.g. a memory dump copied from ChatGPT


`import` on its own asks what to import. The details are under Import and export.

**3. Look at it.**```bash
npx @make0-ai/brain view

The viewer opens on 127.0.0.1 with every brain, how many memories each holds, and what your apps retrieved and added this week.

Models live in ~/.make0/models and data in ~/.make0/brain.db. If you skip init (or pass --no-models), the first save or search downloads the models instead.

Or run it without arguments

Typed in a terminal, npx @make0-ai/brain opens a menu: connect agents, import sessions or notes, open the viewer, create a brain, choose which brains an app can use, export, restore an archived memory, or show stats. Any command run without its arguments asks for them the same way, one step at a time, with arrow keys, checkboxes, and a default on Enter. Ctrl+C cancels without changing anything.

Scripts and MCP clients are unaffected. Passing the arguments, adding --yes, or running without a terminal skips every question, and MCP clients, which start the server without a terminal, get the server as before. make0-brain serve starts the server even in a terminal.

Verify it works

Restart the apps you connected, then check that a memory written by one agent reaches another:

  1. Save from one agent. In Cursor (or any connected app), say: "Remember that my test fruit is mango." It should call add_memory.
  2. Find it from another. In a new Claude Code session (or any other connected app), ask: "What is my test fruit?" It should call search_brain and answer "mango" without being told.
  3. Check who wrote it. Run npx @make0-ai/brain view, open the personal brain, and click the memory. It shows Added by Cursor and a version timeline.

Delete the test memory in the viewer when you are done. If step 1 or 2 doesn't call a Brain tool, the app is missing the custom instruction above (Cursor, Claude Desktop, and VS Code need it pasted) or wasn't restarted. Run npx @make0-ai/brain agents to confirm the app can use the personal brain.

Import directly from

Your coding agents already keep every session on disk. One command reads that history from 41 agents and saves each session as a memory, filed under its project, so the next agent can find what was asked, decided, changed, and broken last time. No API key and no model are needed.```bash
npx @make0-ai/brain import --sessions # pick agents and a brain step by step
npx @make0-ai/brain import --sessions --agent cursor,codex # only these agents
npx @make0-ai/brain import --list-agents # agent ids and names


Claude Code
Codex
Cursor
VS Code Copilot Chat
Copilot CLI
Gemini CLI
Antigravity

opencode
Cline
Roo Code
Kilo Code
Continue
aider
Amp

Goose
Crush
Zed
Hermes
OpenClaw
pi
omp

Senpi
gajae-code
Kimchi
prime-agent
Qwen Code
Kimi Code
Kiro

Junie
Devin CLI
DeepSeek Harness
CodeWhale
CodeBuddy
Command Code
ZCode

Reasonix
TRAE CLI
Muse Code
MiniMax Code
Grok Build
Cherry Studio
Any MCP agent

In a terminal it asks three things: which of the agents it found to import, which brain to save into (or a new one), and whether the summary is right. Each memory is a digest of one session: what you asked, your corrections, the files that changed, the commands that failed, and how it ended. Credentials are redacted before anything is saved. Coding-agent sessions covers the time window, the session cap, scripting flags, and the stores that cannot be read.

## One context across all agents

### Same tools in every app

After `init`, every connected agent gets the same 7 tools:

| Tool                  | What the agent uses it for                                      |
| --------------------- | --------------------------------------------------------------- |
| `list_brains`         | Get the brain ids this app can use. `personal` is always there until you allocate others. |
| `search_brain`        | Find memories for a focused query before answering.             |
| `get_memory`          | Read one memory in full.                                        |
| `get_memory_versions` | Read every saved version of a memory, newest first.             |
| `add_memory`          | Save a fact or a short Markdown note when you ask it to.        |
| `update_memory`       | Change a memory. The previous text is kept as a version.        |
| `delete_memory`       | Archive a memory. Its versions are kept and you can restore it. |

The names and schemas match the hosted Make0 Brain, so a prompt or agent setup works against either one.

### More than one brain

The personal brain is created with the database and cannot be deleted. Add others when a project should not share those memories:```bash
npx @make0-ai/brain brains create "Work" --description "Client work" --agents cursor,claude-code
npx @make0-ai/brain brains                 # list brains
npx @make0-ai/brain agents                 # which app can use which brain
npx @make0-ai/brain import ~/Notes --brain Work
npx @make0-ai/brain view --brain Work

An app with no allocation sees only personal. agents grant and agents revoke change that, and so does the Connect dialog in view. Revoking every brain leaves the app with none: list_brains comes back empty until you grant one again. The viewer and the CLI can open every brain. Agents only see brains you give them, and list_brains is how they learn the id to pass to the other tools.

Open a brain to see its memories as a board, one column per category, with the app that wrote each one.

Every memory knows who wrote it

Make0 Brain reads the client name each app sends when it connects and records it as the writer: claude, chatgpt, or cursor. Any other app is recorded as mcp, with its own client name kept too. Search results show addedBy for each memory, and every version records who wrote it. You can see which agent learned what.

See what each app reads and writes

Every memory an app retrieves or writes is counted per app and per brain, with a rough token count. The home page shows this week at a glance; Details opens the full chart, filterable by brain, range, and app, in memories, tokens, or average tokens per call. The counters stay in the local database.

Context stays consistent

  • Contradictions replace older facts. If Cursor saves "I don't like dark mode in my editor" after Claude saved "I like dark mode in my editor", the newer memory wins and the older one is archived, with its history intact. The archived memory records which memory replaced it: the recycle bin shows the replacement, and an open memory lists what it replaced in its History timeline, with a Recover link. Editing a memory with update_memory is checked the same way.
  • Without an LLM, only clear reversals are replaced. The two memories must say the same thing with opposite polarity, so "I like dark mode" and "I dislike light mode" both stay. A memory saved as a correction replaces the one memory it matches most closely. A changed value, such as "I live in Pune" then "I live in Bangalore", is kept as two memories.
  • Changed values and duplicates are handled with an API key or a local model. An LLM judge compares the closest memories, found by meaning as well as by shared words, so "I'm based in Bangalore now" is compared with "My home city is Pune". It replaces contradictions and merges restatements into one memory. The merged text may only use words from the two originals, so it cannot invent facts.
  • Related memories are linked. Similar memories get links automatically, and search follows them up to two hops, so asking about a project also surfaces the decisions tied to it.

Switch a brain to 3D to orbit and zoom through it: categories branch from the center, and each memory sits on its category.

Memory versioning

Every write to a memory creates a version, whether it comes from an agent, an import, or you in the viewer. Nothing is overwritten in place.

What a version records

Field Meaning
versionNumber 1, 2, 3… per memory.
current The version agents read now. Exactly one per memory.
content, category, kind, entityType, confidence The memory as it was at that point.
writtenBy user, make0, claude, chatgpt, cursor, or mcp.
writerName The app's own client name when writtenBy is the generic mcp.
embeddingModel The embedder that indexed the text while this version was current.
createdAt When the version was written.

A version is written when the content, category, kind, or entity type changes. A confidence-only change does not add one.

Agents can read the history

Search results include versionCount. When it is greater than 1, an agent can call get_memory_versions to see how a fact changed and who changed it: for example, that you switched from npm to pnpm last month and which agent recorded it.

Nothing is lost

Action What happens
update_memory or an edit in the viewer A new current version. Older versions stay.
A contradicting or merged memory The older memory is archived with all its versions, and records what replaced it.
delete_memory Archived: hidden from search and reads, versions kept.
Re-import of an edited note A new version of that memory, not a duplicate.
Re-import of a note you deleted Skipped. Deleted stays deleted.
make0-brain purge --yes The only permanent delete. Agents cannot do it.

Browse and restore```bash

npx @make0-ai/brain history <id> # every version, current one marked *
npx @make0-ai/brain restore <id> --version 2 # make version 2 current again
npx @make0-ai/brain restore <id> # bring back an archived memory
``````text
* v3 2026-10-27T09:14:02.118Z claude
The project uses pnpm and Node 22.
v2 2026-10-20T16:40:51.502Z cursor
The project uses pnpm.
v1 2026-10-02T11:05:33.910Z user
The project uses npm.


Restoring makes an older version current again and re-indexes it. No version is deleted.

`npx @make0-ai/brain view` opens a local page (on `127.0.0.1` only) where you can create and switch brains, browse memories as a board or in 3D, search, add, and edit them, read each memory&#x27;s version timeline, restore a version, bring back archived memories, inspect the stored embedding, and permanently delete.

## Search quality

Measured on SWE-ContextBench Lite, the same comparison as the Make0 benchmark page: 300 earlier coding sessions and 99 related issues. The score is how often search returns the gold past session. The local install uses the offline MiniLM embedder and the ms-marco MiniLM reranker. Once the models are loaded, search takes about **60ms** per query on an Apple M2 Pro with 300 short memories, and about **430ms** in this benchmark, where each query is a whole GitHub issue and each memory a full coding session.

Rank 1, the gold session is the first result:```text
Make0 Brain (cloud)   █████████████████████████████░░░░░░░░░░░  71.7%
Make0 Brain (local)   █████████████████████████░░░░░░░░░░░░░░░  62.6%  ~430ms
LangMem               ██████████████████████░░░░░░░░░░░░░░░░░░  55.6%
OpenViking            ███████████████░░░░░░░░░░░░░░░░░░░░░░░░░  38.4%
Free summary search   ██████████████░░░░░░░░░░░░░░░░░░░░░░░░░░  34.3%
Mem0                  ██████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░  25.3%
Supermemory           █████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░  23.2%

Overall, the gold session appears anywhere in the results:```text
Make0 Brain (cloud) ██████████████████████████████████████░░ 93.9% top 10
Make0 Brain (local) █████████████████████████████████████░░░ 92.9% top 10 ~430ms
LangMem █████████████████████████████░░░░░░░░░░░ 73.3% top 10
Supermemory ████████████████████████░░░░░░░░░░░░░░░░ 59.6% top 15
OpenViking █████████████████████░░░░░░░░░░░░░░░░░░░ 51.5% top 3
Mem0 ████████████████░░░░░░░░░░░░░░░░░░░░░░░░ 39.4% top 3
Free summary search ███████████████░░░░░░░░░░░░░░░░░░░░░░░░░ 36.4% agent chooses


LangMem, OpenViking, Mem0, Supermemory, and free summary search are from Table 5 of that paper. &quot;Overall&quot; counts a hit anywhere in each system&#x27;s own result list; Make0 cloud, Make0 Brain, and LangMem each return 10. On the full benchmark (1,007 past tasks, 357 related issues), hosted Make0 scores 71.4% at rank 1 and 88.2% overall. A stronger embedder and reranker raise accuracy.

How search works: MiniLM embeddings and BM25 keyword scores are blended, a cross-encoder reranks the shortlist (or an LLM filter, with a key), weak results are pruned, and the top results are expanded two hops along memory links.

### LongMemEval

Measured on LongMemEval\_S with the open-source local install. Each question comes with its own history of past chat sessions, and the score is how often search returns the session that holds the answer. Overall covers the 470 standard questions. The 30 abstention questions, which ask about something the history never says, are scored on their own in the last row.

| Question type               |  Recall@5 | Recall@10 |       MRR |
| --------------------------- | --------: | --------: | --------: |
| **Overall**                 | **93.9%** | **96.2%** | **0.941** |
| Knowledge update            |     99.3% |     99.3% |     0.986 |
| Multi-session               |     90.0% |     93.0% |     0.959 |
| Single-session assistant    |      100% |      100% |     1.000 |
| Single-session preference   |     90.0% |     96.7% |     0.717 |
| Single-session user         |      100% |      100% |     0.965 |
| Temporal reasoning          |     89.8% |     93.6% |     0.914 |
| Abstention (not in Overall) |     90.6% |     90.6% |     0.944 |

## Import and export

### Import

- **Folders and vaults.** Each note becomes one memory. Long notes split by heading, and each part keeps the note title. Frontmatter tags or the folder name become the category. Obsidian `[[wikilinks]]` become links between memories. `.obsidian/` and `.trash/` are skipped.
- **Agent rule files.** `--detect` finds the rule files you already wrote for one agent (global ones under your home folder, project ones in the current folder) and makes them available to all of them. Make0 Brain&#x27;s own &quot;search Brain first&quot; block is stripped out, so it is never imported as a memory.
- **Coding-agent sessions.** `--sessions`; see below.
- **Re-runs are safe.** Unchanged items are skipped, edited ones get a new version, and memories you deleted stay deleted.
- **`--extract`** (needs an API key or a local model) turns files into one-fact memories instead of note-sized ones. With `--sessions` it keeps only what stays true after the session: your preferences and corrections, project decisions, and fixes for errors that may come back.
- **`--brain `** picks the brain; at a terminal you are asked instead. `--dry-run` shows what would change without saving or creating anything. Imports over 200 memories ask first; `--yes` skips the question.

### Coding-agent sessions

`--sessions` reads the session history coding agents already keep on your machine and saves one memory per session, in a category per project (**Sessions · acme-api**), so the board shows a column per project. Each memory records what you asked, your corrections, the files that changed, the commands that failed with their first error line, and how the session ended. No model is involved, so it needs no key.

- **At a terminal** it lists the agents it found, busiest first, all ticked; then asks for a brain, or creates one; then shows a summary to confirm. In scripts, `--agent cursor,claude-code` picks agents, `--brain ` the brain (default personal), and `--yes` skips the questions. `--list-agents` prints every agent id.
- **Time window and cap.** It reads the last 30 days and at most 500 sessions, the most recently active first. `--since 2w` or `--since all` changes the window, and `--limit 100` or `--limit all` the cap. Sessions outside them are never opened, so a large history (Cursor&#x27;s database can pass 50 GB) costs a quick scan, not a full read.
- **Privacy.** API keys, tokens, private keys, passwords, and long random tokens are replaced with `[redacted:]` before anything is stored.
- **What is skipped.** Sessions with no prompt you typed, subagent runs, and files under temp folders. When an agent keeps one session in two places (Cursor&#x27;s CLI transcript and its IDE database), it is imported once.
- **Re-running** picks up new sessions; a session that grew gets a new version.
- **Agents read:** the 41 under Import directly from.
- **Not read:** Windsurf and TRAE IDE (their chats are encrypted), JetBrains AI Assistant, Kiro&#x27;s headless `data.sqlite3`, Reasonix 1.x frame logs, and Amp threads that live only on ampcode.com.
- **zstd.** Zed, DeepSeek Harness, and OpenClaw&#x27;s compressed events are zstd-compressed. Node.js 22.15 or newer decompresses them itself; on older Node.js, Make0 Brain uses the `zstd` command when it is installed and otherwise skips those sessions.
- The store locations and record formats follow the session format registry in deja-vu (MIT).

### Export```bash
npx @make0-ai/brain export ./my-brain          # one Markdown file per memory, opens as an Obsidian vault
npx @make0-ai/brain export --json brain.json   # every memory, version, and link (the Make0 port format)

The Markdown export imports back in. The JSON bundle includes archived memories and the full version history. It does not include embeddings; whoever reads it re-embeds with their own model.

Optional API key or local model

Nothing needs a key. With one, Make0 Brain resolves more memory contradictions (reworded updates and changed values, not only clear reversals), merges duplicate memories, picks better categories, filters search results with an LLM, and can import --extract. A model running on your own machine can do the same work without a key.

Copy .env.example to .env in this folder, or to ~/.make0/.env so every app shares one file:```bash
cp .env.example ~/.make0/.env
``````text
OPENAI_API_KEY=sk-... # or OPENROUTER_API_KEY, or MAKE0_BRAIN_API_KEY
MAKE0_BRAIN_LLM_BASE_URL= # any OpenAI-compatible endpoint (optional)
MAKE0_BRAIN_LLM_MODEL= # default gpt-6-luna
MAKE0_BRAIN_EMBEDDINGS=api # API embeddings instead of local MiniLM
MAKE0_BRAIN_LLM_SEARCH=0 # keep search on the local reranker


### Local model (Ollama, LM Studio, llama.cpp)

Point `MAKE0_BRAIN_LLM_BASE_URL` at a server on `localhost` and no key is needed. Nothing leaves your computer.

A server on another machine on your network works the same way, such as a Strix Halo mini PC or a desktop GPU at `http://192.168.1.50:8080/v1`. Private addresses (`10.x`, `172.16`–`31.x`, `192.168.x`, Tailscale&#x27;s `100.64`–`127.x`, IPv6 `fc00::/7` and `fe80::/10`) and `.local`, `.lan`, `.home.arpa`, and `.internal` names are recognized. Memories go to that server and nowhere else. For a hostname Brain cannot place, such as a tunnel, set `MAKE0_BRAIN_LLM_LOCAL=1`; set `0` to treat a private address as a hosted API.```bash
ollama pull llama3.2
``````text
MAKE0_BRAIN_LLM_BASE_URL=http://localhost:11434/v1   # Ollama; LM Studio is http://localhost:1234/v1
MAKE0_BRAIN_LLM_MODEL=llama3.2                       # default llama3.2 on localhost

A local or network URL wins over a hosted key set in the same environment, and that key is never sent to it. A local model is slower than a hosted API, so its calls get five times longer to answer, and search stays on the fast local reranker unless you set MAKE0_BRAIN_LLM_SEARCH=1. Servers that reject OpenAI's JSON mode are asked again without it. A model of 7B parameters or more gives noticeably better merges and extractions than a 1B to 3B one.

MAKE0_BRAIN_BASE_URL, the name before 0.3, still works.

Make0 Brain reads ./.env, then .env in the data folder (MAKE0_BRAIN_HOME, default ~/.make0). A variable already set in the environment, including in an MCP client's env block, wins. Switching embedders is safe: memories indexed by another model are re-embedded on the next search.

Privacy and security

What leaves your machine

When What is sent To
init, or the first save or search Download requests for the two local models (no memory content) Hugging Face
Each launch through npx, which is how agents start Brain A request for the latest release, and a download if there is a new one (no memory content) npm registry
Saves and searches with no API key Nothing
With an API key: saves The new memory and close matches, to merge duplicates and pick a category Your provider (MAKE0_BRAIN_LLM_BASE_URL, default OpenAI)
With an API key: search (MAKE0_BRAIN_LLM_SEARCH not 0) The query and candidate memories, to filter results Your provider
With an API key: import --extract The full text of the imported files (for --sessions, the redacted digest) Your provider
With a localhost MAKE0_BRAIN_LLM_BASE_URL The same as with an API key, but to a server on this machine Nothing leaves the machine
With a private-network MAKE0_BRAIN_LLM_BASE_URL The same as with an API key, but to a server on your network That server only
import --sessions without --extract Nothing
MAKE0_BRAIN_EMBEDDINGS=api The text of every memory and every query, to embed it Your provider

Make0 Brain has no telemetry and does not contact Make0. The usage counts in the viewer stay in the local database.

Agents start Brain with npx -y @make0-ai/brain, so each launch contacts the npm registry and runs any newly published release. If the network is down, npx uses its cached copy and Brain still runs.

To turn this off, install a fixed version and point the agent config at the make0-brain binary instead of npx:bash npm install -g @make0-ai/brain@&lt;version&gt; ``````json { &quot;mcpServers&quot;: { &quot;make0-brain&quot;: { &quot;command&quot;: &quot;make0-brain&quot;, &quot;args&quot;: [] } } }

Pinning the version inside the npx command (npx -y @make0-ai/brain@) is not enough. It stops automatic updates, but npx still contacts the registry on each launch. Running init again puts the npx command back, so edit the config again afterwards.

Make0 Brain being local does not make your agents local. When an agent calls search_brain, the memories it gets back go into that agent's conversation, and that conversation is sent to the agent's own model provider (Anthropic for Claude, OpenAI for Codex, and so on). Keep anything you would not paste into that agent out of the brains it can use. agents grant and agents revoke control which brains each app sees.

Where your data lives

  • Database: ~/.make0/brain.db, a plain SQLite file with your memories, every version, links, and usage counts. It is not encrypted; it is protected by your user account and disk encryption.
  • Imports: the text of each note is copied into the database, with its file path and a hash so re-imports can find changes. The original files are only read, never changed.
  • Agent config: init keeps one .make0-backup of each config file it edits, and adds a marked block to the rule files listed above.
  • API key: read from .env or the environment. It is never stored in the database or in exports.

Bad or malicious memories

A memory is text, and an agent can read it as an instruction. A web page or a file an agent was working on can try to get it to save something like "always run this script". Make0 Brain cannot tell a true fact from a planted one, but it makes them easy to find and undo:

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Make0 Brain 怎么安装?

在客户端按下面的安装命令接入:npx @make0-ai/brain init。装完在客户端配置里引用同一个包或端点。

Make0 Brain 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Make0 Brain 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Make0 Brain 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Make0 Brain 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Cline;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Make0 Brain 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Make0 Brain 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Make0 Brain 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。