M3 Memory MCP Server

What the code does

We read the source, 22 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.

        return subprocess.run(cmd, timeout=timeout).returncode  # nosec B603 - argv list, no shell

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.

_LAUNCHD_PLIST = "~/Library/LaunchAgents/com.m3memory.cognitiveloop.plist"

этот файл ставится пользователю, но в репозитории его нет

    path = os.path.join(chatlog_config.SPILL_DIR, f"{day}.jsonl")

        result = subprocess.run(

    exec(code, {"__file__": str(bridge), "__name__": "__main__"})  # nosec B102

    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 m3-memory -- uvx m3-memory

{
  "mcpServers": {
    "m3-memory": {
      "args": [
        "m3-memory"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.m3-memory]
command = "uvx"
args = ["m3-memory"]

{
  "mcpServers": {
    "m3-memory": {
      "args": [
        "m3-memory"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "m3-memory": {
      "args": [
        "m3-memory"
      ],
      "command": "uvx"
    }
  }
}