Levirge Brain
Shared MCP memory for AI agents: knowledge base, skills, todos and agent-to-agent handoffs.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http levirge-brain 'https://brain.levirge.com/mcp'
{
"mcpServers": {
"levirge-brain": {
"type": "http",
"url": "https://brain.levirge.com/mcp"
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Brain — persistent memory for your AI agents
Your agents forget everything between sessions. Brain doesn't.
Brain is a hosted knowledge base your AI agents read and write over MCP — architecture decisions, runbooks, hard-won gotchas, and agent-to-agent handoffs, searchable from Claude Code, Codex, and any MCP-compatible client. Stop re-explaining your stack to every new session.
Install (2 minutes)
Claude Code:
claude plugin marketplace add levirge/brain
claude plugin install brain@levirge-brain
Then run /mcp in a session and sign in.
Codex CLI:
codex plugin add levirge/brain
Cline, or any MCP client — remote server, no install:
{ "mcpServers": { "brain": { "type": "streamableHttp", "url": "https://brain.levirge.com/mcp" } } }
That is Cline's spelling of the transport type; other clients name it differently. OAuth sign-in on first connect. Details: llms-install.md.
What you get
- Search-first memory —
search_knowledgewith semantic search + reranking; agents cite what they read instead of hallucinating. - Write-back that compounds —
add_knowledgecaptures decisions and fixes once; every future session starts warmer. - Fact lineage — trace any answer back to the documents and atoms it came
from (
/brain:lineage). - Agent-to-agent handoffs — a shared inbox between agents and machines:
hand work from one session, role, or CLI to another (
/brain:handoff). - Work sessions & context packs —
/brain:startpulls the right context for a task;/brain:finishpersists what was learned. - Self-improving ranking —
feedback(helpful / dead-end verdicts) tunes retrieval to how your team actually works.
Works with your models
Measured in a 10-task × 3-repeat bake-off (fixed judge): Claude Opus-class models ground perfectly, and the bundled search-first contract doubled retrieval compliance on a local 26B. Details in plugins/brain/README.md.
Links
- App / sign in: https://brain.levirge.com
- Levirge: https://levirge.com
- Plugin reference: plugins/brain/README.md
Plugin versioning is semver, independent of the Brain server release.
Questions fréquentes
Qu'est-ce que Levirge Brain ?
Shared MCP memory for AI agents: knowledge base, skills, todos and agent-to-agent handoffs.
Comment installer Levirge Brain ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http levirge-brain 'https://brain.levirge.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Levirge Brain ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Levirge Brain est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient Levirge Brain ?
Il est publié par levirge. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.