memi MCP Server

What the code does

We read the source, 4 d ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

const child = spawn(executable, args, {

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 child = spawn(executable, args, {

        const target = path.join(input.captureRoot, capture.artifactName);

        console.log(`\n${ui.fail(`Update failed. Try manually:  ${formatUpdateFailureGuidance(latest)}`)}\n`);

  el.innerHTML = html;

      "Preserve npm’s effective cache, including .npmrc configuration, before packed and upgrade installers isolate their environment. Only the cache path is forwarded; credentials remain excluded. Prefer verified cached packages with network fallback and label install timeouts…

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 memi -- npx -y @memi-design/cli

{
  "mcpServers": {
    "memi": {
      "command": "npx",
      "args": [
        "-y",
        "@memi-design/cli"
      ]
    }
  }
}

[mcp_servers.memi]
command = "npx"
args = ["-y", "@memi-design/cli"]

{
  "mcpServers": {
    "memi": {
      "command": "npx",
      "args": [
        "-y",
        "@memi-design/cli"
      ]
    }
  }
}

{
  "servers": {
    "memi": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@memi-design/cli"
      ]
    }
  }
}