@mysten-incubation/memwal-mcp is uninstallable: pins non-existent @modelcontextprotocol/sdk@1.29.0

Open
#445 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
node.js, typescript
Domain
build-system, release, testing-qa

Research direction

Start by inspecting the published package metadata for @mysten-incubation/memwal-mcp and the repository’s CI or release configuration. Run npx -y @mysten-incubation/memwal-mcp --help with a clean cache, then verify that the released package installs and starts without the ETARGET error; the smoke test should fail if the dependency metadata is invalid.

Written by the indexing model from the issue text.

Description

Following the documented Claude Code MCP setup (claude mcp add --scope user memwal -- npx -y @mysten-incubation/memwal-mcp), the server fails to start; /mcp reports Failed to reconnect to memwal: -32000. Running the documented login directly reproduces the root cause:

$ npx -y @mysten-incubation/memwal-mcp login --prod
npm error code ETARGET
npm error notarget No matching version found for @modelcontextprotocol/sdk@1.29.0.

The published @mysten-incubation/memwal-mcp package depends on @modelcontextprotocol/sdk@1.29.0, which does not exist on the npm registry, so npx cannot install it and the MCP server never runs. This makes the MCP path (the primary integration in the docs) unusable out of the box on a clean machine.

Fix. Loosen the dependency to a published range (an @modelcontextprotocol/sdk version that actually exists) and republish; add a CI smoke test that runs npx @mysten-incubation/memwal-mcp --help on a clean cache so a bad pin fails the release.

Impact / workaround. Until fixed, agents cannot use the MCP tools at all; we fell back to the SDK via a small CLI (@mysten-incubation/memwal itself installs fine). Environment: macOS, Node 25, npm 11, pnpm 10.

Dominant language
TypeScript
Stars
107
Forks
37
Avg merge
3d 12h
Merged PRs (30d)
86

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MystenLabs/MemWal

All issues in MystenLabs/MemWal

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.