server-memory 0.6.3 is not available on npm

[BRO3886]

Describe the bug
Unable to set the custom file path via npx since the npm registry does not have the latest version of server-memory

To Reproduce

• https://www.npmjs.com/package/@modelcontextprotocol/server-memory?activeTab=versions
• 04209ec

Expected behavior
0.6.3 should be available on NPM. Thanks a lot!

[edobez]

Related to #220

[IzumiSy]

Why hasn't that been published yet? I really need that.

[wcygan]

@ashwin-ant @dsp-ant @jspahrsummers can this please have some attention? The fix is there, yet users are needlessly rolling-their-own because of the lack of support.

---

Context:

The commit 04209ec fixes the issue, but it has not yet been published to NPM.

Package: https://www.npmjs.com/package/@modelcontextprotocol/server-memory
Collaborator 1: https://www.npmjs.com/~jspahrsummers
Collaborator 2: https://www.npmjs.com/~thedsp
Collaborator 3: https://www.npmjs.com/~ashwin-ant

[olaservo]

I opened a PR to trigger a publish to NPM here: #1518

I believe there was some timing issue between when the auto-publish process was implemented and when the last code changes were made to the repo. This should force a new version.

[wcygan]

Thank you @olaservo!

I notice that the GitHub Action for typescript publish is skipped, which seems like the culprit?

Ref: https://github.com/modelcontextprotocol/servers/actions/runs/14576064001/job/40882362621

Perhaps there is something wrong with the typescript publish action

Maybe it needs to have a release cut for it to trigger the publish?

  publish:
    runs-on: ubuntu-latest
    needs: [build, detect-packages]
    if: github.event_name == 'release'
    environment: release

    strategy:
      matrix:
        package: ${{ fromJson(needs.detect-packages.outputs.packages) }}
    name: Publish ${{ matrix.package }}

    permissions:
      contents: read
      id-token: write

    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 22
          cache: npm
          registry-url: "https://registry.npmjs.org"

      - name: Install dependencies
        working-directory: src/${{ matrix.package }}
        run: npm ci

      - name: Publish package
        working-directory: src/${{ matrix.package }}
        run: npm publish --access public
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

[olaservo]

@wcygan I think that's expected, since the newer automated release process is a scheduled process that checks for code changes, then auto-creates releases which then need to be approved by someone on the core team: https://github.com/modelcontextprotocol/servers/actions/workflows/release.yml

This worked recently for some other npm packages that needed to get updated, so as long as we see this one pop up in the auto-generated release tonight/tomorrow, we should be good to have the team approve the subsequent release steps.

[wcygan]

Understood. Thank you!

The addition of this version will likely be a boon for adoption of this MCP; I imagine people want to version-control their knowledge graph & share it with others.

[olaservo]

Hi @wcygan looks like a new package version is now on npm: https://www.npmjs.com/package/@modelcontextprotocol/server-memory?activeTab=versions

Side note, the automated publish process switched to calendar versioning.

[wcygan]

Thanks @olaservo! I'm able to get it working now, looks good:

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "env": {
        "MEMORY_FILE_PATH": "/Users/wcygan/path/to/memory.json"
      }
    }
  }
}