Brainbox

dev.thexiPublished by thexi.devOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Gives an AI assistant a persistent, portable private memory graph that any MCP client can read from and write to.

What you can do
Brainbox is a hosted memory service reached over streamable HTTP. According to its description, it keeps a persistent, portable memory graph for AI assistants, so context can carry across sessions and across different MCP clients rather than living inside one chat. The manifest does not list individual tools, so the exact read and write operations are not documented here.
When to use it
Worth considering when you want an assistant to remember information between conversations or share the same memory across several MCP clients, and you are comfortable with that memory being held by a remote hosted service.
Requirements
A remote MCP client that supports streamable HTTP, connected to the provider's endpoint. Authentication is by OAuth and is required; no environment variables or headers are declared.
Before you install
Memory content is stored with a third-party hosted service, so anything the assistant writes there leaves your machine. OAuth grants the server access under your account. The manifest does not list the tools, so what can be written, read, or deleted is not documented here; review the provider's terms and data handling before storing sensitive information.

Installation

In SourceWeft

  1. Open Brainbox in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.thexi%2Fbrainbox/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "brainbox": {
      "type": "http",
      "url": "https://brainbox-mcp.thexi.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.