Account setup, payments, custom assets and claimable balances cover the Classic side, and the same server builds, optimises and deploys Soroban contracts — so a test asset and the contract that uses it can be stood up in one sitting. Signing happens with keys you pass per call.
An MCP server for the Stellar network covering both Stellar Classic and Soroban. Accounts are created and funded, payments sent in XLM or a custom asset, trustlines changed, claimable balances created and claimed, and Soroban contracts built, optimised and deployed.
- A new Stellar account created (stellar_create_account) and funded (stellar_fund_account)
- An account's balance and its transaction history read (stellar_balance, stellar_transactions)
- Payments sent in native XLM or a custom asset (stellar_payment)
- A new asset issued from an issuing and a distributing account with a total supply (stellar_create_asset)
- Trustlines changed with an explicit limit (stellar_change_trust)
- Claimable balances created with claimant predicates — unconditional, before a relative or absolute time, or combined with NOT and AND — and claimed later (stellar_create_claimable_balance, stellar_claim_claimable_balance)
- Soroban contracts built and optimised from a contract path, then deployed (soroban_build_and_optimize, soroban_deploy)
The secret key for whichever account is signing — payments, asset issuance and trustline changes each take a secretKey argument, and asset creation takes both an issuerSecretKey and a distributorSecretKey. Soroban builds need the contract source on the same machine, addressed by contractPath.
Build from source — clone the repository and build it, then point your client at the binary