MCP.so
ログイン

IOTA MCP Server

@Danielmark001

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

Danielmark001

IOTA MCP Server について

Built for IOTA Moveathon Hackathon

IOTA MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "iota_evm_mcp_server": {
      "command": "bun",
      "args": [
        "start"
      ]
    }
  }
}

IOTA MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is IOTA MCP Server?

IOTA MCP Server is a Model Context Protocol (MCP) server that provides blockchain services for IOTA, Shimmer, and 30+ EVM-compatible networks. It enables AI agents to read blockchain state, interact with smart contracts, transfer tokens, and access IOTA-specific features like staking and network monitoring through a unified interface.

How to use IOTA MCP Server?

Clone the repository, install dependencies with Bun (recommended) or npm, configure the .env file with your IOTA JWT token, node URL, and mnemonic for transactions, then start the server with bun start (stdio) or bun start:http (HTTP). Docker deployment is also available.

Key features of IOTA MCP Server

  • Multi-chain support for IOTA, Shimmer, and 30+ EVM networks
  • IOTA-specific services: staking, gas estimation, network status
  • Token operations: ERC20, ERC721, ERC1155 transfer and metadata
  • Smart contract deployment and security analysis on IOTA
  • Cross-chain arbitrage monitoring between IOTA and other networks
  • ENS name resolution for all address parameters

Use cases of IOTA MCP Server

  • AI agents querying IOTA network status, gas prices, and block data
  • Automated token transfers and smart contract interactions across chains
  • Monitoring and executing cross-chain arbitrage opportunities
  • Deploying and analyzing Solidity smart contracts on IOTA networks

よくある質問

1

What dependencies are required to run IOTA MCP Server?

Bun 1.0.0+ or Node.js 18.0.0+ is required. A `.env` file with `IOTA_JWT_TOKEN`, `IOTA_NODE_URL`, and optionally `IOTA_MNEMONIC` (for sending transactions) must be configured.

2

What transport protocols does IOTA MCP Server support?

The server supports both stdio (for embedding in CLI tools) and HTTP (for web applications) transports.

3

Where does blockchain data come from?

Data is fetched directly from the blockchain via user-configured node URLs (e.g., `IOTA_NODE_URL`). The server does not host its own node; it relies on external RPC endpoints.

4

How are transactions authenticated?

Transaction signing uses a private key derived from the mnemonic provided in the `.env` file. No API keys are required for signing; the JWT token is used for node access if needed.

5

Can IOTA MCP Server be used with non-IOTA EVM chains?

Yes, it supports 30+ EVM networks including Ethereum, Optimism, Arbitrum, Base, Polygon, and many others, all through the same MCP interface.

コメント

「その他」の他のコンテンツ