stellar_create_accountLABSCO SUMMARY
Classic and Soroban operations behind one server.
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.
What it is
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.
What you get
- 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)
Requirements
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.
Setup effort
Add the configuration to your client
USE CASES
01
Standing up an account to test against
Create the account and fund it in two calls, so a throwaway identity for testing exists in seconds rather than through a faucet page.
02
Sending a payment
A payment in XLM or a custom asset goes out with the source account's secret key, and the balance read afterwards confirms it.
03
Issuing your own asset
Issuer and distributor keys plus a total supply create the asset, and a trustline with an explicit limit is what lets another account hold it.
04
Locking funds until a condition is met
A claimable balance is created with predicates — unconditional, or before a relative or absolute time — and claimed by the named account when the condition holds.
05
Getting a contract onto the network
Build and optimise from a contract path, then deploy, so the Soroban round trip happens without leaving the conversation.
06
Checking what an account has been doing
Transaction history for a public key comes back as structured records, which is what settles whether a payment actually landed.
12 tools
Listed in project docs. Your client may show a different list.
stellar_balancestellar_paymentstellar_transactionsstellar_create_assetstellar_change_truststellar_create_claimable_balancestellar_claim_claimable_balancestellar_fund_accountsoroban_build_and_optimizesoroban_deploysoroban_retrieve_contract_methodsBEFORE YOU INSTALL
What to know first
Tools you get
12 tools named in the project's documentation.
Requires
- Node.js
- STELLAR_SERVER_URL in your environment
INSTALLATION
Connect your client
MCP Clients
Claude Desktop — local build, Other MCP clients — local build
TERMINAL
git clone https://github.com/syronlabs/stellar-mcp
cd stellar-mcp
npm install
npm run buildJSON
{
"mcpServers": {
"stellar-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_STELLAR_MCP>/dist/index.js"
],
"env": {
"STELLAR_SERVER_URL": "https://horizon-testnet.stellar.org"
}
}
}
}Claude Desktop — npx, Other MCP clients — npx
JSON
{
"mcpServers": {
"stellar-mcp": {
"command": "npx",
"args": [
"-y",
"stellar-mcp"
],
"env": {
"STELLAR_SERVER_URL": "https://horizon-testnet.stellar.org"
}
}
}
}
