Privacy
What leaves your machine.
The tool and this website are two different things with two different answers, and lumping them together would be the easy dishonest move. They are separated below.
The tool: telemetry is gone
brain-mcp used to ship anonymous usage telemetry. It was removed entirely in 0.4.1 and the endpoint it posted to was retired. The current release is 2.0.0-beta.1, which also dropped the only two modules that ever reached the network — the package no longer ships an HTTP client of any kind.
The module still exists so that old imports do not crash, but every function in it now returns None and does nothing. You can read the whole thing in under a minute:
$ cat $(python3 -c "import brain_mcp,os;\
print(os.path.dirname(brain_mcp.__file__))")/telemetry.py
"""brain-mcp telemetry — REMOVED in 0.4.1.
Telemetry was removed entirely (and the endpoint it posted
to was retired). This module remains as a no-op shim so
existing imports keep working.
brain-mcp makes zero network calls at runtime.
"""
def is_enabled() -> bool: return False
def track(event, props=None): return None
def track_tool(...): return None
def flush() -> None: return NoneThe recording path and the MCP server make no network calls at all. Hooks, watchers, the spool, the floor, the manifest, the DuckDB cache and every recall tool run entirely on your machine, against files in your home directory. There is no account, no sync, no server component, and nothing to sign up for.
Prove it with one grep
Do not take that on trust — it is a claim about a codebase, and codebases change. A package that cannot make an HTTP request is a checkable property, so check it. Grep the installed package for every HTTP client Python has:
grep -rn "import httpx\|import requests\|import urllib.request\|\
import socket\|import openai\|import anthropic" \
$(python3 -c "import brain_mcp,os;\
print(os.path.dirname(brain_mcp.__file__))")As of 2.0.0-beta.1 this returns nothing. Earlier releases did have two opt-in paths that reached the network — a summarizer that called whichever LLM provider you configured, and a dashboard route that validated a pasted OpenRouter key. Both modules were removed in the 2.0 recorder rewrite; the package is now just the ingest and recorder trees.
If that grep ever returns a hit, this page is out of date and you should trust the grep, not the page. That is the intended relationship between the two.
Removing something you recorded
An append-only floor raises an obvious question: what if a transcript captured a credential, or something you simply do not want kept? brain-mcp redact replaces a span with a tombstone and records the redaction in the manifest. The content goes; the fact that a redaction happened stays, because a record that can be silently edited is not a record.
This website measures you. Here is exactly how.
brainmcp.dev is a marketing site and it is instrumented like one. That has nothing to do with the tool you install, but claiming the site were clean would be the same species of lie this whole project exists to avoid.
Vercel Analytics and Speed Insights
Aggregate page views and performance timings, collected by Vercel, our host. No cookie is set for this and visitors are not identified across sites.
A first-party event log
The site also records its own events — page views, time on page, which install command got copied — into a Supabase database owned by the author. Each event carries the page path, the referrer, any utm_* parameters in the URL, a coarse operating system guess derived from your user agent, and a random session identifier.
- →The session identifier is a random UUID stored in
localStorageunder_bmcp_sid. It is not a cookie, but it does persist across visits until you clear site data — so calling this site cookie-free would be a technicality, not an honest answer. - →No name, email, account or IP address is recorded in these events. There is nothing to log into.
- →If your browser sends
Do Not Track, the event log is skipped entirely. Blocking the request, or clearinglocalStorage, also works and breaks nothing.
None of this touches the tool. Installing brain-mcp does not connect it to this site, and the site never receives anything about what you record or search.
In short
| Your transcripts | Never leave your machine. |
| The package (2.0.0-beta.1) | Ships no HTTP client at all. No network calls, no account, no sync. |
| Telemetry | Removed in 0.4.1. The shim that remains is a no-op you can read. |
| Redaction | brain-mcp redact tombstones a span and records the redaction in the manifest. |
| This website | Vercel Analytics + a first-party event log with a localStorage session id. Honours Do Not Track. |
| Licence | MIT. |