MCP server
TronGasAi ships an MCP server — a thin wrapper over the API that exposes actions as tools an AI assistant (e.g. Claude Desktop) can call. It authenticates with an API key, so everything is bounded by that key’s scope and daily spend limit.
- Read —
get_pricing,get_balance,preview_*,list_*(work with any key). - Write (spends TRX) —
buy_energy,create_auto_refill,enable_smart,pause_automation/resume_automation/cancel_automation(need atradeorfullkey).
Each write tool is labelled with the scope it needs. A read-only key lets an agent monitor an account with
no ability to spend; add a daily spend limit to cap a trade key.
Recommended setup for agents
Section titled “Recommended setup for agents”- Create a dedicated API key with the least scope the agent needs (
readfor monitoring,tradeto act). - Set a daily spend limit appropriate to the task.
- Configure the MCP server with that key. Rotate or revoke it anytime from the dashboard.
Transport
Section titled “Transport”The MCP server runs over stdio (local, e.g. Claude Desktop). A remote transport is planned.