Skip to content

Installation

Install the machine-memory CLI, or set up MCP-only agent access without a binary.

Updated View as Markdown
For humans

Choose the path that matches how you use Machine Memory.

CLI

Install the standalone machine-memory binary when you want local setup, remote provision, or agent commands from the terminal.

Download

Download the binary for your platform from the latest GitHub release:

Binaries are not signed; OS that do require it will reject its execution

Quick install

macOS and Linux

curl -fsSL https://machine-memory.jfa.dev/install | bash

Windows PowerShell

irm https://machine-memory.jfa.dev/install.ps1 | iex

Add $HOME/.local/bin to PATH if it is not already there, then verify the installation:

machine-memory --version

Both quick-install scripts verify the downloaded archive’s SHA-256 digest against the release checksums.txt asset and abort on a mismatch.

Manual install

Extract the release archive for your platform. Put the executable anywhere on your PATH.

For UNIX users, you may need to make it executable:

chmod +x machine-memory

Check Troubleshooting for solutions to common problems.

Next steps

After the binary is on your PATH:

MCP

Use this path when agents talk to the remote MCP server and you do not need the CLI binary.

  1. Deploy the stack if you do not already have one: Infrastructure

  2. Follow MCP setup (enable OAuth, connect a client, tools)

  3. Run the public init script to write AGENTS.md:

    curl -fsSL https://machine-memory.jfa.dev/init-mcp | bash

    On Windows:

    irm https://machine-memory.jfa.dev/init-mcp.ps1 | iex

More detail: MCP Init.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close