Levirge Brain

Official registry AI and agents

Shared MCP memory for AI agents: knowledge base, skills, todos and agent-to-agent handoffs.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http levirge-brain 'https://brain.levirge.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "levirge-brain": {
            "type": "http",
            "url": "https://brain.levirge.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Brain — persistent memory for your AI agents
  2. Install (2 minutes)
  3. What you get
  4. Works with your models
  5. Links

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_knowledge with semantic search + reranking; agents cite what they read instead of hallucinating.
  • Write-back that compounds — add_knowledge captures 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:start pulls the right context for a task; /brain:finish persists 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.

Plugin versioning is semver, independent of the Brain server release.

Frequently asked questions

What is Levirge Brain?

Shared MCP memory for AI agents: knowledge base, skills, todos and agent-to-agent handoffs.

How do I install Levirge Brain?

It runs as a remote server. In Claude Code: claude mcp add --transport http levirge-brain 'https://brain.levirge.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Levirge Brain need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Levirge Brain open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Levirge Brain?

It is published by levirge. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.