ASK ABOUT YOUR WALLET
Know what is available.
“Show my balances and the last ten payments.”
Give your assistant account and payment history to work with, without giving it spending access.
BuildAtto MCP
A wallet for your agent.
An allowance from you.
Connect your AI assistant to Atto with the Model Context Protocol. Start with balances and payment history. When you want it to pay, approve access and spending limits in your own terminal.
Run in your terminal
npx --yes @attocash/mcp@latest setupChoose your wallet and access, then add the generated configuration to your MCP client. Spending needs your local approval.
Beta · Node.js 24.15.0+ · An MCP client with local stdio support · Your OS password store. Check compatibility →
Package on npm ↗ASSISTANT REQUEST
Send 0.0001 ATTO to my chosen recipient.
- Start read-onlyBalances and history. No spending access.
- You approve in your terminalChoose the accounts and spending limits.
- The agent pays within those limitsIt cannot approve its own allowance.
ILLUSTRATIVE PAYMENT0.0001 ATTO
PER-PAYMENT CAP0.01 ATTO
Within the locally approved allowance
A useful assistant.
With wallet context.
You do not need to enable payments to get started. The same connection can read the wallet, follow events, and later make approved payments.
FOLLOW INCOMING PAYMENTS
Watch for what arrives.
“Watch this address for incoming payments.”
Read-only watches report payment events. Receiving the funds into the account is a separate operation that needs spending access.
ALLOW SMALL PAYMENTS
Pay an exact amount.
“Send 0.0001 ATTO to my saved recipient.”
After your local approval, the agent can pay people and services that accept ATTO, within the allowed accounts and amount limits. Atto charges no protocol transaction fee.
Choose the access.
Keep the approval.
A proposed allowance grants nothing. You review and approve it locally before the agent can spend.
Decide which funds.
Choose the source accounts the agent may use. A dedicated MCP wallet keeps its funds separate from your other wallet.
Set the allowance.
Approve a per-payment cap and a rolling spending cap. Ask the assistant to show the policy and remaining allowance at any time.
Confirm it yourself.
Review the wallet, network, accounts, and proposed limits in your terminal. No MCP tool can approve its own proposal.
These limits constrain the wallet tools, not arbitrary programs running as your OS user. Unrestricted shell access is a separate permission. Understand the approval boundary →
Your wallet setup.
Your choice.
Recovery stays out of the conversation. Create or import a wallet in your terminal and keep a private offline backup.
A dedicated agent wallet.
The default setup gives MCP its own wallet profile. Put only the funds you want available to the agent in that wallet, then choose its access.
Start with a separate wallet →The wallet you use in the CLI.
Choose your existing CLI wallet during setup. The same absolute profile directory shares funds, payment history, request IDs, and spending limits.
Connect an existing profile →Another way to build.
Choose the interface that fits the work. Each connects to the same feeless Atto network.
Build with Atto MCP.
Open the guide for setup, requirements, and implementation details.