Hedera MCP Server

Created By
hashgraph-onlinea year ago
Overview

What is Hedera MCP Server?

Hedera MCP Server is a production-ready Model Context Protocol (MCP) server that enables AI agents and LLMs to interact with the Hedera hashgraph network using natural language. Users can execute transactions, check balances, and manage tokens by simply describing their requests in plain English.

How to use Hedera MCP Server?

To use the Hedera MCP Server, clone the repository from GitHub, configure your environment with your Hedera credentials, and start the server using Docker or local development setup. You can then interact with the server via JSON-RPC or SSE endpoints.

Key features of Hedera MCP Server?

  • Natural language processing for transactions and queries.
  • Zero-config setup with automatic database initialization.
  • Hot reload for instant updates without restarts.
  • Analytics dashboard for tracking usage and credits.
  • Support for token operations and smart contracts.

Use cases of Hedera MCP Server?

  1. Executing transactions like transferring HBAR or creating tokens using natural language.
  2. Managing account balances and transaction histories through simple commands.
  3. Scheduling transactions for future execution.

FAQ from Hedera MCP Server?

  • Can I use Hedera MCP Server for all Hedera operations?

Yes, it supports a wide range of operations including transactions, token management, and smart contracts.

  • Is there a cost associated with using the server?

Yes, operations consume credits that can be purchased with HBAR.

  • How do I authenticate with the server?

You can authenticate using an API key generated through the request-auth challenge process.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hashgraph-online
Star
0
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
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)

2 days ago