Skip to main content
Connect your AI tools to the official Hedera documentation for real-time, accurate answers to your Hedera-related questions directly from the source. This server searches and reads the docs. To have an agent create Hedera transactions, use the Network MCP Server, part of AI Studio.

Quickstart

Server URL: https://docs.hedera.com/mcp (Streamable HTTP). No API key, wallet, or authentication is required. Pick your AI tool, add the server, then verify the connection.
Verify: Run claude mcp list and confirm hedera-docs is listed as a connected server.See Claude Code for more setup options and notes.

What Is the Hedera Docs MCP Server?

The Model Context Protocol (MCP) is an open standard that creates direct connections between AI applications and external data sources. Instead of relying on general web search results, MCP lets AI tools search your documentation directly for more accurate, up-to-date information. Hedera’s MCP server gives any MCP-compatible AI application access to every page in the Hedera docs navigation, including:
  • API references and SDK documentation
  • Code examples and tutorials
  • How-to guides and quickstarts
  • Network concepts and architecture docs
  • The OpenAPI specs for the mirror node REST API, the smart contract verification API, and the Hedera status API

Available Tools

The server exposes three tools: The filesystem tool is how an AI tool reads a complete page. Every page at the URL path /some/page is available at /some/page.mdx, and the OpenAPI specs are mounted under /openapi/ (openapi.yaml, hedera-status-api.yaml, and smart-contract-verification-api.yaml). The specs are stored as single-line JSON despite the .yaml name, so query them with jq rather than head. For example, an agent can call it with:
Each filesystem call is stateless: the working directory resets to / and nothing carries over between calls. Output is truncated to 30 KB per call. search_hedera and query_docs_filesystem_hedera only read published documentation. Both carry the MCP annotations readOnlyHint: true and destructiveHint: false, which some AI tools use to run them without asking for approval. submit_feedback is the one tool that sends data: when an AI tool calls it, the page path and feedback text are recorded as page feedback in the Hedera docs team’s Mintlify analytics dashboard. The server also publishes a hedera skill as an MCP resource. MCP gives an agent access to the docs content, and the skill tells it how to use that content, so connecting the server gives agents both. Search and the filesystem cover the pages in the docs navigation. Pages hidden from the navigation are not included.
Tool names are specific to each Mintlify-hosted server. Use the names your AI tool reports from the server rather than hardcoding them.

MCP Server URL

Use this URL to connect any supported AI tool to the Hedera documentation.

Installation

The Hedera Docs MCP server is a remote HTTP server hosted by Mintlify. No code is downloaded or executed on your machine. Your AI tool connects directly to https://docs.hedera.com/mcp over HTTPS and reads the documentation through the tools listed above. The server requires no authentication, wallet, or keys. To connect, you manually add the server URL to your AI tool’s configuration using the setup instructions below. This is the recommended approach because it gives you full visibility into what’s being configured, and no third-party packages are installed or executed on your system.

Quick Connect From Any Docs Page

The contextual menu at the top of every page on docs.hedera.com includes these options:

Setup by Tool

Note

If you run into issues, refer to the Additional Resources section below as setup instructions can change and that’s where you’ll find the most current guidance.

Claude (Web)

Claude supports MCP servers as custom connectors on Free, Pro, Max, Ultra, Team, and Enterprise plans. On the Free plan, you can add one custom connector.
  1. Go to Customize → Connectors, click + Add, then select Add custom connector.
  2. Enter the name Hedera Docs and the URL https://docs.hedera.com/mcp, then click Continue.
  3. Under Authentication, choose No sign-in, because the Hedera docs server is public. Click Continue, then click Add.
Verify: Click the ”+” button in the lower left of the chat box, select Connectors, and enable Hedera Docs. Claude will automatically use the Hedera Docs tools when your questions relate to Hedera development.

Claude Desktop

Claude Desktop supports remote MCP servers through custom connectors and local servers through Desktop Extensions. The Hedera docs server is remote, so add it as a custom connector:
  1. Go to Customize → Connectors, click + Add, then select Add custom connector.
  2. Enter the name Hedera Docs and the URL https://docs.hedera.com/mcp, then click Continue.
  3. Under Authentication, choose No sign-in, because the Hedera docs server is public. Click Continue, then click Add.
Verify: Click the ”+” button in the lower left of the chat box, select Connectors, and enable Hedera Docs.
Note: Remote connectors are configured through your Claude account, so a connector added on claude.ai is also available in Claude Desktop. On Team and Enterprise plans, an owner first adds the connector in Organization settings → Connectors, and members then connect to it from Customize → Connectors.

Claude Code

Claude Code connects to MCP servers via CLI commands. Run the following command in your terminal. --scope user makes the server available in every project; without it, Claude Code adds the server to the current project only.
Verify: Run claude mcp list and confirm hedera-docs is listed as a connected server.

Cursor IDE

Cursor reads MCP servers from mcp.json. You can also install and manage servers from the Customize page in the Cursor sidebar. Add the following to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in your project root (one project):
Verify: Open Customize in the Cursor sidebar and confirm hedera-docs is enabled. Then, in Cursor’s chat, ask “What tools do you have available?” and confirm the response lists the Hedera Docs tools.

VS Code (GitHub Copilot)

VS Code connects to MCP servers through GitHub Copilot. Add the Hedera server to your Copilot Global configuration so it’s available in every workspace. Option A: Command Palette (Recommended)
  1. Press Cmd + Shift + P (macOS) or Ctrl + Shift + P (Windows/Linux) and run MCP: Add Server.
  2. Select HTTP (HTTP or Server-Sent Events) and enter https://docs.hedera.com/mcp.
  3. When prompted for a server ID, enter hedera-docs.
  4. When prompted for a destination, select Global, then Copilot Global.
Verify: In the Chat view, send a prompt that names the server, such as “Use the hedera-docs MCP server to find how to create a topic on Hedera.” Expand the tool call in the response and confirm it came from hedera-docs. See VS Code’s Verify the first tool call for the full checks. Option B: Manual Configuration Create or edit ~/.copilot/mcp-config.json (or $COPILOT_HOME/mcp-config.json if you set COPILOT_HOME) and add the following, then run the verify step above:
Note: Earlier versions of this guide used .vscode/mcp.json with a "servers" key. VS Code still reads that file for compatibility but labels it deprecated, and it only applies to one project. To move an existing entry, copy it into mcp-config.json under "mcpServers", then remove it from .vscode/mcp.json.

Devin Desktop

Devin Desktop, formerly Windsurf, connects to MCP servers through its Devin Local agent. Devin Local supports the stdio, Streamable HTTP, and SSE transport types.
  1. Open or create the MCP config file for the scope you want:
    • User (all your projects): ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows)
    • Project (shared through version control): .devin/mcp_config.json
  2. Add the following:
  1. In the Agents window, click Customize in the agent sidebar, then click MCPs. hedera-docs appears in the This computer list. Refresh the list if it doesn’t.
If you also use Devin CLI, this command adds the server to the same user config file:
Note: The Available list on the MCPs tab shows servers from your MCP registries. Add the Hedera docs server through the config file rather than installing a similarly named third-party server from that list.

ChatGPT

ChatGPT connects to remote MCP servers through plugins. Account and workspace policies apply to adding and using custom MCP servers; on Enterprise workspaces, an admin controls these permissions. Steps (ChatGPT web):
  1. Go to ChatGPT Plugins, select the ”+” button, then select Add custom MCP server.
  2. Enter the name Hedera Docs and the description Search the official Hedera documentation., then enter the server URL https://docs.hedera.com/mcp.
  3. The Hedera docs server is public and needs no authentication. Review the risk warning and select I understand and want to continue.
  4. Select Create as a plugin and confirm the discovered tools match the Hedera Docs tools. Then install the plugin.
Verify: Start a new conversation, type @ in the prompt box, and select Hedera Docs. ChatGPT desktop app: open Settings → MCP servers, select Add server, enter Hedera Docs as the name, choose Streamable HTTP, and enter https://docs.hedera.com/mcp. Save the server, then select Restart.
Note: ChatGPT deep research and company knowledge expect an MCP server with tools named exactly search and fetch. The Hedera docs server uses different tool names, so use it in regular conversations through the plugin. See Connect and test your plugin for OpenAI’s current instructions.

Codex

Codex CLI, the Codex IDE extension, and the ChatGPT desktop app share MCP configuration in ~/.codex/config.toml. You can also scope the server to one project with .codex/config.toml, which Codex only reads for trusted projects.
Verify: Run codex mcp list and confirm hedera-docs appears. In a Codex session, ask “What tools do you have available?” and confirm the response lists the Hedera Docs tools. To edit the config file directly instead, add the following to ~/.codex/config.toml. The command above writes the same entry:

Gemini CLI

Google’s Gemini CLI supports MCP servers through a settings.json configuration file. It supports stdio, SSE, and Streamable HTTP transports.
Prerequisite: Install Gemini CLI with npm install -g @google/gemini-cli@latest.
Verify: Launch Gemini CLI, run /mcp, and confirm hedera-docs is listed with the Hedera Docs tools. Gemini CLI disables MCP servers, including user-level ones, in folders you haven’t trusted. If hedera-docs shows as disabled, trust the folder when Gemini CLI asks “Do you trust the files in this folder?” To edit the settings file directly instead, add the following to ~/.gemini/settings.json. In Gemini CLI v0.21.0 and later, the command above writes the same entry:
"type": "http" selects the Streamable HTTP transport, which the Hedera docs server uses; it does not accept SSE connections. These settings need Gemini CLI v0.21.0 or later. Earlier versions treat url as an SSE endpoint and cannot connect, so use "httpUrl": "https://docs.hedera.com/mcp" instead (current versions still accept httpUrl but mark it deprecated).

Agent Instructions

Connecting the server makes the Hedera Docs tools available. Project instructions tell your agent when to use them, so Hedera questions go to the docs instead of the model’s memory. Add the instructions to the file your AI tool reads at the start of every session. Some tools read more than one of these files, so add the instructions to only one of them.
Add the following to AGENTS.md in your project root. Codex, Cursor, and VS Code (GitHub Copilot) read this file.

Example Requests

After you connect the server, try these requests. Each one uses a different Hedera Docs tool.

Using Multiple MCP Servers

You can connect the Hedera Docs MCP server alongside other documentation MCP servers. Here’s an example Cursor configuration with multiple servers:
Connected MCP servers do not add documentation content to the conversation until the AI calls a tool. The AI decides when to search based on query relevance, so it doesn’t search every connected server for every question. When it does search, each query returns multiple results, so searching several servers for one question can make the conversation much longer and leave less room for the response. Best practices for multiple servers:
  • Connect only the servers relevant to your current work.
  • Be specific in your prompts so the AI searches the most relevant server.
  • Disconnect servers you’re not actively using to reduce context usage.

Configuration Reference

A quick-reference table of config file paths and JSON formats for each tool:

Troubleshooting

Server not connecting?
  • Verify the URL is exactly https://docs.hedera.com/mcp (no trailing slash).
  • Ensure you have an active internet connection.
  • Restart your AI tool after adding the configuration.
Tools not appearing?
  • The server exposes three tools: search_hedera, query_docs_filesystem_hedera, and submit_feedback. If none appear, the connection failed.
  • In Cursor, click the refresh button next to the server entry.
  • In VS Code, run MCP: List Servers from the Command Palette, select hedera-docs, and choose Restart Server. If that action isn’t offered, choose Stop Server, then Start Server.
  • In Claude Code, run claude mcp list to verify the server is registered.
  • In Devin Desktop, open Customize → MCPs and check that hedera-docs is in the This computer list.
Search returning no results?
  • Try rephrasing your query with more specific Hedera terminology.
  • Ensure the MCP server is enabled/active for your current chat session.
Rate limits: Mintlify, which hosts the server, applies rate limits to protect availability: If a limit is exceeded, the server returns HTTP 429 Too Many Requests. Back off and retry after a short delay. Limits reset on a rolling hourly window. Mintlify sets these limits and can change them; see Mintlify’s rate limits for the current values.

Additional Resources


Writer: Krystal, Senior DX Engineer

Editor: Ty, Senior Product Manager