# Brainbox [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://brainbox.thexi.dev  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/brainbox

## Description
Persistent, portable memory for AI assistants — your private memory graph, from any MCP client.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "brainbox": {
    "command": "npx",
    "args": ["-y","brainbox"]
  }
}
```

## Documentation

## What Brainbox MCP server does

The Brainbox MCP server is intended to give AI assistants persistent memory through a private memory graph. Its central purpose is to preserve assistant memory beyond an individual interaction, rather than limiting context to the current conversation. The memory is described as portable, so it is intended to remain usable across different MCP clients instead of being tied to one assistant application.

This makes Brainbox relevant for workflows where an assistant needs continuity over time. Examples include retaining information that should remain available in later sessions or using a consistent memory layer while changing MCP clients. The supplied material does not identify a specific data domain, such as contacts, documents, tasks, or code repositories, so those use cases should not be assumed.

## How it works

Brainbox represents the assistant’s private memory as a graph and exposes that memory through MCP. An MCP-compatible client can therefore use Brainbox as its memory service. The description states that it works from any MCP client, but it does not provide the names of supported clients or explain the exact MCP transport.

The available information also does not describe how memories are created, queried, updated, deleted, indexed, or connected within the graph. It confirms the intended characteristics—persistent, portable, and private memory—but not the underlying database, hosting model, synchronization behavior, or data format.

## Limitations and notes

The source material is limited to a short product description and does not include a README. As a result, there is no grounded information about installation, configuration, required environment variables, authentication, licensing, pricing, client-specific setup, or named MCP tools.

Developers evaluating the Brainbox MCP server should verify those details at the project source before deployment. In particular, confirm where the memory graph is stored, how privacy is enforced, whether data can be exported, and which MCP clients have been tested. The phrase “from any MCP client” describes the intended portability, but it does not by itself establish compatibility with every client implementation.

Based on the available description, Brainbox is best understood as a portable memory layer for AI assistants rather than a general-purpose knowledge base, search service, or document retrieval system. The Brainbox MCP server may fit applications that need continuity across sessions, provided the missing operational and security details meet the project’s requirements.

_Full upstream README: https://allmcps.com/mcp/brainbox/readme_