Hedera MCP

What hedera-mcp MCP server does

The hedera-mcp MCP server gives MCP clients access to Hedera network operations without executing transactions itself. Its catalog includes 73 tools covering accounts, Hedera Token Service (HTS), Hedera Consensus Service (HCS), smart contracts, files, schedules, network information, and Mirror Node analytics.

Account tools can create, update, delete, inspect, and transfer HBAR between accounts. HTS tools cover fungible tokens and NFTs, including creation, minting, burning, transfers, associations, freezes, KYC, pauses, wipes, allowances, airdrops, rejection, updates, and deletion. HCS, EVM, file, and schedule tools provide corresponding transaction-building and read operations. The server also exposes four addressable resources for network exchange rates, network supply, account data, and token data.

How it works

The hedera-mcp MCP server separates data access from transaction execution. Reads are sent to a configured Hedera Mirror Node REST endpoint and do not require an account or credential. For writes, the server constructs and freezes a transaction, then returns base64-encoded unsigned bytes along with a human-readable summary. A wallet, Hedera SDK, or command-line tool must sign and submit those bytes separately.

Agents can inspect a generated transaction before signing it with the transaction-decoding tool. This supports workflows where an application or human reviews the transaction contents and controls the signing step. Smart-contract execution and query tools support ABI-aware calls when supplied with an ABI, function name, and arguments.

Setup and configuration

The package is published as @purplesquirrel/hedera-mcp and can be started with npx:

npx -y @purplesquirrel/hedera-mcp

Set HEDERA_NETWORK to testnet, mainnet, or previewnet; it defaults to testnet. HEDERA_OPERATOR_ID is optional and accepts an account ID, not a private key. When supplied, it acts as the default payer or treasury while transactions are built. HEDERA_MIRROR_URL can override the default Mirror Node REST base URL, including for a private or HGraph endpoint.

The README shows configuration for Claude Desktop and Claude Code using the npx command and these environment variables. The project is licensed under MIT.

Tools and capabilities

• Build unsigned account and HBAR transactions.
• Create and manage fungible tokens and NFT collections.
• Build HCS topic and message transactions.
• Deploy, update, execute, query, and inspect EVM contracts.
• Create, append to, update, and delete Hedera files.
• Create, sign, delete, and inspect scheduled transactions.
• Query balances, NFTs, transactions, blocks, allowances, contracts, network fees, supply, nodes, and exchange rates.

Limitations and notes

The hedera-mcp MCP server does not sign or submit transactions and never handles private keys. A separate wallet, SDK, or CLI is required for live writes. The optional HEDERA_OPERATOR_ID is only an account identifier and does not authenticate the server or authorize spending.

Read availability depends on the configured Mirror Node. EVM contract queries require a known ABI when using ABI-aware calls. Although the repository includes live testnet verification and test harnesses, those harnesses are separate from the MCP server; any signing key used for live execution belongs to the test setup, not the server.