mcpField
B
brains

brains

Local
github.com/spacecowboyianMemory & Knowledge

About brains

Personal wiki and memory for AI assistants: store, search, and recall structured notes

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"spacecowboyian-brains": {
"command": "npx",
"args": [
"-y",
"brains-mcp"
],
"env": {
"WIKI_DIR": "<WIKI_DIR>",
"STORAGE_BACKEND": "<STORAGE_BACKEND>",
"GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<GOOGLE_CLIENT_SECRET>",
"GOOGLE_REFRESH_TOKEN": "<GOOGLE_REFRESH_TOKEN>",
"DRIVE_FOLDER_ID": "<DRIVE_FOLDER_ID>",
"SUPABASE_URL": "<SUPABASE_URL>",
"SUPABASE_SERVICE_ROLE_KEY": "<SUPABASE_SERVICE_ROLE_KEY>"
}
}
}
}
Run commandnpx -y brains-mcp
Environment variables to set
WIKI_DIRPath to local wiki directory (used when STORAGE_BACKEND=local or omitted)
STORAGE_BACKENDStorage backend: 'local' (default), 'supabase', or 'drive'
GOOGLE_CLIENT_IDGoogle OAuth client ID (required for Google Drive backend)
GOOGLE_CLIENT_SECRETSecretGoogle OAuth client secret (required for Google Drive backend)
GOOGLE_REFRESH_TOKENSecretGoogle OAuth refresh token (required for Google Drive backend)
DRIVE_FOLDER_IDGoogle Drive folder ID for wiki storage
SUPABASE_URLSupabase project URL (required for Supabase backend)
SUPABASE_SERVICE_ROLE_KEYSecretSupabase service role key (required for Supabase backend)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmbrains-mcp1.101.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.