Context7
Up-to-date docs for AI agents
Descripción del creador (original en inglés)
Memory for a Claude Code agent that survives the session: five tools, a markdown vault, all local.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"brain-core": {
"command": "uvx",
"args": [
"brain-core-mcp",
"serve"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add brain-core -- uvx brain-core-mcp serveEste necesita valores en su línea de comandos, así que copia la configuración y complétalos.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"brain-core": {
"command": "uvx",
"args": [
"brain-core-mcp",
"serve"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este necesita valores en su línea de comandos, así que copia la configuración y complétalos.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"brain-core": {
"type": "stdio",
"command": "uvx",
"args": [
"brain-core-mcp",
"serve"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub xy-claude, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.4.10) llegó al registro hoy.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Context7, Codebase Memory, Exa
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
A memory for your Claude Code agent that survives the session. One local MCP server, five tools, a markdown vault you can read, an eval that proves recall. Installs with one command.
brain-core gives a Claude Code agent a long-term memory that lives on your disk. You name the agent, you tell it who you are, and from then on every session opens with yesterday's brief, the decisions you made, the facts that changed and the corrections you gave. It remembers by writing markdown files you can open in any editor, and it finds things again through a local SQLite index plus Hindsight, a self-hosted vector memory. Nothing leaves your machine except the LLM calls you already make.
It is for one person running one or more agents on their own computer: a solo developer, a founder, anyone tired of re-explaining their project every morning. It is not a hosted service and not a team product.
Both. One Python package, three ways in:
| Piece | What it is | Who uses it |
|---|---|---|
brain serve | an MCP server that Claude Code starts from the agent's .mcp.json and that exposes five tools | the agent, every session, without you touching it |
brain command | a CLI: brain init, brain doctor, brain index, brain hindsight install, brain cron install, brain daily, brain weekly | you, once at setup, then cron |
brain_core.Agent | the Python library both of the above sit on | the eval runner, the demo script, your own scripts |
To a Claude Code user: an MCP server with five memory tools and a one-line installer. To a Python developer: a memory library with an MCP front end.
curl -fsSL https://raw.githubusercontent.com/xy-claude/brain-core/main/install.sh | bash -s -- --agent Atlas --user Alex
Every session with a coding agent starts from zero. You explain the project again, the decision you made last week again, the thing it got wrong on Tuesday again. Memory add-ons exist, but they put your notes in someone's cloud, expose 30 tools the agent cannot choose between, and nobody shows you an eval.
brain-core is the opposite: local, five tools, markdown files you own, and a test suite that reports hit rates.
CLAUDE.md with the agent's name and yours, five rule files (identity, doctrine, authority, memory, system), three skills, a safety hook, an .mcp.json and an empty vault. Claude Code reads that folder as a project, so the agent knows how to use its memory from the first message.brain_session('start'), which returns one block: today's brief, the executive state, the mental models, a recall per active mission, and a flag if the previous session crashed. It closes with brain_session('end'), which files the day's archive and rewrites state for tomorrow.brain_remember(text, kind). The text goes to the vault first, then the SQLite index, then Hindsight, then the relations table, and the reply says what each layer did. A duplicate is skipped. A fact whose value changed gets a ⚠ Fact changed banner and the old line stays, so the history is visible.brain_recall(query) searches the vault, the index and Hindsight at once, deduplicates, ranks by relevance and recency, and caps the reply at 6k tokens so it never floods the context.brain daily writes the next morning's brief and backs up Hindsight. brain weekly archives sessions older than 30 days into a monthly summary and refreshes the mental models.flowchart LR
CC[Claude Code] -->|MCP, 5 tools| B[brain serve] B --> V[(vault/ markdown)] B --> S[(brain.db SQLite + FTS)] B --> H[(Hindsight vector memory)] B --> G[(relations table)] CRON[brain daily / weekly] --> V CRON --> H
| Tool | One call does |
|---|---|
brain_session('start') | the whole start block: daily brief, executive state, mental models, a recall per mission, inbox count, and a flag if the last session crashed |
brain_recall(query, scope) | one query across every store, the Claude Code transcripts of this folder and any stores.notes folders included, deduplicated, ranked by relevance and recency, capped at 6k tokens; scope='transcript' is what past sessions said and ran, useful on day one |
brain_remember(text, kind) | writes vault → SQLite → Hindsight → graph and reports each layer. Near-duplicates are skipped; a changed value gets a ⚠ Fact changed banner and the old line stays |
brain_distill(source) | captures a URL, GitHub repo, YouTube video, PDF, file or pasted text into an immutable raw/ folder for the agent to compile |
brain_session('end') | drains the queue, closes the day's session file, rewrites state and critique, writes the clean-close marker |
Plus brain_status() for health in one call: which stores are up, how many tokens the always-loaded context costs, whether a session is open, and which decisions are waiting on you.
| You need | Why | Check |
|---|---|---|
| macOS, or Linux with systemd | the installer sets up a background service and cron | uname |
about 2 GB of disk and 10 minutes, or --lite | Hindsight ships an embedded Postgres and a CPU embedding model; --lite skips it | |
an Anthropic API key, or a Claude Code login, or --lite | Hindsight uses an LLM to reason over memories | echo $ANTHROPIC_API_KEY |
| Claude Code | the agent runs inside it; the installer adds it if missing | claude --version |
Pick two names before you run the command: the agent's name (--agent), which becomes its folder and identity, and your own (--user), which is how the agent addresses you. Both can be changed later by editing CLAUDE.md.
curl -fsSL https://raw.githubusercontent.com/xy-claude/brain-core/main/install.sh | bash -s -- --agent Atlas --user Alex
In a hurry, or no 2 GB to spare? Add --lite: vault plus SQLite full-text search, no Hindsight, installed in about a minute. Everything in the five tools works; what you give up is semantic recall over paraphrases, mental models and the weekly reflection. The recall numbers in Does it work? are measured on exactly this configuration. Upgrade any time with brain hindsight install, then uncomment the hindsight: block in brain.yaml.
curl -fsSL https://raw.githubusercontent.com/xy-claude/brain-core/main/install.sh | bash -s -- --agent Atlas --user Alex --lite
What it does, in order. Re-running skips what is already there, so after a failure you fix the cause and run the same line again.
== 1/8 Xcode command line tools present
== 2/8 Homebrew present == 3/8 uv, gh, gitleaks, node, Claude Code == 4/8 brain-core (v0.4.0) installed with uv tool == 5/8 Agent Atlas at ~/Agents/Atlas 31 files written == 6/8 Hindsight (required store) service: healthy == 7/8 Cron daily 06:07, weekly Sun 07:13 == 8/8 Doctor Health check: OK
| Step | What happens | If it stops here |
|---|---|---|
| 1 | checks for git via the Xcode command line tools | macOS opens an install dialog; finish it, then re-run |
| 2 | installs Homebrew if missing | Homebrew asks for your password itself |
| 3 | installs uv, gh, gitleaks, node and Claude Code with Homebrew | anything already present is left alone |
| 4 | installs the brain command from PyPI with uv tool | --ref v0.4.0 pins a git tag instead |
| 5 | runs brain init and writes the agent folder | an existing brain.yaml is never overwritten |
| 6 | installs Hindsight as a launchd service on 127.0.0.1:8888 | first start downloads the embedding model; give it a few minutes |
| 7 | installs brain daily and brain weekly as launchd agents | |
| 8 | runs brain doctor on the new agent | brain doctor ~/Agents/Atlas repeats it any time |
Two things the installer cannot do for you:
export ANTHROPIC_API_KEY=sk-ant-... # add it to ~/.zshrc too
brain hindsight install # copies the key into ~/.config/hindsight/env (mode 600) and restarts the service claude # sign in to Claude Code once
The installer prints a note if the key was not in your shell when it ran. If you would rather not use an API key, pass --provider claude-code and Hindsight uses your Claude Code login instead. That mode is for personal use only.
| Flag | Meaning |
|---|---|
--agent NAME | the agent's name (required) |
--user Alex | how the agent addresses you |
--dir PATH | where the agent lives, default ~/Agents/NAME |
--provider | anthropic (default), openai, or claude-code (uses your Claude Code login; personal use only) |
--api-key-env VAR | read the key from a variable other than _API_KEY |
--profile DIR | a folder copied over the generic rules last, for your own doctrine |
--lite | skip Hindsight: vault + SQLite only, upgrade later |
--dashboard | the Hindsight web UI on http://localhost:9999 |
--ref v0.4.0 | pin a git tag instead of the PyPI release |
brain adopt ~/Agents/Atlas --vault ~/Agents/Atlas/vault --bank atlas-brain --user Alex
Adds brain.yaml, the brain MCP server, the four hooks and the memory rule to an existing Claude Code folder, then indexes its facts. CLAUDE.md, skills and the vault are left alone; omit --bank to run lite.
The same one line. It needs git and curl already present. It then installs uv from astral.sh, installs Claude Code with npm when node is present, runs Hindsight as a systemd --user service, and writes the two jobs into your user crontab as tagged lines it can find and replace on re-run.
uv tool install brain-core-mcp # or: uv tool install git+https://github.com/xy-claude/brain-core@v0.4.0
brain init Atlas --path ~/Agents/Atlas --user Alex brain hindsight install # launchd on macOS, systemd --user on Linux brain cron install ~/Agents/Atlas brain doctor ~/Agents/Atlas
brain doctor ~/Agents/Atlas
It prints the agent name, the config path, row counts per table, and Health check: OK. Store health shows up in the first brain_session('start') reply and in brain_status(). The common problems:
| Symptom | Cause | Fix |
|---|---|---|
brain: command not found | the uv tool bin folder is not on your PATH | uv tool update-shell, then open a new terminal |
ERROR: no brain.yaml at ... | wrong path | pass the agent folder, or the brain.yaml inside it |
| hindsight unreachable at http://127.0.0.1:8888 | the service i
Solo se muestra el principio; lee el resto en el repo