Quick Start
This is the shortest path to a working SLK proposal review flow.
MUTX ships as a single unified binary:
mutx— the terminal UI (default)mutx daemon— the headless background servicemutx web— the browser-based UImutx-link(also reachable asmutx link) — the MCP agent interface
1. Start the daemon
mutx daemon
This starts the headless service that holds wallet state and runs the authorization flow.
2. Start the TUI
mutx
On first run, create or import a wallet from the Wallets tab:
- Press
nto create a wallet, orito import one - Pick the chain — Solana for this example. The full list of supported chains is in the Wallet Management page.
- Pick the network —
devnetif you want to experiment safely,mainnetfor real funds - Enter a wallet name
- Choose how the wallet should be protected. Use Password unless you are working with a throwaway wallet.
- Press
rto display the receive address - Press
bto refresh balances (balances also refresh automatically in the background)
3. Connect an agent
Local stdio mode (default):
mutx link
HTTP mode:
mutx link serve --mode http --bind 0.0.0.0:8000
4. Configure your MCP client
Minimal local configuration:
{
"mcpServers": {
"mutx": {
"command": "mutx",
"args": ["link"]
}
}
}
If you run Link over HTTP, point your client to /mcp on the chosen host and port.
5. Approve the agent’s SLK proposal
The agent calls request_slk once at the start of the session:
- the proposal appears in the Proposals tab
- inspect capabilities, scopes, wallets, and expiry
- press
yto approve,eto narrow the draft before approving, ornto deny
Once approved, every subsequent agent call is authorized by the SLK —
no per-call prompt. Inspect the SLK in the SLKs tab, audit dispatches
in the Activity tab, and revoke at any time with r.
WalletConnect session proposals are handled from the DApps tab,
unless the agent’s SLK grants can_wc_connect for the matching dApp
scope — in that case the session is approved autonomously.
6. Verify Link is working
mutx link wallet list
If you see your wallets printed, the socket is healthy and any MCP client will be able to reach MUTX.
See the MCP Setup guide for detailed configuration, or Agent Integration for client-specific instructions.