Automated summary
An MCP server that connects coding agents to the IOTA network for wallet management with human-approved signing, Move contract build/test/publish, and on-chain queries over JSON-RPC and GraphQL.
Strengths
- 18 tools spanning wallet operations, Move CLI and on-chain queries in one MCP server
- Explicit human-in-the-loop signing flow with pending requests, approve/reject, and post-approval digest verification
- Build, test-with-coverage and unsigned publish transaction generation for Move packages
- No secrets held in the MCP process, plus built-in mainnet/testnet/devnet switching
Limitations
- Assumes a separate agent-wallet server is already installed and reachable for human approval
- Completed publishing depends entirely on manual approval, which blocks fully autonomous workflows
- On-chain tools are limited to read queries and ABI decompilation, with no historical indexing
Use it when an agent needs to prepare, test or publish Move contracts on IOTA and inspect on-chain state while keeping signing under human control.
Avoid it if you need end-to-end automation without human intervention or if you are working on a blockchain other than IOTA.
Security analysis
CautionThe skill is a legitimate MCP server integration with no destructive, exfiltration, or obfuscated instructions. However, it grants wallet-signing and arbitrary IOTA CLI capabilities, and the approval/rejection tools could undermine the intended human-in-the-loop control if exposed directly to an agent. This warrants caution rather than risky.
- •Exposes `iota_cli` to run any IOTA CLI command, which is broad and powerful even if legitimate.
- •Wallet signing flow relies on an external local agent-wallet server; `iota_wallet_approve` and `iota_wallet_reject` are listed as tools, so human-in-the-loop safety depends on how tool access is configured.
- •Global npm install from `iota-agent-mcp` without version pinning or integrity verification adds supply-chain risk.
Examples
Build the Move package in ./my_move_project and run the unit tests with a coverage summary.Fetch IOTA object 0xabc123 and tell me its owner, type, version and content.Generate an unsigned publish transaction for ./my_move_project with a 500000000 gas budget, submit it for wallet signing, then confirm the digest once it's approved.name: iota-agent-mcp description: "IOTA blockchain MCP server providing wallet management with human-in-the-loop signing, Move smart contract build/test/publish, and on-chain queries via JSON-RPC and GraphQL. Use when interacting with IOTA network from AI coding agents, managing IOTA wallets, building or publishing Move packages, querying on-chain objects or transactions, or checking epoch and network statistics."
IOTA Agent MCP
MCP server that connects AI coding agents to the IOTA blockchain. Provides 18 tools across wallet operations, Move smart contract development, and on-chain data queries — all via stdio transport with no secrets in the MCP process.
Workflow
- Configure the MCP server in your agent's settings (Claude Code, Cursor, VS Code Copilot)
- Query on-chain data — fetch objects, transactions, coins, epoch info, or decompile modules
- Develop Move contracts — build, test with coverage, generate unsigned publish transactions
- Sign and publish — generate unsigned transaction, submit via
iota_wallet_sign_execute, checkiota_wallet_pendingfor approval status, verify on-chain withiota_transaction
Signing flow (human-in-the-loop)
Wallet operations that modify state require human approval:
- Call
iota_wallet_sign_executewith base64-encoded transaction bytes — creates a pending request - Call
iota_wallet_pendingto confirm the request was queued - The human approves (
iota_wallet_approve) or rejects (iota_wallet_reject) via the agent-wallet server - On approval, verify the transaction landed on-chain: call
iota_transactionwith the returned digest - If rejected, inform the user and do not retry without explicit instruction
Tools
Wallet (8 tools)
iota_wallet_address— Get the active wallet addressiota_wallet_balance— Check IOTA balance for the active walletiota_wallet_accounts— List all derived wallet accountsiota_wallet_sign_execute— Sign and execute a transaction (requires human approval via agent-wallet server)iota_wallet_pending— List pending signing requests awaiting approvaliota_wallet_approve— Approve a pending signing request by IDiota_wallet_reject— Reject a pending signing request by IDiota_wallet_switch_network— Switch between mainnet, testnet, and devnet
Move CLI (4 tools)
iota_cli— Run any IOTA CLI command (e.g.client gas,move new my_project)iota_move_build— Compile a Move package and report build resultsiota_move_test_coverage— Run Move tests with coverage analysis and summaryiota_move_publish_unsigned— Generate unsigned publish transaction for agent-wallet signing
On-Chain Query (6 tools)
iota_object— Fetch object data by ID (owner, type, version, content)iota_objects_by_owner— List objects owned by an addressiota_transaction— Fetch transaction details by digest (input, effects, events)iota_coins— Get coin objects for gas estimation and token queriesiota_epoch_info— Current epoch, checkpoint, and network statistics via GraphQLiota_decompile— Retrieve and decompile a deployed Move module's ABI
Examples
Build and test a Move package:
iota_move_build(path: "./my_move_project")
→ "BUILDING my_move_project ... Build Successful"
iota_move_test_coverage(path: "./my_move_project")
→ "## Test Results\nRunning Move unit tests ... 5 tests passed\n\n## Coverage Summary\n85.7% coverage"
Query an on-chain object:
iota_object(object_id: "0xabc123...")
→ { "owner": "0xdef456...", "type": "0x2::coin::Coin<0x2::iota::IOTA>", "version": 42, "content": {...} }
Publish a Move package with wallet signing:
iota_move_publish_unsigned(path: "./my_move_project", gas_budget: "500000000")
→ "AAACAQBk..." (base64 tx bytes)
iota_wallet_sign_execute(tx_bytes: "AAACAQBk...")
→ "Request queued (id: req-1). Awaiting human approval."
Configuration
Set environment variables to override defaults:
IOTA_WALLET_SERVER— Agent wallet server URL (default:http://localhost:3847)IOTA_RPC_URL— IOTA JSON-RPC endpoint (default: mainnet)IOTA_GRAPHQL_URL— IOTA GraphQL indexer (default: mainnet)
Setup
npm install -g iota-agent-mcp
// Claude Code: ~/.claude/settings.json
{
"mcpServers": {
"iota": { "command": "iota-agent-mcp" }
}
}
// Cursor / VS Code: .cursor/mcp.json or .vscode/mcp.json
{
"servers": {
"iota": { "command": "npx", "args": ["iota-agent-mcp"] }
}
}
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/iota-agent-mcp-mrwakfei/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/iota-agent-mcp-mrwakfei' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/iota-agent-mcp-mrwakfei/download' --output '.skill-downloads/iota-agent-mcp-mrwakfei/SKILL.md.part' && mv '.skill-downloads/iota-agent-mcp-mrwakfei/SKILL.md.part' '.skill-downloads/iota-agent-mcp-mrwakfei/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Setup
npm install -g iota-agent-mcp
// Claude Code: ~/.claude/settings.json
{
"mcpServers": {
"iota": { "command": "iota-agent-mcp" }
}
}
// Cursor / VS Code: .cursor/mcp.json or .vscode/mcp.json
{
"servers": {
"iota": { "command": "npx", "args": ["iota-agent-mcp"] }
}
}
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/iota-agent-mcp-mrwakfei/SKILL.md' && test -s '.skill-downloads/iota-agent-mcp-mrwakfei/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/iota-agent-mcp' && cp -R '.skill-downloads/iota-agent-mcp-mrwakfei' '.claude/skills/iota-agent-mcp'Cursor
test -f '.skill-downloads/iota-agent-mcp-mrwakfei/SKILL.md' && test -s '.skill-downloads/iota-agent-mcp-mrwakfei/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/iota-agent-mcp' && cp -R '.skill-downloads/iota-agent-mcp-mrwakfei' '.cursor/skills/iota-agent-mcp'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/iota-agent-mcp-mrwakfei'openskills read 'iota-agent-mcp-mrwakfei'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/iota-agent-mcp-mrwakfei/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.