buy_energy — powersun tron mcp MCP Tool
buy_energy
(buy energy) is one of 27 tools on the
powersun tron mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call buy_energy from your client
- Claude Code powersun tron mcp buy_energy run in your project directory
- Claude Desktop powersun tron mcp buy_energy ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor powersun tron mcp buy_energy ~/.cursor/mcp.json
- VS Code powersun tron mcp buy_energy .vscode/mcp.json
- Zed powersun tron mcp buy_energy ~/.config/zed/settings.json
- Windsurf powersun tron mcp buy_energy ~/.codeium/windsurf/mcp_config.json
- Cline powersun tron mcp buy_energy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI powersun tron mcp buy_energy ~/.gemini/settings.json
- Grok powersun tron mcp buy_energy .mcp.json (in your project root)
- ChatGPT powersun tron mcp buy_energy Settings → Connectors → Advanced → Developer mode
- Claude.ai powersun tron mcp buy_energy Settings → Connectors → Add custom connector
- LangChain powersun tron mcp buy_energy pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http powersun-tron-mcp https://powersun.vip/mcp
Other tools on this server
- get_prices
- estimate_cost
- get_available_resources
- get_market_overview
- get_balance
- broadcast_transaction
- get_orders
- get_order_status
- get_deposit_info
- get_swap_quote
- execute_swap
- get_pool_stats
- get_earnings
- get_auto_selling_config
- configure_auto_selling
- get_pool_delegations
- withdraw_earnings
- register_pool
- get_onchain_status
- check_pool_permissions
- trigger_vote
- get_auto_action_history
- register
- verify_registration
- build_permission_transaction
- broadcast_signed_permission_tx
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.