tron_mcp_server

This MCP server provides a feature-rich integration with the TRON blockchain, enabling AI assistants to perform balance checks, manage transactions, interact with smart contracts, and fetch real-time blockchain data. It includes a smart fallback system that automatically uses a local TRON node when available, with TronGrid and TronScan as backups to ensure high availability and reliability. Available tools cover balance inquiries, resource estimation, contract interaction, and block/data retrieval, plus direct API calls to TronGrid and TronScan for advanced use cases. You can query current energy prices, monitor network parameters, and browse TRON documentation directly through the MCP interface.

To use the tools, start the MCP server and configure Claude or your MCP client to point to the tron MCP server. Common actions include checking a TRX balance with get_balance, estimating energy for a contract call with estimate_contract_energy, calling a read-only contract method via contract_call, and retrieving block or transaction data with get_block or get_transaction. For API-backed data, you can leverage trongrid_api_call and tronscan_api_call to fetch data directly from TronGrid or TronScan as needed. The server also exposes get_energy_prices to understand current energy costs, and get_current_block_number to monitor the chain state in real-time.

Prerequisites:\n- Node.js 18 or higher\n- npm (or yarn)\n- Access to a TRON wallet address (for balance queries)\n- Optional: TronGrid API key for higher rate limits\n\nQuick Installation (Recommended)\n1) Clone the repository and enter the project:\nbash\ngit clone https://github.com/Netts-official/tron_mcp_server.git\ncd tron_mcp_server\n\n2) Run the automated setup script:\nbash\n# For Linux/macOS\nchmod +x setup.sh\n./setup.sh\n\n# For Windows (PowerShell)\n.\setup.ps1\n\n# Alternative: Use npm script\nnpm run install-claude\n\nThe setup script will:\n- Check Node.js version (18+)\n- Install npm dependencies\n- Create .env from .env.example\n- Configure Claude CLI (if installed)\n- Configure Claude Desktop (if installed)\n- Test server functionality\n\nManual Installation\nIf you prefer manual setup:\n1) Install dependencies:\nbash\nnpm install\n\n2) Configure environment variables:\nbash\ncp .env.example .env\n# Edit .env with your configuration\n\n3) Add to Claude CLI:\nbash\nclaude mcp add tron -s user -- node /absolute/path/to/src/index.js\n\n4) Test the installation:\nbash\nnpm test-server\n

Environment variables and configuration tips:\n- NETWORK should match your target TRON network (mainnet by default).\n- FULL_NODE_URL, SOLIDITY_NODE_URL, and EVENT_SERVER_URL should point to accessible TRON nodes. If you run your own node, ensure CORS and network permissions allow MCP access.\n- TRONGRID_API_KEY is optional but recommended for higher rate limits when using fallback sources.\n- PRIVATE_KEY is optional and should be kept secure; it is only required for sending transactions.\n- The smart fallback system prioritizes the local node, then TronGrid, then TronScan. If a source is unavailable, the MCP will transparently switch sources to maintain uptime.\n- When integrating with Claude, ensure the mcpServers configuration references the correct path to src/index.js and that environment variables are properly loaded in Claude’s and Cursor/CLI environments.\n- If you encounter issues with contract calls, verify gas/energy estimation and the contract’s accessibility (read-only calls via TronGrid may be faster).