
Hedera Mcp
io.github.ExpertVagabondPublished by GitHub account ExpertVagabondv0.5.0Updated Oct 24, 2026
Build-only Hedera (Hashgraph) MCP — 73 tools across all core services plus analytics reads.
Overview
A build-only Hedera (Hashgraph) MCP server that lets an assistant construct and inspect Hedera transactions and read network data, without ever holding keys.
- What you can do
- Build unsigned, frozen transactions for accounts, tokens, consensus topics, smart contracts, files and schedules, returned as base64 for you to sign elsewhere. Decode and inspect a built transaction before signing. Read network and analytics data from the public Mirror Node: blocks, transactions, balances, token and NFT holdings, allowances, contract state and results, stake, supply, fees and exchange rate. Look up accounts by public key or EVM address, and read keyless resources for exchange rate, supply, accounts and tokens.
- When to use it
- Useful when you want an AI assistant to help draft Hedera operations — creating tokens, topics, contracts or scheduled transactions — while you keep signing and submitting yourself. Also suited to exploring Hedera network and account data through Mirror Node reads.
- Requirements
- Local process run via npx from the npm package, so Node.js is needed. Optional environment variables: HEDERA_NETWORK (mainnet, testnet or previewnet; testnet by default), HEDERA_OPERATOR_ID (an account id used as default payer, not a key) and HEDERA_MIRROR_URL to override the Mirror Node REST base. Network access to the Mirror Node is required for reads.
Installation
In SourceWeft
- Open Hedera Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
hedera-mcp
[MCP Registry] [npm] [license]
Comprehensive Model Context Protocol server for Hedera (Hashgraph). Full coverage of every core Hedera service — Account, Token (HTS), Consensus (HCS), Smart Contract (EVM), File, Schedule, and Network — exposed as 79 MCP tools any AI agent (Claude, Cursor, etc.) can call.
Build-only. Never holds keys. Reads hit the public Mirror Node REST API (no auth). Writes return an unsigned, frozen transaction (base64) for you to sign and submit with your own wallet/SDK/CLI. This server never sees a private key and never executes anything.
Why this exists
The official Hedera Agent Kit ships a preconfigured MCP server, but its tool surface is intentionally small (balance, transfer, deploy). This server fills the gap with end-to-end coverage of the Hedera API, organized for developer education and agent-driven onboarding — so a developer can go from "certified" to "shipping their first HTS token / HCS topic / contract" inside a single AI session.
Security model
- Reads → public Mirror Node REST. No keys, no account required.
- Writes → the tool constructs the transaction, freezes it for offline signing, and returns base64 bytes plus a human summary. You inspect it (
hedera_decode_transaction), then sign and submit yourself. - The only optional environment input is
HEDERA_OPERATOR_ID— an account id, used as the default payer/treasury when building. Never a key.
This mirrors the posture of goat-network-mcp: safe to run anywhere, safe to give to an autonomous agent.
Published on npm and the MCP Registry as io.github.ExpertVagabond/hedera-mcp.
Install
Run directly with npx (no clone needed):
Or from source:
Configure (Claude Desktop / Claude Code)
Build-only workflow
Inspect anything before signing:
Tool catalog (79)
Account (8): create_account · transfer_hbar · update_account · delete_account · approve_hbar_allowance · get_account_info · get_account_balance · get_account_nfts
Token / HTS (23): create_fungible_token · create_nft_collection · mint_fungible · mint_nft · burn_token · transfer_token · transfer_nft · associate_token · dissociate_token · freeze_token_account · unfreeze_token_account · grant_kyc · revoke_kyc · pause_token · unpause_token · wipe_token · delete_token · update_token · token_airdrop · reject_token · approve_token_allowance · approve_nft_allowance · get_token_info · get_nft_info
Consensus / HCS (6): create_topic · submit_message · update_topic · delete_topic · get_topic_info · get_topic_messages
Smart contract / EVM (6): deploy_contract · execute_contract · update_contract · delete_contract · query_contract · get_contract_info — execute_contract & query_contract are ABI-aware (pass { abi, functionName, args }; calldata encoded + results decoded automatically)
File (4): create_file · append_file · update_file · delete_file
Schedule (4): create_schedule · sign_schedule · delete_schedule · get_schedule_info
Network / utility (7): prng · get_transaction · get_network_nodes · get_exchange_rate · get_network_supply · get_network_fees · decode_transaction
Analytics (Mirror Node reads, 14): get_block · get_blocks · get_account_transactions · get_token_balances · get_token_nfts · get_nft_history · get_account_allowances · get_account_token_allowances · get_account_nft_allowances · get_contract_results · get_contract_state · get_network_stake · search_accounts_by_pubkey · get_account_by_evm
Resources (4)
Besides tools, the server exposes addressable, keyless MCP resources agents can read by URI:
hedera://network/exchange-rate · hedera://network/supply · hedera://account/{accountId} · hedera://token/{tokenId}
Examples & learning
examples/TUTORIAL.md— Build on Hedera in 5 prompts (the certified→shipping learning path)examples/agent-demo.md— wire into Claude Desktop and build by asking;node examples/agent-sim.mjsprints a reproducible agent transcriptexamples/scenarios/— unique use cases, each runnable + Mirror Node-verified: HCS notary, AI agent audit trail, agent-to-agent payments, self-taxing token
Verification
npm run lint/npm run build— clean against@hashgraph/sdk2.81.0node test-battle.mjs— 72/73 in the auto-discovery suite (1 skip:query_contractneeds a known ABI, verified separately) → all 73 tools verified (pre-MPP; 79 with the MPP charge tools)node test-live.mjs— 10/10 write paths executed on testnet, Mirror Node-verifiednode test-battle-live.mjs— battle mode: 31/31 operations on testnet across two accounts (full token lifecycle incl. freeze/KYC/pause/wipe, NFT, topic, file, scheduled transfer requiring a 2nd signer, PRNG), Mirror Node-verified. Re-run signed by an ED25519 operator: 31/31 still pass — non-EVM tools are key-type-agnostic (the server holds no keys; EVM tools inherently require ECDSA per Hedera's EVM-alias rule)node test-contract.mjs— real Solidity contract compiled → deployed → executed → read end-to-end (store(42)→retrieve()= 42), confirming the full EVM path andquery_contractnode test-contract-abi.mjs— ABI-awarequery_contract: fed a raw ABI, it auto-encodes/decodes —answer()→ 73 (uint),title()→ "hedera-mcp" (string),ping()→ 73 (pure)node test-edge-cases.mjs— 12/12 edge paths on testnet the happy-path suites miss: large file via create+append (>1 tx chunk), HCS message >1024 B auto-chunked across 2 mirror entries (reassembled to 1200 B), NFT collection with a 10% royalty + 1ℏ fallback custom fee, delegated approved spend (operator approves B → B pulls 200 paying its own fee), HBAR → fresh ED25519 alias auto-account-create, and adecode_transactionround-trip
Development
Live execution verification
test-execute.mjs proves the build-only output is real: the MCP server builds an
unsigned transaction, the harness signs it with a throwaway testnet key from .env
and submits it, then confirms the result independently via Mirror Node. The server
stays build-only the whole time — only the test harness ever touches a key.
Get a free testnet account at portal.hedera.com.
Built on @hashgraph/sdk and @modelcontextprotocol/sdk.
Releasing
Bump the version in package.json, server.json (both top-level version and packages[0].version), and src/index.ts; update CHANGELOG.md; then publish to npm and the MCP Registry.
Then sync the MCP Registry. Run mcp-publisher from /tmp, not from the project directory — on this setup the project lives on a volume where the publisher can't persist its OAuth token (operation not permitted), which silently fails the publish step. Copying server.json to a writable scratch dir sidesteps it:
Verify all three surfaces are aligned:
License
MIT © Matthew Karsten
Source: README.md at commit 5f9a722
Tools
0Version history
1- v0.5.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts