br8n
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@br8n search my brain for the decision on pricing"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
br8n
Owned, portable working memory. A plain-files brain template and a tiny MCP server that lets any model read it.
Everything your team has taught a chat tool about how the work gets done is sitting inside somebody else's login. Switch tools and you're a stranger again. This repo is the other direction: the memory lives in files you own, and the model is just a reader.
br8n is the AI delivery practice of Branded Mayhem Collective. This is the open part: the file layout and the door. The hosted install adds retrieval, governance, and someone running it with you — on the same files, which never change shape. br8n.io
What's here
template/brain/— the brain layout:how-we-work/,decisions/,exceptions/,handoffs/,voice/. Markdown only. One file, one thing. Write the why, so the model can push back later.src/— an MCP server (stdio) with three tools:brain_list,brain_read,brain_search. Search returns file + line so answers cite their source. No vectors, no index, no account. Grep is the point.
Related MCP server: Universal Memory MCP Server
Use it
npx @br8n/mcp ~/my-brain # MCP server on stdio (or: npm i -g @br8n/mcp && br8n ~/my-brain)
# template: git clone https://github.com/Branded-Mayhem-Collective-LLC/br8n && cp -r br8n/template/brain ~/my-brainClaude Desktop / Claude Code / Cursor (any MCP client) — add:
{ "mcpServers": { "br8n": { "command": "npx", "args": ["-y", "@br8n/mcp", "/path/to/my-brain"] } } }Then ask the model something the brain knows. It answers from the file and names it. Switch the model; same answer, same file.
Why files
Portable.
cp -r brain/ new-machine/is the whole migration. If you can't do that, you don't own it.Inspectable. You can read every byte the model reads.
Model-agnostic. The folder doesn't care which model is on the other side of MCP.
It can push back. A decision stored with its why lets a model say "this conflicts with what you decided in March." A chat history can't.
The method is public on purpose
The layout and this server are MIT. What br8n charges for is hands on a real operation: eliciting what's actually in people's heads, shaping retrieval for the role, running it, and keeping it current. If you'd rather do it yourself, start here — most people should. The free first course is at br8n.io/lab.
Not affiliated
br8n on PyPI (a context-capture engine by a different author) is not this project.
MIT © 2026 Branded Mayhem Collective LLC
Publishing (maintainers)
Configure npm's trusted publisher once for @br8n/mcp:
Publisher: GitHub Actions
Organization:
Branded-Mayhem-Collective-LLCRepository:
br8nWorkflow:
publish.ymlAllowed action:
npm publish
Publish the version already committed to main, then update the official MCP Registry:
gh workflow run publish.yml --ref main -f version=0.1.2
gh run watch --exit-status
mcp-publisher login github
mcp-publisher publishThe GitHub-hosted workflow uses npm trusted publishing (OIDC), so it requires no long-lived npm token. Change the version argument for future releases.
Available Tools
3 toolsbrain_listARead-onlyIdempotent
List every markdown file in the brain (relative path, size, last modified).
Inputs: no named parameters.
brain_readARead-onlyIdempotent
Read one file from the brain by relative path (e.g. decisions/2026-03-change-orders.md).
Inputs: path (required).
brain_searchARead-onlyIdempotent
Literal, case-insensitive search across the brain. Returns file, line number and the matching line, so answers can cite the source.
Inputs: query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool targets a distinct operation: listing all files, reading a specific file, and searching content. There is no overlap or ambiguity in their purposes.
All tools consistently use the 'brain_' prefix with a simple verb pattern (list/read/search), making the API predictable and easy to navigate.
Three tools is minimal but well-scoped for a read-only markdown knowledge base. Each tool serves a necessary and non-redundant function.
The set fully covers the core retrieval workflows: browsing the structure, reading files, and searching content. Write or management operations are absent, but they appear outside the server's stated read-only scope.
Maintenance
Related MCP Connectors
One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.
Shared long-term memory vault for AI agents with 20 MCP tools.
Shared memory for your AI tools: tasks, notes and context every tool can read and write over MCP.
An MCP memory server. One memory your agents share — across models, devices and apps.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server providing persistent brain storage for LLM agents, including memory, personality, social intelligence, and context management.1MIT
- AlicenseNot gradedqualityDmaintenanceA portable MCP server providing a shared intelligent memory system for any MCP-compatible AI tool, enabling storage, retrieval, extraction, and governance of memories across sessions.16 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides a file-first personal memory layer for AI agents, enabling them to store and retrieve memories as markdown files with an SQLite index. The MCP server offers read-only search by default, with optional write tools for manual memory addition and conflict resolution.2 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that turns a git-versioned Markdown vault into a queryable memory for AI agents, providing tools like brain_search, brain_read, and brain_neighbors.Apache 2.0