Repository navigation
nirium-mcp needs viem installed by hand (missing peer of mppx, not covered by peerDependenciesMeta) #118
Description
nirium-mcp fails to start unless viem is installed by hand, on a normal npm install (not just with --legacy-peer-deps).
Chain: nirium-mcp@0.6.1 depends on mppx@^0.6.31, whose package.json lists viem: ">=2.51.0" under peerDependencies. Its peerDependenciesMeta marks @modelcontextprotocol/sdk, elysia, express and hono as optional: true, but not viem, so npm treats it as a required peer and does not auto-install it even on npm 7+.
mppx really imports it: node_modules/mppx/dist/evm/client/Charge.js:1 has import { getAddress, parseUnits } from 'viem'. That is the EVM side of mppx (its Stellar side is what nirium-mcp calls), but loading the module still runs that import, so the process fails to start.
Repro:
cd packages/mcp && rm -rf node_modules package-lock.json
npm install
npm ls viem # empty
node dist/index.js # ERR_MODULE_NOT_FOUND: viem
Proposed fix (not done): add "viem": "^2.x" to dependencies in packages/mcp/package.json (or to nirium-mcp's own peerDependencies with viem listed and required), so a plain npm install works. Not fixing in this issue, scope kept separate from #117.
🤖 Generated with Claude Code
Activity
fix(mcp): add viem as direct dependency to resolve mppx peer import (n…
Ranjeet2063 commentedon Oct 12, 2026
Hello maintainers,
I reviewed this issue and would like to work on it.
Technical Implementation Outline:
Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!
fix(mcp): resolve JSON parse error and pin viem to ^2.55.19
ci(mcp): build nirium-mcp and clean-install check the npm tarball (#144)
Eras256 commentedon Oct 31, 2026
Thanks for the interest. No plan came in, so this one goes to @fernando-mendoza, who already built the CI for
packages/mcp(#144) and knows its clean-install check. If you want to help, reply on any open Niriumtober issue with a short plan: which files you would touch and how you would test it.Written with Claude Code.
Eras256 commentedon Oct 31, 2026
Correction to my comment above: this issue already has an open fix, #124 by @maxx-GENIUS (opened Oct 11, adds
viemas a direct dependency ofpackages/mcp). I missed it, so I assigned the issue by mistake and said that no plan had come in. That was wrong. I removed the assignment. @fernando-mendoza will review #124, and it can be merged from there once it checks out.Written with Claude Code.
Merge pull request #247 from nirium-protocol/fix/issue-118-mcp-viem-d…
fix(mcp): add viem as a direct dependency to resolve mppx's required …
Merge pull request #253 from nirium-protocol/release/mcp-0.6.4