Soroban MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RPC_URL | No | Override the default RPC endpoint. | |
| LOG_LEVEL | No | Log level: debug, info, warn, error. | info |
| STELLAR_NETWORK | No | The Stellar network to use: testnet, futurenet, or mainnet (read-only ops only on mainnet). | testnet |
| SOROBAN_CLI_PATH | No | Path to the Soroban/Stellar CLI binary. | stellar |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_contractA | Builds a Soroban smart contract project using the Stellar CLI. Returns structured compiler diagnostics (file, line, error code, message) — not raw rustc text. |
| run_testsA | Runs the Soroban contract test suite with |
| get_account_infoA | Returns balance, sequence number, and signers for a Stellar account. Includes a testnet funding link if the account is not found. |
| get_contract_stateA | Reads and returns storage entries (persistent, instance, temporary) for a Soroban contract. Keys and values are decoded to human-readable strings where possible. |
| deploy_contractA | Deploys a compiled .wasm file to testnet or futurenet using the Stellar CLI. Returns the contract ID and transaction hash. Mainnet is intentionally not supported here. |
| invoke_contractA | Simulates a Soroban contract function call via RPC. Returns the function result AND simulated resource cost (CPU instructions, memory, min fee). For read-only calls no signing is needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Network Status | Current ledger height and health for a Stellar network |
| Contract ABI | Contract ABI/spec parsed from the on-chain WASM metadata |
| Contract Transaction History | Recent transaction history for a contract |
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: building, testing, account info, contract state, deployment, and invocation. There is no overlap in purpose, and the descriptions make it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern in snake_case (build_contract, run_tests, get_account_info, get_contract_state, deploy_contract, invoke_contract). This creates a predictable and uniform naming convention.
Six tools is a well-scoped count for a Soroban smart contract development server. Each tool covers a core step in the contract lifecycle without being redundant or overwhelming.
The toolset covers the essential workflow: build, test, deploy, invoke, inspect state, and manage account access. While additional tools could be added (e.g., listing contracts), the existing set is sufficient for common development tasks and has no obvious dead ends.