Install
Add it to your client
Section titled “Add it to your client”Add this to your MCP client config (Claude Code, Claude Desktop, Cursor, or anything else that speaks MCP over stdio):
{ "mcpServers": { "sui": { "command": "npx", "args": ["-y", "sui-analytics-mcp"] } }}No account, API key, or config file is required. The server reads public Sui endpoints and defaults to mainnet. Requires Node.js >= 22.13.
Load the forensics tools
Section titled “Load the forensics tools”For investigative work, start with the forensics tools loaded. Add an env
block beside command and args:
"env": { "SUI_TOOLS": "core,forensics" }Without it the server starts with the core profile, and the model turns on
other tools with enable_tools when a question needs them.
Tool profiles lists what each profile contains.
Optional extras
Section titled “Optional extras”- The forensics skill gives Claude the
investigation method. Copy it once into
~/.claude/skills. SUI_STORE_PATHturns on the local store. Labels and fan-out measurements then persist across sessions, and the case tools (save_finding,export_case) and watch tools (watch_addresses,poll_watch) need it. See Optional local store.decompile_moduleneeds an external binary. Every other tool works without it. See Move decompiler.
Running from source
Section titled “Running from source”For development, or to run a version you’ve modified:
git clone https://github.com/0xfreak0/sui-mcp.gitcd sui-mcpnpm installnpm run buildThen point your client at the build output instead of npx:
{ "mcpServers": { "sui": { "command": "node", "args": ["/absolute/path/to/sui-mcp/dist/index.js"] } }}See CONTRIBUTING.md for the development and release workflow.