Hedera

hedera-mcp

Model Context Protocol server for Hedera (Hashgraph)

73 tools build-only never holds keys 7 services + analytics testnet-verified

Full coverage of every core Hedera service — Account, Token (HTS), Consensus (HCS), Smart Contract (EVM), File, Schedule — plus a 14-tool Mirror Node analytics layer, exposed to any AI agent over MCP. Reads hit the public Mirror Node (no auth). Writes return an unsigned, frozen transaction you sign with your own wallet. The server never sees a private key and never executes anything.

73tools
72/73build+read verified
10/10live writes on testnet
8use cases · live-verified
0keys held

Watch

Install

npx @purplesquirrel/hedera-mcp

Add to Claude Desktop / Claude Code:

{
  "mcpServers": {
    "hedera": {
      "command": "npx",
      "args": ["-y", "@purplesquirrel/hedera-mcp"],
      "env": { "HEDERA_NETWORK": "testnet" }
    }
  }
}

The only optional env var is HEDERA_OPERATOR_ID — an account id, not a key.

Coverage

Account 8

create · transfer · update · delete · allowances · info · balance · NFTs

Token / HTS 23

create FT/NFT · mint · burn · transfer · associate · freeze · KYC · pause · wipe · update · airdrop · reject · allowances · info

Consensus / HCS 6

create · submit · update · delete topic · read messages

Smart Contract 6

deploy · execute · update · delete · eth_call read · info

File 4

create · append · update · delete

Schedule 4

create · sign · delete · info

Network 7

prng · transaction · nodes · exchange rate · supply · fees · decode

Analytics 14

blocks · account txns · token balances & NFTs · NFT history · allowances · contract results & state · stake · key & EVM lookup

Use cases

Eight runnable scenarios — each a single command that builds via the MCP, executes on testnet, and self-verifies via Mirror Node, including the negative assertions: the compliant token proves the network rejects a pre-KYC transfer; the DAO payout proves it won't move on a single signature. Source in examples/scenarios.

Notary

Hash a document → consensus-timestamp it → tampering becomes detectable.
HCSnode examples/scenarios/notary.mjs

AI audit trail

An agent logs every action to HCS, then replays its own verifiable history.
HCS + AInode examples/scenarios/audit-trail.mjs

Agent payments

Agent A pays Agent B in service-credit tokens per task, with a commerce ledger.
HTS + HCSnode examples/scenarios/agent-payments.mjs

Self-taxing token

Every transfer auto-tolls a treasury — protocol-enforced, no smart contract.
HTS custom feesnode examples/scenarios/self-taxing-token.mjs

Compliant token

KYC-gated + freezable: transfers are network-rejected until the issuer grants KYC. RWA / stablecoin rails.
HTS KYC + freezenode examples/scenarios/compliant-token.mjs

Verifiable raffle

Consensus PRNG (VRF-backed, not caller-seedable) picks a winner; prize NFT minted to them.
PRNG + NFTnode examples/scenarios/verifiable-raffle.mjs

DAO treasury

A 2-of-3 scheduled payout that stays pending until the signature threshold is met, then auto-executes.
Schedule + KeyListnode examples/scenarios/dao-treasury.mjs

Chain of custody

An NFT digital twin handed down a supply chain; provenance from transfer history + an HCS log.
NFT × HCSnode examples/scenarios/chain-of-custody.mjs

Build-only flow

agent → hedera_create_fungible_token
      → server builds + freezes TokenCreateTransaction
      → returns base64 (unsigned)
      → you sign in HashPack / SDK / CLI → submit to Hedera

Inspect anything before signing with hedera_decode_transaction. Verified end-to-end on testnet: token create+mint, NFT create+mint, topic, file, scheduled transfer — all submitted from unsigned server output and confirmed via Mirror Node.