The read tools default to your own address when none is passed, which is convenient and also a standing reminder that the server always knows whose keys it holds. The DEX path is the one place the descriptions enforce an order: dex-find-routes, dex-simulate-swap and dex-swap each state that pools must be checked with dex-get-pools first, and the simulate step exists so the expected outcome is known before slippage is committed. query-network is the intentional escape hatch, and it is honest about the cost of that — it will execute any gRPC-gateway path, and tells you to read the openapi specification at openapi://{networkName} before calling it, which means the tool list is a floor on what this can reach rather than a ceiling.
A MANTRA chain client covering the Cosmos side — bank, staking, IBC, CosmWasm and generic gRPC-gateway queries — and the EVM side — contract read, write and deploy, plus ERC20, ERC721 and ERC1155 transfers — from a single mnemonic.
- Balances across the token standards: get-balance and get_evm_balance read native holdings, get_token_balance reads an ERC20, get_nft_balance returns the count of ERC721 tokens an address holds from a collection, and get_erc1155_balance returns the quantity held of one ERC1155 token ID.
- Staking from discovery to payout: get-validators lists validators, delegate and undelegate move stake against an operatorAddress with a denom and memo, get-delegations reads current positions, and get-available-rewards then claim-rewards read and collect what is owed.
- Swaps with a rehearsal step built in: dex-get-pools lists the liquidity pools, dex-find-routes finds routes between an input and output denom, dex-simulate-swap returns the expected outcome without executing, and dex-swap executes under a slippage bound.
- Contract work on the CosmWasm side and the EVM side: cosmwasm-contract-query runs a read-only function and cosmwasm-contract-execute changes state with attached funds; read_evm_contract, write_evm_contract and deploy_evm_contract take an abi and args with maxFeePerGas and maxPriorityFeePerGas ceilings; is_contract distinguishes a contract from an externally owned account.
- Transfers on the EVM side: transfer_om moves native OM, transfer_erc20 and transfer_token move ERC20 balances, transfer_nft moves an ERC721 token, transfer_erc1155 moves a quantity of a multi-token ID, and approve_token_spending authorises a spenderAddress such as a DeFi protocol.
- Chain reads and a deliberate escape hatch: get-account-info returns account state, get-block-info reads from CometBFT RPC and get-block-info-evm from EVM RPC, get_transaction and get_transaction_receipt resolve a txHash, estimate_gas prices a transaction before you commit to it, and query-network executes any gRPC-gateway path the dedicated tools do not cover.
- Cross-chain movement: ibc-transfer sends tokens over IBC with sourcePort, sourceChannel, an ibcMemo and a timeoutHeight or timeoutTimestamp.
- Token and collection metadata: get_erc20_token_info returns name, symbol, decimals and total supply, get_nft_info returns collection name, symbol, token URI and current owner, get_erc1155_token_uri returns the metadata URI, and check_nft_ownership confirms whether an address holds a given token ID.
- sign-and-broadcast signs and broadcasts a generic cosmos-sdk transaction from the messages you supply, and get_address_from_mnemonic derives the EVM address the server will sign as.
A mnemonic phrase for the account that will sign, supplied as MNEMONIC — get_address_from_mnemonic derives the EVM address from it. CUSTOM_NETWORKS is also read from the environment, and every tool takes a networkName.
One command — npx -y mantrachain-mcp@latest