Build-only Hedera (Hashgraph) MCP — 51 tools across Account, HTS, HCS, EVM, File & Schedule.
Hedera MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Build-only Hedera (Hashgraph) MCP — 51 tools across Account, HTS, HCS, EVM, File & Schedule.
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.
Once Hedera is connected, these are the calls the assistant has available:
Service — Official starter MCPAccount — balanceFile — —Schedule — —Network — —HEDERA_NETWORK — testnetHEDERA_OPERATOR_ID — (unset)HEDERA_MIRROR_URL — per-networkYou will need 4 environment variables: HEDERA_NETWORK, HEDERA_OPERATOR_ID, HEDERA_MIRROR_URL, HEDERA_OPERATOR_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @purplesquirrel/hedera-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Hedera's toolset — Service, Account, File and 5 more — is a fair guide to whether it matches your workflow. It is maintained by ExpertVagabond; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Hedera's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Service | Official starter MCP |
| Account | balance |
| File | — |
| Schedule | — |
| Network | — |
| HEDERA_NETWORK | testnet |
| HEDERA_OPERATOR_ID | _(unset)_ |
| HEDERA_MIRROR_URL | per-network |
{
"mcpServers": {
"hedera": {
"command": "npx",
"args": ["-y", "@purplesquirrel/hedera-mcp"],
"env": {
"HEDERA_NETWORK": "testnet",
"HEDERA_OPERATOR_ID": "0.0.1234"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| HEDERA_NETWORK | Configuration value read at startup. | Optional |
| HEDERA_OPERATOR_ID | Configuration value read at startup. | Optional |
| HEDERA_MIRROR_URL | Endpoint or connection string the server talks to. | Yes |
| HEDERA_OPERATOR_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.