Hedera MCP Server

What is Hedera MCP Server?

A Model Context Protocol (MCP) server for interacting with the Hedera network. It provides tools for creating Hedera wallets, checking account balances, building transactions, and sending signed transactions, and is intended as a demo implementation – not for production use.

How to use Hedera MCP Server?

Clone the repository, install dependencies (npm install), create a .env file with your Hedera operator credentials and network choice (testnet or mainnet), then build (npm run build) and start the server (npm start). A test client (node test-client.js) demonstrates the complete end-to-end flow.

Key features of Hedera MCP Server

• Creates new Hedera accounts with a minimal initial balance
• Checks account balances in tinybars
• Builds unsigned transfer transactions
• Sends signed transactions to the Hedera network
• Uses Model Context Protocol for AI-agent integration
• Architecture keeps transaction construction server-side

Use cases of Hedera MCP Server

• AI assistants that autonomously create and manage Hedera wallets
• Automated testnet faucets that check balances and dispense funds
• Demonstration of centralised transaction logic with client-side signing
• Educational tool for learning the Hedera transaction lifecycle

FAQ from Hedera MCP Server

Is this server safe to use in production?

No. The README explicitly warns that this is a demo implementation with several security vulnerabilities, including sending private keys in response bodies and lacking encryption or transaction verification.

What are the runtime requirements?

Node.js version 18 or higher and npm or yarn. You also need a Hedera account (testnet or mainnet) with its operator ID and private key.

How do I configure the server?

Create a .env file with HEDERA_OPERATOR_ID, HEDERA_OPERATOR_KEY, and HEDERA_NETWORK. An optional PORT defaults to 3000.

What tools does the server expose?

Four MCP tools: create-wallet (no input), check-balance (accountId), build-transaction (sender, recipient, amount), and send-transaction (signedTransaction base64).

How does the transaction lifecycle work?

The server builds a transaction, the client signs it using the Hedera SDK, and the server submits the signed transaction to the Hedera network. The test client demonstrates this full flow.