M
ModelBrain/modelbrain-mcp
ModelBrain is a local-first memory layer that gives Claude, ChatGPT and Cursor one shared memory, kept on your own computer.
updated 2026-11-15
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · ModelBrain/modelbrain-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
ModelBrain/modelbrain-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# modelbrain-mcp
Excerpted from the repository README (abridged)
ModelBrain is a local-first memory layer that gives Claude, ChatGPT and Cursor one shared memory, kept on your own computer. Free for one person, no account.
This package is a thin MCP stdio client for it. If you sync your memory to your other computers or share it with a team, the copy ModelBrain stores is encrypted on your computer first, and ModelBrain does not hold the key.
This package does not install or bundle ModelBrain. It connects to the ModelBrain desktop app already running on your machine.
## If ModelBrain is not installed
The launcher still starts and answers the MCP handshake, so your client shows the server and its tools instead of a start-up failure. Every tool call then returns one plain result: ModelBrain is not installed, and where to get it. Nothing is stored or recalled in this state. The same message is printed to standard error.
The tool list it shows comes from bin/tools.json, a copy of what the real server reports. Maintainers refresh it with npm run snapshot-tools on a machine that has ModelBrain installed.
To get the old behaviour, where the launcher exits with status 1 when the app is missing, pass --require-app or set MODELBRAIN_MCP_REQUIRE_APP=1.
## Why a separate package
ModelBrain's own installed app already ships a binary, mcp_server, that speaks MCP over stdio and talks to the local ModelBrain daemon. This package finds that binary on the current machine and runs it. It exists so ModelBrain can be registered with the MCP Registry and the directories that list from it, with a reviewable package as the distribution target, while the actual engine stays out of this repository.
## Requirements
macOS (Apple Silicon), Windows (x64 or arm64) or Linux (x86_64 or aarch64, glibc 2.28 or newer)
ModelBrain installed
## Use
In ModelBrain's Allow or Block prompt this client shows up as your assistant's name with node as the program (mcp_server.exe on Windows). If you turn on Require client tokens in ModelBrain, mint a token for your assistant with modelbrain_admin setup tokens --mint NAME and put it in your client's env block as MODELBRAIN_CLIENT_TOKEN; the launcher passes it through.
Most MCP clients run a server with npx. Point your client's MCP config at:
json
"mcpServers": {
This package is a thin MCP stdio client for it. If you sync your memory to your other computers or share it with a team, the copy ModelBrain stores is encrypted on your computer first, and ModelBrain does not hold the key.
This package does not install or bundle ModelBrain. It connects to the ModelBrain desktop app already running on your machine.
## If ModelBrain is not installed
The launcher still starts and answers the MCP handshake, so your client shows the server and its tools instead of a start-up failure. Every tool call then returns one plain result: ModelBrain is not installed, and where to get it. Nothing is stored or recalled in this state. The same message is printed to standard error.
The tool list it shows comes from bin/tools.json, a copy of what the real server reports. Maintainers refresh it with npm run snapshot-tools on a machine that has ModelBrain installed.
To get the old behaviour, where the launcher exits with status 1 when the app is missing, pass --require-app or set MODELBRAIN_MCP_REQUIRE_APP=1.
## Why a separate package
ModelBrain's own installed app already ships a binary, mcp_server, that speaks MCP over stdio and talks to the local ModelBrain daemon. This package finds that binary on the current machine and runs it. It exists so ModelBrain can be registered with the MCP Registry and the directories that list from it, with a reviewable package as the distribution target, while the actual engine stays out of this repository.
## Requirements
macOS (Apple Silicon), Windows (x64 or arm64) or Linux (x86_64 or aarch64, glibc 2.28 or newer)
ModelBrain installed
## Use
In ModelBrain's Allow or Block prompt this client shows up as your assistant's name with node as the program (mcp_server.exe on Windows). If you turn on Require client tokens in ModelBrain, mint a token for your assistant with modelbrain_admin setup tokens --mint NAME and put it in your client's env block as MODELBRAIN_CLIENT_TOKEN; the launcher passes it through.
Most MCP clients run a server with npx. Point your client's MCP config at:
json
"mcpServers": {
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/modelbrain-modelbrain-mcp/)
- Source
- awesome · https://github.com/ModelBrain/modelbrain-mcp
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.