StellarMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port. | 3000 |
| MCP_TRANSPORT | No | Transport mode: stdio (default) or http-sse. | stdio |
| STELLAR_NETWORK | No | Stellar network: testnet (default) or mainnet. | testnet |
| STELLAR_RPC_URL | No | Soroban RPC URL (same rules as Horizon). | |
| STELLAR_AUTO_SIGN | No | Legacy auto-sign flag if policy unset. | |
| STELLAR_SEP38_URL | No | Anchor SEP-38 endpoint for quotes. | |
| STELLAR_SECRET_KEY | No | Signing key; omit for read-only / unsigned-XDR-only operation. | |
| STELLAR_HORIZON_URL | No | Horizon base URL (https; host must be default-allowed or listed in STELLAR_ALLOWED_HOSTS). | |
| STELLAR_USDC_ISSUER | No | USDC issuer for valuation in guarded signing (default is network USDC). | |
| STELLAR_ALLOWED_HOSTS | No | Comma-separated extra hostnames allowed for the three URL vars above. | |
| STELLAR_AUTO_SIGN_LIMIT | No | Legacy / used with guarded (must be > 0). | |
| STELLAR_AUTO_SIGN_POLICY | No | Auto-sign policy: safe, guarded, or expert. | |
| STELLAR_REQUEST_TIMEOUT_MS | No | Upstream request timeout (max 30000). | |
| STELLAR_TRUSTED_ANCHOR_DOMAINS | No | Comma-separated domains allowed for anchor/TOML and SEP flows. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stellar_get_account_historyA | Fetch the paginated transaction history for a Stellar account. |
| stellar_get_accountA | Fetch account details including balances, signers, flags, and calculated minimum balance. |
| stellar_fund_accountA | Fund a Stellar testnet account with 10,000 testnet XLM using Friendbot. |
| stellar_set_optionsA | Modify account options (e.g., adding a signer, setting weights/thresholds, or updating flags). Returns unsigned XDR by default unless policy allows. |
| stellar_submit_paymentB | Submit a Stellar payment transaction and return the transaction hash. |
| stellar_submit_fee_bump_transactionA | Sponsor the fees for an existing transaction using a Fee Bump Transaction. Submits to the network. |
| stellar_create_trustlineA | Create a trustline for a non-native Stellar asset and return transaction hash. |
| stellar_deposit_liquidityB | Deposit liquidity into a classic Stellar AMM liquidity pool. |
| stellar_withdraw_liquidityA | Withdraw liquidity from a classic Stellar AMM liquidity pool. |
| stellar_get_fee_statsA | Fetch current fee statistics and return recommended fee for reliable inclusion. |
| stellar_get_ledger_metaA | Fetch closed ledger header metadata from Horizon (primary) with Soroban RPC getLedgers fallback. Responses are bounded with truncation metadata; results may be cached on disk with TTL. |
| stellar_get_transaction_metaA | Fetch transaction result / fee metadata XDR from Horizon (primary) with Soroban RPC getTransaction fallback. Payloads are bounded with truncation metadata; optional operation_index slices decoded TransactionMeta when not truncated. |
| stellar_xdr_typesA | List supported Stellar XDR type names for encode/decode/schema (from the bundled XDR JSON engine). |
| stellar_xdr_json_schemaA | Return Draft-7 JSON Schema for a Stellar XDR type (use with stellar_xdr_encode). |
| stellar_xdr_guessA | Given base64 XDR, return which XDR types decode successfully (single value only; not streams). |
| stellar_xdr_encodeA | Encode JSON into base64 XDR for a named type (roundtrip with stellar_xdr_json_schema + decode tools). |
| stellar_decode_xdrA | Decode a base64 encoded Stellar transaction XDR into a readable JSON format showing operations and parameters. |
| stellar_sep10_authB | Perform SEP-10 challenge signing flow and return JWT token. |
| stellar_sep6_transferB | Initiate a SEP-6 programmatic deposit or withdrawal. |
| stellar_sep12_customerA | GET or PUT customer KYC data to an Anchor's SEP-12 KYC_SERVER. |
| stellar_sep31_remittanceC | Initiate a SEP-31 cross-border remittance payment. |
| stellar_sep24_interactiveA | Initiate a SEP-24 interactive deposit or withdrawal. Returns the interactive URL to present to the user. |
| stellar_get_anchor_tomlA | Fetch and parse the stellar.toml file for a given anchor domain to discover SEP support (SEP-10, SEP-24, etc). |
| stellar_get_sep38_quoteA | Request a SEP-38 indicative quote and return rate metadata. |
| stellar_soroban_simulateA | Simulate a Soroban smart contract invocation to get footprint, events, and results. Does NOT submit transaction. |
| stellar_soroban_invokeB | Invoke a Soroban smart contract. Simulates the transaction, extracts the footprint, and submits it to the network if policy allows. |
| stellar_soroban_get_eventsB | Fetch historical events emitted by a Soroban smart contract. |
| stellar_soroban_deployA | Upload WASM and deploy a Soroban smart contract instance. Returns wasmHash, contractId, and transaction hashes. |
| stellar_soroban_read_stateA | Read the state of a specific contract data entry directly from the ledger without simulating a transaction. |
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 29 tools
Tools are largely distinct but several fetch/metadata tools (e.g., stellar_get_ledger_meta, stellar_get_transaction_meta) could cause minor confusion for an agent. However, descriptions clearly differentiate their purposes.
All tools follow the stellar_verb_noun pattern consistently, using clear verbs like create, get, submit, decode. No mixing of conventions.
29 tools is high but justified by the broad domain coverage (accounts, transactions, SEPs, Soroban, XDR, liquidity). Each tool serves a specific function without redundancy.
Covers most major Stellar operations including accounts, trustlines, payments, liquidity pools, Soroban smart contracts, and multiple SEPs. Missing path payments and account merging, but still comprehensive.