Vestige MCP Server

What the code does

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

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.

postinstall: node scripts/postinstall.js

  const result = spawnSync(process.execPath, [installerPath], {

  const binaryPath = path.join(__dirname, binaryName);

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        self.process = subprocess.Popen(

  $memList.innerHTML = html;

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 vestige -- npx -y vestige-mcp-server

{
  "mcpServers": {
    "vestige": {
      "args": [
        "-y",
        "vestige-mcp-server"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.vestige]
command = "npx"
args = ["-y", "vestige-mcp-server"]

{
  "mcpServers": {
    "vestige": {
      "args": [
        "-y",
        "vestige-mcp-server"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "vestige": {
      "args": [
        "-y",
        "vestige-mcp-server"
      ],
      "command": "npx"
    }
  }
}