session-recap MCP Server

What the code does

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

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.

      const child = spawn(tries[i], ['-I', digest, ...args], { stdio: ['ignore', 'pipe', 'pipe'] })

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.

    spawn(cmd, args, { stdio: 'ignore', detached: true }).unref()

    proc = subprocess.Popen(["zstd", "-dc", "--", path], stdout=subprocess.PIPE, stderr=subprocess.DEVNULL)

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 session-recap -- npx -y session-recap

{
  "mcpServers": {
    "session-recap": {
      "command": "npx",
      "args": [
        "-y",
        "session-recap"
      ]
    }
  }
}

[mcp_servers.session-recap]
command = "npx"
args = ["-y", "session-recap"]

{
  "mcpServers": {
    "session-recap": {
      "command": "npx",
      "args": [
        "-y",
        "session-recap"
      ]
    }
  }
}

{
  "servers": {
    "session-recap": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "session-recap"
      ]
    }
  }
}