Say Ur Intent

Sui MCP

Sui MCP is a local-first Sui review and evidence layer for AI clients.

It turns a supported Sui action into an internal Review card where you inspect verified transaction facts and a PTB graph, then request approval in your own wallet. The backend builds or verifies the material, binds the reviewed account and digest, and uses WalletConnect for a sign-only request. It verifies the wallet's returned bytes and signature before one submission to Sui mainnet.

The AI and card never receive executable transaction bytes or signatures. Neither a review nor a wallet connection is standing transaction permission. Only an explicit user action and that transaction's wallet approval authorize the request. Lost replies are resolved by reading the known digest; they do not cause another signing or submission request. Request failures and unknown outcomes are separate from independently observed chain success/failure.

Account, Receipt and Chart cards provide read-only evidence independently of signing. Connect, Disconnect, Review and Settings also run inside the MCP host. Settings provides local data controls and explicit connection-service recovery. Human-readable review is not a guarantee of safety or of complete interpretation of every transaction detail; the raw PTB structure and addresses remain inspectable.

Users can ask ordinary questions:

• "Can I cover a 1000 dollar payment with my assets?"
• "How much are my USD-denominated assets together?"
• "What is the shortfall?"

Install

Install once with npm, then register the command in each AI app. You need Node.js 22 or newer, including npm. No Git checkout, build, custom installation folder, database server, Sui API key or endpoint setup is required for the normal path.

Already used an earlier release? Follow Updating an Existing Sui MCP Installation first. New installations can continue below.

This guide describes 0.8.2. First confirm it is published, then install that exact version:

npm view @zktx.io/sui-mcp@0.8.2 version

npm install -g @zktx.io/sui-mcp@0.8.2

The first command must return 0.8.2. If it is unavailable, follow the version availability guidance; do not drop the version and assume an older release matches this guide. Contributors can use the optional developer checkout.

Register the installed command in your app. This is the complete default configuration for Claude Desktop; Cursor's example is in the setup guide:

{

"mcpServers": { "sui-mcp": { "command": "sui-mcp" } } }

Codex uses TOML in ~/.codex/config.toml instead:

[mcp_servers.sui-mcp]

command = "sui-mcp"

Keep existing settings and other servers when adding these entries. Choose your app's walkthrough for the file location, registration and startup confirmation:

• Codex Desktop / CLI
• Claude Desktop
• Claude Code
• Cursor

After the app loads the registration, ask: "Use Sui MCP to show its package name, server name, version and network." Expect @zktx.io/sui-mcp, sui-mcp, 0.8.2 and mainnet. Then ask: "Use Sui MCP to list the available DeepBook pools on Sui mainnet." This first read needs no wallet or transaction. The first-use tutorial explains expected results, optional cards and wallet connection. If the app cannot find sui-mcp, use Command not found.

Using several apps at once

Codex, Claude Desktop and other local MCP apps can use the same installation at the same time on one computer under the same OS user. Register sui-mcp in each app. With defaults, they share the local backend, settings, records and one current wallet connection; no separate wallet pairing per app is needed. Changing that connection in one app affects the others, while completed cards keep their original results.

All apps must use the same package release and configuration. Updates require stopping all participating Sui MCP connections before restarting the shared backend. See Using Multiple Apps for sharing and update conditions. Interactive wallet, Review and Settings workflows require MCP Apps card support; ordinary reads can be used without it.

Package identity and local data

The npm package is @zktx.io/sui-mcp, and its repository is zktx-mcp/sui-mcp. Confirm the requested version is available before changing your client registration.

Use the full scoped package name: the unscoped sui-mcp package is a different project. Use sui-mcp as the default MCP registration name. A client-defined registration alias is a local label, not server identity or authorization. This is a pre-release: local data formats can change, and migration is not provided. Compatible updates preserve the current data directory. Incompatible databases and backups are rejected without conversion or automatic deletion. If startup reports a database format mismatch, follow the recovery instructions. You can retain the old files and use a new empty data directory, or explicitly choose to discard the old local data and settings and start fresh with defaults. Data from a different package is not discovered or imported. See the setup guide for installation and shared-server restart instructions.

Product Scope in Two Layers

• Implemented: Sui mainnet read evidence, non-signable external proposal review, and account-bound DeepBook swap review using protocol-agnostic adapters. Account, Receipt, Chart, Connect, Disconnect, Review and Settings cards use the same SQLite state and scoped permission model. The backend verifies stored material, ownership, quote/policy provenance, human-readable facts, simulation and PTB evidence before an explicit user request. WalletConnect carries bytes only between the backend and wallet; ordinary MCP responses expose facts, request status and observed execution results. Settings owns endpoint and read-address controls, local backup/import/reset, and explicit connection-service recovery. Settings operations require scoped user confirmation; ordinary MCP calls only create the card or read settings.
• Safety boundaries: no private-key custody, no MCP or AI autonomous execution, no forwarding of opaque external transaction bytes to a wallet, and no peg guarantee. The current product does not silently choose settlement tokens or routes. It does not provide fiat cash-out, P&L, tax or cost-basis support.

DeepBook provides the current scoped Sui conversion, price, and orderbook evidence through the shared protocol adapter contracts. Wallet and Sui balance reads describe held assets. They do not define the whole product.

Sui MCP does not custody funds, hold private keys, or autonomously trade on behalf of users. By current design, it does not rank venues, choose routes, make best-price recommendations, or silently choose settlement tokens for users.

Account-bound transaction building, signing requests and chain observation stay in the local backend. The Review card displays evidence and current permitted actions. Public review JSON, model-facing card data and backups never contain transaction bytes, signatures, SDK keys or signing permission. Reopening a card reads its stored state and never replays a financial request.

The current release flow is:

The user states an intent in natural language.

Sui MCP resolves the supported Sui mainnet evidence surface. The AI answers only from returned evidence and boundaries. Supported swap transaction material build is an account-bound review step, not part of the natural-language intent evidence answer.

The current release implements intent evidence for supported Sui mainnet reads. It can also create a read-only, non-signable local review session from a structured external payment or Sui action proposal. External proposal ingestion does not trust external transaction material or send anything for wallet signing.

For setup, see docs/MCP_SETUP.md. For the MCP API reference, see docs/MCP_TOOLS.md. For the AI-client answer playbook, see docs/AGENT_BEHAVIOR.md. For manual maintainer and developer utilities, see docs/UTILITY_INDEX.md.

User-question flows for USD-denominated coverage, balance totals, and shortfall answers live in docs/AGENT_BEHAVIOR.md. The response fields for those answers live in docs/MCP_TOOLS.md.

What Works Today

The current release can run as a local stdio MCP server and expose mainnet Sui DeFi evidence:

• wallet balances with verified display units;
• coin-balance classification;
• USD-denominated settlement asset groups derived from pinned DeepBook SDK registry metadata;
• intent evidence with response summaries for natural-language USD-denominated payment coverage, balance-total, and shortfall questions;
• DeepBook pools, tokens, mid price, orderbook context, raw quotes, display-amount quotes, and account inventory;
• user-requested bounded Sui transaction digest lookup, account activity scans, sent-function activity scans with known-wallet-only persistence, and stored normalized activity summaries;
• read-only external proposal review sessions that display proposed action, asset flow, recipient or target, freshness, missing evidence, user choices, unsupported claims, and non-signable reason;
• local Sui MCP review evidence and review-session status reads;
• account-bound DeepBook review with verified material, digest, ownership, policy, human-readable facts, simulation and PTB visualization, followed by explicit card selection and wallet approval through the backend;
• separately recorded request state and chain success/failure, shown in the Review card and available through ordinary reads;
• a Receipt card for server-read facts about any transaction digest, independent of signing.

It also includes:

• a local review server bound to 127.0.0.1;
• a local SQLite store for chain-qualified address history and review evidence;
• MCP output checks that reject forbidden executable, signing, token, seed, and key-material field names from responses.

Screens

Wallet connection. One WalletConnect connection provides one fixed address per approved chain. Settings chooses networks for the next connection, defaulting to Sui. The wallet may return a subset. Sui, Ethereum and Solana mainnet addresses are supported; financial actions remain Sui-only. A chain returning multiple addresses is unavailable for that connection; there is no account selector. Changing the wallet, address or network scope requires disconnecting and connecting again. Connect and Disconnect are separate purpose cards. Connect starts one pairing after authenticated View confirmation; Disconnect asks for one exact-target confirmation. Ended cards show a fixed address-free result and accept no further operation. Current addresses are available through read-only connection status. Connection is not transaction approval.

Review and result. The Review card prepares and renews verified conditions for its fixed Sui account and connection. Disconnecting and reconnecting cannot retarget an existing review. A replacement connection requires a new review. Users inspect the graph, amounts and costs, then choose Request wallet approval and approve in their wallet. Failed preparation has an explicit retry. Receipt and completed Review show the executed graph, observed asset changes and net network fee. Details supplements the same facts. Missing graph or receipt