Skip to main content
Glama

TEnergy MCP server

Let an AI agent rent TRON energy for you: check prices, estimate a USDT transfer, place an order and watch it land on chain — with a spending cap you set. Works with Claude, Cursor, ChatGPT and any client that speaks the Model Context Protocol.

  • Never touches a wallet key. It cannot sign transactions and refuses to start if one is passed.

  • Testnet by default. Mainnet only when you point it there.

  • Capped. An order above TENERGY_MCP_MAX_ORDER_TRX (default 50 TRX) is refused before buying.

Connect

Claude Desktop, Cursor (mcp.json):

{
  "mcpServers": {
    "tenergy": {
      "command": "npx",
      "args": ["-y", "@tenergy/mcp"],
      "env": { "TENERGY_API_KEY": "ak_test_...", "TENERGY_API_SECRET": "..." }
    }
  }
}

Claude Code:

claude mcp add tenergy -e TENERGY_API_KEY=ak_test_... -e TENERGY_API_SECRET=... -- npx -y @tenergy/mcp

ChatGPT and other remote clients: npx -y @tenergy/mcp --http 3333 behind HTTPS, then add https://<your-host>/mcp as a connector.

No key? It still runs: get_prices and get_address_resources are public.

Related MCP server: mcp-server-tronlink

Tools

Tool

Does

Needs a key

get_prices

Energy prices per tier

no

get_address_resources

An address's energy and bandwidth right now

no

estimate_transfer

Energy a USDT transfer between two addresses needs

yes

get_balance, get_deposit_addresses

Your prepaid balance and where to top it up

yes

create_quote

A price held for a short time

yes

create_order

Buys energy for a receiver; requires max_price_sun and client_order_id

yes, spends

get_order, list_orders

Order status, delegation hashes

yes

Resources: tenergy://docs/quickstart, tenergy://llms.txt.

Settings

Variable

Default

Meaning

TENERGY_API_KEY, TENERGY_API_SECRET

unset

Your key pair. Used to sign requests, never shown to the model

TENERGY_API_URL

https://api-nile.tenergy.me/v1

Nile testnet. Mainnet: https://api.tenergy.me/v1 with an ak_live_ key

TENERGY_MCP_MAX_ORDER_TRX

50

The most one order may cost

TENERGY_MCP_READ_ONLY

unset

1 removes create_quote and create_order, even with a spending key

npx -y @tenergy/mcp --help prints this table. Get a key in the dashboard; test TRX for Nile from the faucet.

Docs · TypeScript SDK · support@tenergy.me

MIT licensed. Node 22+.

Available Tools

11 tools
calculate_savingsB

Free. What renting energy saves versus burning TRX for USDT transfers: uses the live energy price from our price table and the chain burn price. Give transfers per day and the share that go to empty addresses.

Inputs: transfers_per_day (required), network, share_to_empty.

estimate_contract_callA

Read-only, free, no API key, nothing signed. Simulates a smart contract call on a public node (triggerconstantcontract) and returns the energy it would use and the TRX it would burn without energy. Give the function selector, e.g. "transfer(address,uint256)", and the ABI-encoded parameter hex.

Inputs: parameter (required), owner_address (required), contract_address (required), function_selector (required), +1 more.

explain_conceptA

Free, offline. A short, accurate explanation of a TRON resource concept for a user. Concepts: energy, bandwidth, delegation, burn, activation, recovery, rental, routing.

Inputs: concept (required).

get_address_resourcesA

Read-only, free, no API key needed. Returns the on-chain energy and bandwidth an address has right now (limits, used, available) and whether it is activated. Call it before buying to see whether the address already has enough energy for its next transfer.

Inputs: address (required), network.

get_chain_parametersA

Read-only, free, no API key. The TRON fee parameters now, read from a public node: energy price (getEnergyFee, SUN per unit), bandwidth price (getTransactionFee), free bandwidth per day, unstake delay in days.

Inputs: network.

get_energy_fee_historyA

Free, offline. Every approved change of the TRON energy price (getEnergyFee) since 2018 with its committee proposal and date, read from the chain on 2026-10-04.

Inputs: no named parameters.

get_marketA

Read-only, free, no API key. The live energy market: every venue TEnergy reads with its 1-hour and 1-day price per unit (SUN), when it was read, and our own price. Use it to compare venues or to tell a user where energy is cheapest right now.

Inputs: network.

get_market_summaryA

Read-only, free, no API key. One month of the energy market: for each venue min / median / max price, number of readings and share of time it answered, plus the median price by hour of day (UTC). Month as YYYY-MM.

Inputs: month (required), network.

get_price_historyA

Read-only, free, no API key. Price history of one market venue (slug from get_market; "tenergy" for ours): 5-minute points of the 1-hour and 1-day price over the last N hours.

Inputs: slug (required), hours, network.

get_pricesA

Read-only, free, no API key needed. Returns the current rental price table: for each resource (energy, bandwidth, activation) and tier (5m, 1h, 1d) the price in SUN per unit, min/max amount and available (false = listed but not buyable now; do not offer it), plus when the table stops being valid. Call it before telling a user a price; these prices are indicative, a binding price comes from create_quote.

Inputs: network, resource.

suggest_order_sizeA

Free, offline. How much energy to order for N USDT transfers, given how many go to addresses that already hold USDT and how many to addresses with a zero USDT balance (measured 2026-09-30: 64,285 vs 130,285 energy per transfer). Use get_address_resources first to know which case a recipient is.

Inputs: to_empty (required), to_holders (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tools mostly have distinct purposes, but get_prices and get_market both expose current energy prices, and get_price_history and get_market_summary both report market data. The descriptions clarify the differences, so confusion is limited but possible.

    Naming Consistency5/5

    All tool names use snake_case with clear verb_noun patterns such as get_prices, estimate_contract_call, suggest_order_size, calculate_savings, and explain_concept. The convention is consistent and predictable throughout.

    Tool Count5/5

    11 tools is well within the typical 3-15 range and fits the domain of TRON energy data, market info, and estimation. Each tool has a distinct function, though a few read-only queries could theoretically be consolidated.

    Completeness3/5

    The surface covers price data, address resources, chain parameters, estimation, savings, and concepts. However, get_prices explicitly references create_quote for binding prices, but no create_quote or order-placement tool exists, leaving a notable gap for completing a rental transaction.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers