M1nd MCP Server

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

    let body = fs::read_to_string(&path).map_err(|error| M1ndError::InvalidParams {

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const res = await deps.spawn(args.storeVersion);

    proc = subprocess.Popen([_BIN_PATH, "--stdio", "--no-gui"], stdin=subprocess.PIPE,

    env = dict(os.environ)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add m1nd -- npx -y @maxkle1nz/m1nd

{
  "mcpServers": {
    "m1nd": {
      "args": [
        "-y",
        "@maxkle1nz/m1nd"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.m1nd]
command = "npx"
args = ["-y", "@maxkle1nz/m1nd"]

{
  "mcpServers": {
    "m1nd": {
      "args": [
        "-y",
        "@maxkle1nz/m1nd"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "m1nd": {
      "args": [
        "-y",
        "@maxkle1nz/m1nd"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: M1ND_WORKSPACE_ROOT (Workspace root to bind the graph to (defaults to the current working directory)). The author declared them in the registry entry; get the values from the project itself.