Hedera Testnet Mirror Node MCP Server

Name: Hedera Testnet Mirror Node MCP Server
Author: hedera-dev

@hedera-dev

Repository

About Hedera Testnet Mirror Node MCP Server

Hedera MCP server

#mirrornode #mcp-server #hedera

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mirrornode-mcp-server": {
      "command": "bun",
      "args": [
        "mcpServer.ts"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Hedera Testnet Mirror Node MCP Server?

It is a Model Context Protocol (MCP) server that interfaces with the Hedera Testnet Mirror Node API. Built using FastMCP and Zod, it automatically converts Hedera Mirror Node API endpoints (defined in OpenAPI specification format) into MCP‑compatible tools.

How to use Hedera Testnet Mirror Node MCP Server?

Clone the repository, install dependencies with npm install, then start the server with bun mcpServer.ts. The server listens for SSE connections on http://localhost:3333/hedera-testnet-mirror-node-api/sse.

Key features of Hedera Testnet Mirror Node MCP Server

Automatic conversion of OpenAPI endpoints into MCP tools
Server‑Sent Events (SSE) transport support
Input validation using Zod schemas
Proxies between an HTTP API client and the MCP transport

Use cases of Hedera Testnet Mirror Node MCP Server

Querying Hedera testnet transaction and account data via AI assistants
Enabling MCP‑compatible agents to interact with the Hedera network
Building automated workflows that read mirror node state
Testing and prototyping Hedera applications with a natural‑language interface

FAQ from Hedera Testnet Mirror Node MCP Server

What dependencies are required?

Bun (or another TypeScript runtime) and npm. All library dependencies (FastMCP, Zod, openapi‑zod‑client) are installed via npm install.

How are API endpoints converted into tools?

The server uses convertZodiosToMcp to process GET endpoints defined in an OpenAPI specification. Each endpoint is mapped to a Zod schema and registered as an MCP tool that executes the corresponding API call.