Hedera announces network MCP and wallet connectors

Hedera releases Network MCP and Wallet Connector: AI proxy transaction process attracts attention

Hedera announced the launch of its Network MCP and Wallet Connector. This combination purportedly allows AI agents to create, sign and send transactions from Claude Code. However, key details about who controls the signing key remain unconfirmed.

This announcement will be released on September 14, 2026. Hedera said the two products are designed to connect AI tools directly to the Hedera network. The company positions it as a convenience layer for developers; critics of agent-based signature designs argue that the design raises a custody issue, and the material released does not fully answer that concern.

Core Points

• Hedera announced the release on September 14, 2026.
• Network MCP is explicitly mentioned in the announcement.
• Wallet Connector is also mentioned in the announcement.

Product Features and Workflow

Hedera said that Hedera Network MCP and Wallet Connector are now online. Officials describe a workflow: AI agents can create, sign, and send Hedera transactions within Claude Code. These two products were introduced together as the core content of this release.

The settings specified follow three steps: adding an MCP, connecting a wallet, and then signing and sending. According to release notes, HashPack and Kabila are listed as available wallet connection options.

This workflow echoes Hedera's broader strategy of positioning the network as a platform that supports automation tools. Recent changes in Hedera's leadership also demonstrate its new strategic focus on AI integration. It should be noted that these release descriptions come from Hedera's official product behavior has not been verified by independent testing.

Product definitions and open issues

Network MCP refers to the Hedera network's MCP server, and Wallet Connector is the part that links supported wallets, of which HashPack and Kabila have been named. Although the announcement distinguishes the two products, it only describes their specific division of responsibilities in a high-level manner.

The most direct rebuttal focuses on signing permissions rather than setting steps. Liviu Epure, whose qualifications have not been independently verified, writes that the key detail worth keeping track of is which key the agent ultimately holds, because the cycle of signing is the same as the cycle of reading the output of an untrusted tool.

"The part worth noting is which key the agent ultimately holds, because the cycle of signing is the cycle of reading the output of an untrusted tool. Hedera is unique in that it has the right basic primitives at the account level rather than the contract level..."

As a protocol context, Hedera's governance record already includes limit authorization controls. According to the proposal text, HIP-336, labeled "Final", describes an authorization mechanism that allows third-party accounts to transfer HBAR, homogenization tokens and NFTs.

The same proposal stipulates that authorization can be revoked by setting the authorization amount of HBAR or homogenization tokens to zero through CryptoApproveAllowance. In addition, the consumer needs to sign when performing the authorized transfer, while the owner does not need to sign, and the fee is paid by the caller's account. These are existing basic account-level primitives and do not confirm that the new connector uses these functions.

Release details still need to confirm that the

announcement fails to address several practical points that developers need to weigh before using it. The software package or release, detailed installation requirements, and whether the tool is targeted at the mainnet, testnet, or both were not confirmed. The full scope of supported transactions has not been determined.

Key escrow, approval prompts, and default connector permissions were also not verified. During the study, Hedera's official MCP product page returned an HTTP 403 error, making it impossible to read the specifications. The omission does not indicate that Hedera intentionally withheld or failed to publish this information.

In terms of market background, HBAR traded at $0.077665 during the study snapshot period, up 3.79% from the previous session, with a market cap of nearly $3.4 billion. No link has been established between this price change and this release.

Overall market sentiment is at 57 on the Crypto Fear & Greed Index, classified as "Greed," which measures the entire market rather than Hedera specific. During the cycle, HBAR has fluctuated, including recent trading breakthroughs in key support levels earlier.

The bullish view holds that as institutional interests such as the Canary HBAR ETF already traded on the Hedera network expand, Hedera will apply its account-level basic primitives to AI-driven workflows. The bearish view is straightforward: Until hosting, privilege defaults, and network scope are documented and tested, the community response raises the issue of signature permissions still unresolved.

Disclaimer : This article is for reference only and does not constitute financial or investment advice. There are significant risks in the cryptocurrency and digital asset markets. Before making a decision, be sure to study it yourself.