TRON integrates deBridge MCP for cross-chain AI execution

TRON DAO integrated deBridge’s Model Context Protocol (MCP) server into the TRON network on April 17, 2026. The integration provides a single interface for developers and automated agents to request quotes, determine routing and execute transactions across multiple blockchains.

The MCP server connects TRON to deBridge’s liquidity network through a lightweight API that can be embedded in integrated development environments and agent systems. Developers and agents can request real‑time pricing, receive route suggestions and obtain executable transaction data within their existing workflows.

Transaction signing remains under the user’s control. The MCP server does not access private keys and returns transaction data that developers or agents can trigger to complete on‑chain execution.

TRON and deBridge described the setup as supporting one‑click or programmatic cross‑chain operations that reduce fragmented bridging flows by centralizing quote, routing and execution calls with minimal configuration. deBridge characterized its core protocol as solver‑driven and zero‑TVL and reported it has processed tens of billions in volume with no reported exploits.

Sam Elfarra, a TRON DAO spokesperson, commented: “Integrating deBridge’s MCP server enables AI agents to perform cross‑chain executions and allows developers to focus on building applications instead of managing cross‑chain swaps.” Alex Smirnov, deBridge co‑founder, added: “Applications increasingly use multiple chains; efficient and secure connections between ecosystems are required to meet user expectations.”

TRON DAO provided network metrics as of April 2026: more than 376 million user accounts, over 13 billion total transactions and upwards of $27 billion in total value locked. The announcement noted TRON formerly hosted the largest circulating supply of USDT, which exceeded $86 billion at one point.

The release did not list specific chains or tokens supported in the TRON deployment. Both organizations emphasized that the MCP server does not hold user funds and relies on on‑chain execution and user signing for transaction completion.