Nightly builds (unstable)

Nightly builds let you try unreleased changes from main before they ship in a tagged release. A new nightly is published automatically each night that main has changed.

Unstable

Nightly builds are not release-tested and may contain breaking or incomplete changes. Don't use them in production. For stable use, install the default (tagged) release instead.

Install

npm

{
  "mcpServers": {
    "fireflyiii": {
      "command": "npx",
      "args": ["-y", "@daften/fireflyiii-mcp@nightly"],
      "env": {
        "FIREFLY_URL": "https://your-firefly-instance.example.com",
        "FIREFLY_TOKEN": "your-personal-access-token-here"
      }
    }
  }
}

The @nightly tag is what pins you to the nightly channel. Drop it to return to the latest tagged release.

Docker

docker pull ghcr.io/daften/fireflyiii-mcp:nightly

How nightlies are versioned

Each nightly is published as a SemVer pre-release, for example 0.2.2-nightly.20260614T0300. Because it is a pre-release:

• A normal install with no tag always resolves to the latest tagged release — never a nightly. On npm the latest dist-tag is never moved to a nightly; on Docker the :latest tag is never moved either.
• Version-range installs (for example ^0.2.1) also skip nightlies, because npm excludes pre-releases from ranges unless you explicitly opt in.

You only ever receive a nightly by explicitly requesting the @nightly (npm) or :nightly (Docker) tag.

Going back to a stable build

Reinstall without the nightly tag:

npx -y @daften/fireflyiii-mcp          # latest tagged release
docker pull ghcr.io/daften/fireflyiii-mcp:latest