mirrornode

This MCP server exposes an interface that mirrors Hedera Testnet Mirror Node endpoints as MCP tools. It automatically converts the OpenAPI-described endpoints into MCP tools, validated by Zod schemas. Clients interact with the server via the MCP transport, while the server internally calls the Hedera Mirror Node HTTP API to fetch data. Note that Server-Sent Events (SSE) are not accessible to clients in this setup; the server operates over the MCP SSE pathway, exposing read-only endpoints that reflect the Mirror Node data. To use it, configure the server to point at the Hedera Testnet Mirror Node API and then invoke the generated MCP tools that correspond to Mirror Node GET endpoints. The tooling leverages a generated API client created with openapi-zod-client, then wraps each endpoint in an MCP tool that validates inputs and returns the API response.

Prerequisites:

• A runtime capable of TypeScript execution (Bun is recommended as used by the project) or a compatible environment to run TypeScript directly.
• Node.js installed if you plan to run via node (not required if using Bun).

Installation steps:

1. Clone the repository

git clone https://github.com/hedera-dev/mirrornode-mcp-server

2. Navigate to the project directory

cd mirrornode-mcp-server

3. Install dependencies

npm install

4. Start the server (example using Node as the launcher; adapt if using Bun or another TS runner)

node mcpServer.ts

If you prefer Bun (as the project suggests), you can run:

bun mcpServer.ts

5. Verify startup by checking for the log message indicating the MCP server started and the SSE endpoint address is available.

Notes and tips:

• The server uses FastMCP and Zod for input validation, with endpoint definitions generated from the Hedera Mirror Node OpenAPI specification.
• SSE transport is present in the server implementation, but this MCP server does not permit client connections over SSE for this setup.
• Ensure the MIRROR_NODE_API_BASE_URL environment variable is correctly set to the Hedera Testnet Mirror Node API base URL.
• If you encounter CORS or network issues when the server calls the Mirror Node API, verify network access from the hosting environment to the Mirror Node endpoint.
• The OpenAPI to MCP conversion validates that endpoints use GET and maps parameters to Zod schemas before exposing them as MCP tools.
• If you modify OpenAPI files, you may need to re-run the openapi-zod-client generation step (as described in the repo) to refresh the generated client and endpoint definitions.