How to Get the Latest Updates for DeusData codebase-memory-mcp

Run codebase-memory-mcp update to automatically fetch and install the latest release from GitHub, or reinstall using the one-line installer script to get the newest version with checksum verification and daemon support.

The DeusData/codebase-memory-mcp repository provides multiple mechanisms to keep your memory tool current, ranging from native CLI commands to automated installation scripts. These methods ensure you can quickly upgrade across Linux, macOS, and Windows platforms while maintaining verification safeguards.

Update via the Built-In CLI Command

The update subcommand offers the fastest upgrade path and is implemented directly in the codebase-memory-mcp binary (built from the src/ directory). When executed, it queries the GitHub release feed and performs an atomic replacement of your installed binary if a newer version exists.

According to the documentation in README.md (lines 156‑162) under the "Keeping Up to Date" section, this method requires no external dependencies beyond your existing installation:

codebase-memory-mcp update

This command handles the entire update process—including checksum verification—ensuring you always have the latest release without manual package management.

Reinstall Using the Automatic Installer

To perform a complete fresh installation that always pulls the latest release, use the one-line installer. This method leverages scripts/setup.sh as a convenience wrapper to fetch artifacts from GitHub, while scripts/install.sh handles binary verification and system placement.

Run the standard headless installation:

curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh | bash

To enable the UI variant, append the --ui flag to the installation command:

curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh \
  | bash -s -- --ui

This approach is ideal when switching between UI and headless modes or ensuring the update-checking daemon is properly configured alongside the binary.

Manual Update from GitHub Releases

For environments requiring offline-capable or highly controlled updates, manually download the release archive from the GitHub "Latest release" page. Extract the appropriate tar or zip file for your platform and execute the bundled installation script.

On Unix systems, run the local install.sh after extraction:

./install.sh

On Windows, use PowerShell to download the archive and execute install.ps1 (located in the scripts/ directory):

Invoke-WebRequest -Uri https://github.com/DeusData/codebase-memory-mcp/releases/latest/download/codebase-memory-mcp-windows-amd64.zip -OutFile cbm.zip
Expand-Archive cbm.zip -DestinationPath .
.\install.ps1

Both platform-specific scripts perform the same rigorous checksum verification and binary placement as the automated curl-based installer.

Background Update Notifications

The update-checking daemon runs automatically when installed via the setup scripts (install.sh or install.ps1). This daemon verifies your installed version against GitHub releases on every tool startup. If a newer release is detected, it displays a notification banner in your agent console during the first tool call, ensuring you never miss critical updates even when relying exclusively on CLI usage.

Summary

• Run codebase-memory-mcp update for the quickest, atomic update that replaces only the binary via the built-in subcommand.
• Use the one-line curl installer to perform a fresh installation via scripts/install.sh and scripts/setup.sh, with optional --ui flag support.
• Download manually from GitHub releases and run install.sh (Unix) or install.ps1 (Windows) for controlled, offline-capable updates with checksum verification.
• Rely on the background daemon for passive notifications that alert you to new versions on startup without manual checking.

Frequently Asked Questions

How does the codebase-memory-mcp update command work?

The built-in update command queries the GitHub release feed to compare your current binary against the latest available version. If a newer release exists, it automatically downloads the appropriate asset, verifies its checksum, and replaces your installed binary atomically without requiring external scripts.

What is the difference between the update command and the installer script?

The update command modifies your existing installation by checking GitHub releases and replacing only the binary, while the installer script (implemented in scripts/install.sh and scripts/setup.sh) performs a complete fresh installation that can also configure the update-checking daemon and optionally enable UI support via the --ui flag.

How do I enable automatic update notifications?

Automatic notifications are handled by the update-checking daemon, which is installed automatically when you use the install.sh or install.ps1 scripts. This daemon checks for new releases every time the tool starts and displays a banner notification during the first tool call if a newer version is available.

Can I update codebase-memory-mcp on Windows using PowerShell?

Yes, Windows users can update manually by downloading the latest codebase-memory-mcp-windows-amd64.zip from the releases page, extracting it, and running the bundled install.ps1 script from the scripts/ directory. This PowerShell script performs the same checksum verification and binary installation as the Unix-based install.sh counterpart.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}