Move decompiler
decompile_module is the only tool that needs an external binary, and every
code question can be answered without it:
disassemble_modulereturns Move bytecode assembly via the GraphQL endpoint; itsfunction_nameargument returns one function.get_move_functionreturns a function’s signature and visibility.diff_package_upgradediffs two versions of a package, function by function.analyze_packagesummarizes a package’s API and runs a heuristic risk scan.
Use the decompiler when you want higher-level, source-like Move output instead of bytecode.
Build the binary
Section titled “Build the binary”Revela’s move-decompiler is a Rust binary. It is not bundled with the npm
package. Build it and set SUI_DECOMPILER_PATH to its absolute path. You need
a Rust toolchain (rustup.rs).
git clone --depth 1 https://github.com/verichains/revela_sui.gitcd revela_sui/external-crates/movecargo build --release --bin move-decompiler# binary lands at target/release/move-decompilerIf you already cloned this repo, npm run build:decompiler does the same
clone and build and copies the result to bin/move-decompiler.
Point the server at it
Section titled “Point the server at it”Add its absolute path to your client config:
{ "mcpServers": { "sui": { "command": "npx", "args": ["-y", "sui-analytics-mcp"], "env": { "SUI_DECOMPILER_PATH": "/absolute/path/to/revela_sui/external-crates/move/target/release/move-decompiler" } } }}Without SUI_DECOMPILER_PATH the server falls back to looking for
move-decompiler on PATH. Prefer the absolute path: desktop clients often
launch servers with a minimal environment that doesn’t include your shell’s
PATH, so a binary you can run in a terminal may still be invisible to the
server.
When the binary is missing
Section titled “When the binary is missing”If it’s found in neither place, or SUI_DECOMPILER_PATH is set to an empty
string, decompile_module returns an error naming the tools that read bytecode
without it, its module listing reports decompiler_available: false, and
every other tool is unaffected.