mcpField
L
Levirge Brain

Levirge Brain

Remote
levirge.comMemory & Knowledge0Updated 2w ago

About Levirge Brain

Levirge Brain is a hosted knowledge base for AI agents, preserving decisions, runbooks, fixes, and handoffs across sessions. Agents access and update shared memory through MCP.

Key features

  1. 01Semantic search with reranking
  2. 02Write and retrieve shared knowledge
  3. 03Trace answers to source documents
  4. 04Agent-to-agent handoff inbox
  5. 05Task context packs and work sessions
  6. 06Feedback-tuned retrieval

Use cases

  1. 01Reuse architecture decisions across sessions
  2. 02Look up runbooks and known fixes
  3. 03Hand work between agents or CLIs
  4. 04Save task findings for later sessions

MCP support

Exposes shared memory capabilities to MCP clients, including knowledge search and writes, lineage, and handoffs.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://brain.levirge.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Levirge Brain

version

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.

Links

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.