random-sui-account says not to use the result in production, and gen_mnemonic and gen_sui_accounts_by_mnemonic are marked as not recommended for production, so the accounts this server mints are scoped to disposable test identities by the person who wrote it. sui-transfer carries no such marking and deserves the same care: it takes recipients, amounts and network and nothing else, so the key that signs it is settled somewhere outside the call, and get_account_info_by_private_key accepts a raw privateKey as an argument.
A Sui chain toolkit for an agent session: faucet, sui-balance and sui-transfer act on a chosen network, while random-sui-account, gen_mnemonic, gen_sui_accounts_by_mnemonic and get_account_info_by_private_key handle keys and accounts.
- Funding and reading on any network the call names: faucet requests faucet funds for a list of addresses, and sui-balance returns balances for a list of addresses, each taking addresses and network.
- Payments in one call: sui-transfer sends SUI denominated in mist to a single address or to multiple addresses, taking recipients, amounts and network together.
- Account material generated on demand: random-sui-account creates accounts, gen_mnemonic generates mnemonics, and gen_sui_accounts_by_mnemonic derives accounts from a mnemonic you supply, each taking num for how many.
- Key inspection: get_account_info_by_private_key returns the account behind a privateKey you already hold.
Nothing — no account, no key.
One command — npx -y sui-mcp@latest