mcp

TronSave MCP — buy/sell/extend TRON resources (ENERGY, BANDWIDTH) on the TronSave market. Networks (by endpoint): POST /mcp = mainnet, POST /testnet/mcp = testnet. Auth: call `tronsave_login` first, then send the returned `sessionId` as the `mcp-session-id` header on every later request. Two modes — (1) wallet SIGNATURE (preferred; required for platform tools): get a message via `tronsave_get_sign_message`, sign it client-side, submit `<signature>_<timestamp>`; (2) API KEY (`apiKey` param). Never send private keys to the server — signing is always client-side. Two tool families: - Platform (`tronsave_*`, GraphQL market): public discovery (list/estimate/order book/min price) plus signature-session mutations (create/cancel/update order, auto-sell, API keys). - Internal (`tronsave_internal_*` + `tronsave_get_internal_account`, REST, api-key account): estimate, create order, history, details, order book, extend — scoped to your deposited internal balance. Units: all prices are