iota-agent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IOTA_RPC_URL | No | IOTA JSON-RPC endpoint | https://api.mainnet.iota.cafe |
| IOTA_GRAPHQL_URL | No | IOTA GraphQL indexer | https://graphql.mainnet.iota.cafe |
| IOTA_WALLET_SERVER | No | Agent wallet server URL | http://localhost:3847 |
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 |
|---|---|
| iota_wallet_addressB | Get the active wallet address |
| iota_wallet_balanceB | Check IOTA balance for the active wallet |
| iota_wallet_accountsB | List all derived wallet accounts |
| iota_wallet_sign_executeA | Sign and execute a transaction via the agent wallet (human-in-the-loop approval required) |
| iota_wallet_pendingA | List pending signing requests awaiting approval |
| iota_wallet_approveC | Approve a pending signing request |
| iota_wallet_rejectC | Reject a pending signing request |
| iota_wallet_switch_networkC | Switch between mainnet, testnet, and devnet |
| iota_cliB | Run an arbitrary IOTA CLI command. Use for operations not covered by other tools. |
| iota_move_buildC | Build a Move package and report compilation results |
| iota_move_test_coverageB | Run Move tests with coverage analysis. Returns test results and coverage summary. |
| iota_move_publish_unsignedB | Generate an unsigned publish transaction for a Move package (for agent wallet signing) |
| iota_objectB | Fetch on-chain object data by ID. Returns owner, type, version, and content. |
| iota_objects_by_ownerC | List objects owned by an address |
| iota_transactionB | Fetch transaction details by digest |
| iota_coinsC | Get coin objects for an address (useful for gas estimation and token queries) |
| iota_epoch_infoB | Get current epoch, checkpoint, and network statistics via GraphQL |
| iota_decompileB | Retrieve and decompile a deployed Move module. Returns the module's ABI (structs, functions, type params). |
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 18 tools
Most tools have distinct purposes with clear boundaries, such as iota_object for fetching object data versus iota_objects_by_owner for listing owner objects. However, there is some overlap between iota_wallet_approve and iota_wallet_reject, which both handle pending signing requests but with opposite actions, which could cause minor confusion in selection. The iota_cli tool is a catch-all for uncovered operations, which might overlap with other tools if not used carefully.
The tool names follow a highly consistent pattern with a clear prefix 'iota_' and descriptive verb_noun combinations, such as iota_move_build, iota_wallet_balance, and iota_epoch_info. All tools use snake_case uniformly, and the naming conventions are predictable across the set, making it easy to understand the purpose and domain of each tool.
With 18 tools, the count is slightly high but reasonable for a comprehensive IOTA agent server covering CLI operations, Move development, object queries, and wallet management. It provides a broad scope without being overwhelming, though it might benefit from slight consolidation in areas like wallet request handling to reduce complexity.
The tool set offers complete coverage for the IOTA agent domain, including CLI execution, Move package building and publishing, on-chain data queries (objects, transactions, epochs), and full wallet lifecycle management (accounts, balances, signing, network switching). There are no obvious gaps; agents can perform all essential operations from development to deployment and interaction with the blockchain.