Brains

Brains runs locally from a Node.js package published to the npm registry: brains-mcp version 1.94.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y brains-mcp@1.94.1. It reads these environment variables: WIKI_DIR, STORAGE_BACKEND, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), GOOGLE_REFRESH_TOKEN (secret), DRIVE_FOLDER_ID, SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY (secret); set them in the client's configuration for this server. Required arguments: BRAINS_TRANSPORT.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "brains": {
      "command": "npx",
      "args": [
        "-y",
        "brains-mcp@1.94.1"
      ],
      "env": {
        "WIKI_DIR": "<value>",
        "STORAGE_BACKEND": "<value>",
        "GOOGLE_CLIENT_ID": "<value>",
        "GOOGLE_CLIENT_SECRET": "<secret>",
        "GOOGLE_REFRESH_TOKEN": "<secret>",
        "DRIVE_FOLDER_ID": "<value>",
        "SUPABASE_URL": "<value>",
        "SUPABASE_SERVICE_ROLE_KEY": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect