Korg Ledger MCP Server

What the code does

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

            self._process = subprocess.Popen(

        resolved = (os.path.join(root, path)

    def exec(self, code: str, fuel: dict,

            command, shell=True, input=json.dumps(payload),

        env = dict(os.environ)

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-ledger -- uvx korgex

{
  "mcpServers": {
    "korg-ledger": {
      "args": [
        "korgex"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.korg-ledger]
command = "uvx"
args = ["korgex"]

{
  "mcpServers": {
    "korg-ledger": {
      "args": [
        "korgex"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "korg-ledger": {
      "args": [
        "korgex"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: KORG_JOURNAL_PATH (Path to the JSONL ledger journal (defaults to .korg/journal.jsonl).), KORG_LEDGER_HMAC_KEY (Optional HMAC key — makes the chain tamper-PROOF, not just tamper-evident.). The author declared them in the registry entry; get the values from the project itself.