MUTX exposes 17 MCP tools.
Most tools follow one of these patterns:
- approval in the TUI
- autonomous execution with a valid
SLK
- direct execution for low-risk session and token lifecycle operations
- Wallets are referenced by short ID or wallet name
slk is optional on tools that support autonomous execution
wallet_connect creates a pairing attempt, but the user still approves the WalletConnect proposal inside the TUI
| Tool | Description | Requires |
wallet_list | List available wallets | Approval or SLK |
wallet_details | Get wallet info (name, address, network) | Approval or SLK |
wallet_balance | Refresh and return SOL plus token balances | Approval or SLK |
wallet_receive | Get receive address | Approval or SLK |
wallet_send | Send SOL | Approval or SLK with can_send |
wallet_token_list | List SPL tokens | Approval or SLK |
wallet_token_send | Send SPL tokens | Approval or SLK with can_send_tokens |
wallet_swap | Swap tokens via Jupiter or Raydium | Approval or SLK with can_swap |
wallet_transactions | Transaction history with optional filters | Approval or SLK |
| Tool | Description | Requires |
address_book_list | List saved contacts | Approval or SLK |
address_book_add | Add a contact | Approval or SLK |
| Tool | Description | Requires |
wallet_connect | Submit a WalletConnect pairing URI | TUI approval of subsequent proposal |
wallet_sessions | List active sessions | None |
wallet_disconnect | Disconnect session | None |
| Tool | Description | Requires |
request_slk | Request a Short Lived Key | Approval (always) |
get_slk_info | Check SLK status | None |
slk_revoke | Revoke an active SLK | None |
Typical agent behavior looks like this:
- Call
wallet_list
- Choose a wallet ID or name
- Call read-only tools such as
wallet_balance or wallet_receive
- For sends or swaps, either wait for human approval or use a pre-approved
SLK