MELRA MCP Server

What the code does

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

  "doas", "gsudo", "ksu", "pfexec", "pkexec", "run0", "runas", "runuser", "su",

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.

      existsSync("/.dockerenv") || existsSync("/run/.containerenv"),

    const child = spawn(claude, claudeLaunchArgv(file, passed), { cwd: env.workspaceRoot, stdio: "inherit" });

COPY package.json pnpm-lock.yaml pnpm-workspace.yaml tsconfig.base.json .npmrc ./

        ...Object.fromEntries(Object.entries(process.env).filter(([name]) => !withheld.has(name.toUpperCase()))),

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

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

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

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

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