stellarpilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stellar_contract_deployC | Deploy a Soroban smart contract to Stellar network |
| stellar_contract_invokeB | Invoke a function on a deployed Soroban contract |
| stellar_contract_buildC | Build a Soroban contract from Rust source code |
| stellar_contract_initC | Initialize a new Soroban contract project |
| stellar_contract_optimizeC | Optimize WASM files for deployment |
| stellar_contract_aliasC | Manage contract aliases for easier reference |
| stellar_contract_asset_deployB | Deploy a Stellar Asset Contract for wrapping classic assets |
| stellar_contract_bindingsC | Generate client bindings for a contract in various languages |
| stellar_contract_infoC | Get information about a contract (interface, metadata, etc.) |
| stellar_contract_extendC | Extend the time-to-live of contract data entries |
| stellar_contract_restoreC | Restore evicted contract data entries |
| stellar_contract_readD | Read contract data entries |
| stellar_contract_fetchC | Fetch a contract's WASM binary from the network |
| stellar_contract_uploadB | Upload a WASM file to the ledger without creating a contract instance |
| stellar_contract_idC | Generate contract IDs for assets or WASM contracts |
| stellar_tx_paymentC | Create and send a payment transaction |
| stellar_tx_create_accountC | Create and fund a new Stellar account |
| stellar_tx_change_trustC | Create, update, or delete a trustline for an asset |
| stellar_tx_account_mergeC | Merge account balance into another account and remove source |
| stellar_tx_manage_dataC | Set, modify, or delete account data entries |
| stellar_tx_set_optionsC | Set account options like flags, signers, and home domain |
| stellar_tx_manage_sell_offerC | Create, update, or delete a sell offer on the DEX |
| stellar_tx_manage_buy_offerC | Create, update, or delete a buy offer on the DEX |
| stellar_tx_signC | Sign a transaction envelope |
| stellar_tx_sendC | Send a signed transaction to the network |
| stellar_tx_simulateC | Simulate a transaction to predict results and costs |
| stellar_tx_hashC | Calculate the hash of a transaction envelope |
| stellar_tx_decodeB | Decode transaction XDR to human-readable JSON |
| stellar_tx_fetchB | Fetch a transaction from the network by hash |
| stellar_tx_update_sequenceC | Update the sequence number on a transaction |
| stellar_tx_path_paymentC | Send a payment using path finding for cross-asset transfers |
| stellar_keys_generateC | Generate a new identity using a 24-word seed phrase |
| stellar_keys_addC | Add a new identity (keypair, ledger, OS specific secure store) |
| stellar_keys_public_keyC | Given an identity return its address (public key) |
| stellar_keys_fundB | Fund an identity on a test network |
| stellar_keys_listC | List identities |
| stellar_keys_removeC | Remove an identity |
| stellar_keys_secretC | Output an identity's secret key |
| stellar_keys_useC | Set the default identity for all commands |
| stellar_network_addC | Add a new network configuration |
| stellar_network_removeC | Remove a network configuration |
| stellar_network_listC | List configured networks |
| stellar_network_useB | Set the default network for all commands |
| stellar_network_healthC | Check the health of the configured RPC |
| stellar_network_infoC | Get detailed information about the network |
| stellar_network_settingsC | Fetch the network's config settings |
| stellar_events_watchC | Watch the network for contract events |
| stellar_ledger_latestC | Get the latest ledger sequence and information from the network |
| stellar_ledger_fetchB | Fetch specific ledger information by sequence number |
| stellar_fee_statsB | Fetch network fee statistics for transaction planning and cost estimation |
| stellar_snapshot_createC | Create a ledger snapshot using a history archive |
| stellar_container_startB | Start a container running a Stellar node, RPC, API, and friendbot (faucet) |
| stellar_container_stopB | Stop a network container started with stellar container start |
| stellar_container_logsB | Get logs from a running network container |
| stellar_xdr_decodeB | Decode XDR data to human-readable format |
| stellar_xdr_encodeC | Encode JSON data to XDR format |
| stellar_xdr_guessC | Guess the XDR type of given data |
| stellar_xdr_types_listC | List all available XDR types |
| stellar_xdr_types_schemaB | Get JSON schema for a specific XDR type |
| stellar_xdr_compareC | Compare two XDR values |
| stellar_xdr_generate_defaultC | Generate default XDR values for a type |
| stellar_config_dirB | Show the global configuration directory location and contents |
| stellar_config_migrateC | Migrate the local configuration to the global directory |
| stellar_envB | Print environment variables in .env format or get specific variable value |
| stellar_cache_cleanB | Delete the cache, removing all cached data including transaction history and contract specs |
| stellar_cache_pathA | Show the location of the cache directory |
| stellar_cache_actionlog_listC | List cached actions like transactions and simulations (experimental feature) |
| stellar_cache_actionlog_readC | Read cached action details by ID (experimental feature) |
| stellar_doctorC | Diagnose and troubleshoot CLI and network issues, checking for common problems |
| stellar_completionC | Print shell completion code for the specified shell |
| stellar_versionB | Print version information for the Stellar CLI |
| stellar_plugin_searchB | Search for CLI plugins using GitHub |
| stellar_plugin_listB | List installed plugins |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 73 tools
Most tools target distinct resource+action pairs (e.g., tx_payment vs tx_path_payment, contract_deploy vs contract_upload). A few boundaries are subtle, such as tx_send vs tx_payment and contract_read vs contract_fetch vs contract_info, but descriptions generally clarify them.
All tools use snake_case with a consistent stellar_ prefix and domain_action hierarchy. Minor noun-vs-verb endings exist, but the pattern is highly predictable with no mixed conventions.
73 tools is far beyond the typical 3-15 range and creates severe cognitive overload for an agent. While the underlying CLI has many commands, exposing all as separate tools is an extreme mismatch for a coherent MCP surface.
The surface covers identities, networks, transactions, contracts, XDR, cache, config, plugins, containers, ledgers, events, fees, and snapshots. This is comprehensive for the Stellar CLI domain with no obvious critical gaps.