Korg Recall MCP Server

What the code does

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

    let mut cmd = Command::new(&req.command);

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(binaryPath, ["--introspect"], {

        result = subprocess.run(

    blob_path = os.path.join(blob_dir, sha256)

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 korg-recall-mcp -- npx -y @korgg/recall-mcp

{
  "mcpServers": {
    "korg-recall-mcp": {
      "args": [
        "-y",
        "@korgg/recall-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.korg-recall-mcp]
command = "npx"
args = ["-y", "@korgg/recall-mcp"]

{
  "mcpServers": {
    "korg-recall-mcp": {
      "args": [
        "-y",
        "@korgg/recall-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "korg-recall-mcp": {
      "args": [
        "-y",
        "@korgg/recall-mcp"
      ],
      "command": "npx"
    }
  }
}