Hedera MCP

Created By
pisuthda year ago
MCP server implementation for the Hedera blockchain using the Hedera Agent Kit.
Overview

What is Hedera MCP?

Hedera MCP is an MCP server implementation for the Hedera blockchain, utilizing the Hedera Agent Kit. It enables AI models that support the Model Context Protocol (MCP) to interact seamlessly with the Hedera network, allowing users to perform various blockchain operations without needing extensive coding knowledge.

How to use Hedera MCP?

To use Hedera MCP, install Claude Desktop, configure it with your Hedera account details, and run the server either through Claude Desktop or standalone using the command npx hedera-mcp.

Key features of Hedera MCP?

  • Over 15 MCP tools for account and token operations.
  • Non-custodial setup ensuring no private keys are exposed.
  • Compatibility with MCP clients like Claude Desktop.
  • Integration with additional MCP tools for enhanced functionality.

Use cases of Hedera MCP?

  1. Managing HBAR balances and token distributions.
  2. Creating and minting fungible and non-fungible tokens.
  3. Automating blockchain tasks through AI interfaces.

FAQ from Hedera MCP?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows AI models to interact with blockchain networks in a standardized way.

  • Is Hedera MCP secure?

Yes, it is designed to be non-custodial, ensuring that private keys are not exposed on any server.

  • Can I use Hedera MCP without coding?

Absolutely! Hedera MCP allows users to perform blockchain operations without needing to write code.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pisuthd
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago