Reading a balance is harmless; sending is not, and the same configured key does both. The private key sits in a local `.env` and any transfer the model is asked to make is signed with it, so use a wallet funded for exactly this purpose, and try the airdrop path first.
A small backend that gives an assistant three Solana actions: read the SOL balance of a public key, transfer SOL from the configured wallet to a recipient, and request an airdrop to a public key.
- The SOL balance of any public key, read on request
- A transfer of SOL from the wallet you configured to a recipient you name
- An airdrop requested against a public key, for working on a test cluster
- A stdio server the client launches directly, with node and the built entry point named in the config
A Solana wallet, with its private key placed in a `.env` file in the project root as `PRIVATE_KEY`. Node, and a Claude Desktop entry giving the path to node and the path to the server's entry file. That private key is the whole authority the server has — it signs transfers with it.
One command plus a key — npx -y backend, then supply credentials