GoTRON MCP

MCP金融服务

提供方 fbsobreira

金融服务 未标注 API Key 社区 / 第三方 Claude DesktopClaudeCursorCodex
查看接入方式

MCP server for TRON blockchain — connect AI agents to TRX, TRC20, smart contracts, staking & governance via GoTRON SDK

一句话选型结论

按资料字段整理

GoTRON MCP 属于金融服务类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类金融服务 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

金融服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

tron smart contracts blockchain grpc cryptocurrency web3 ai agents claude

支持客户端

适用场景

tronsmart contractsblockchain

安装与配置

未标注 API Key
上游未给出传输方式
gotron-mcp --network mainnet

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
行情与财务数据

查行情、财报、汇率等金融数据。

支付与账务查询

查订单、账单与交易流水。

风控与核验

做身份、信用与风险信息核验。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在金融服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
GoTRON MCP当前 未标注 未标注 未标注 有 未标注
Alpaca MCP 62 stdio · 本地进程 支持远程部署 有 2026-05-18
OpenNews MCP 11 stdio · 本地进程 支持远程部署 有 2026-05-17
MCP Server 273df76d 未标注 stdio · 本地进程 本地部署 有 2026-05-17
tradingview-mcp 未标注 stdio · 本地进程 本地部署 有 2026-04-19
goat (Goat SDK) 未标注 未标注 未标注 无 2026-05-17

服务器档案

金融服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方fbsobreira上游标注的维护方 fbsobreira
分类金融服务本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

11.4 KB
来自项目仓库与上游目录的原文,未做删改

GoTRON MCP Server

MCP server for TRON blockchain — let AI agents query balances, tokens, blocks, and build transactions.

Built on the GoTRON SDK and the Model Context Protocol.

Two Modes

Local Mode Hosted Mode
Transport stdio Streamable HTTP
Read tools All All
Transaction builders All (unsigned tx hex) All (unsigned tx hex)
Sign/Broadcast Opt-in via keystore passphrase Disabled
Install Required Zero install

Install

Go Install```bash

go install github.com/fbsobreira/gotron-mcp/cmd/gotron-mcp@latest


### Homebrew```bash
brew install fbsobreira/tap/gotron-mcp

curl```bash

curl -fsSL gotron.sh/install-mcp | sh


### Docker```bash
docker run -p 8080:8080 ghcr.io/fbsobreira/gotron-mcp

The image starts the HTTP transport. For stdio, append --transport stdio:```bash
docker run -i --rm ghcr.io/fbsobreira/gotron-mcp --transport stdio


### MCP Registry

Published to the MCP Registry as `io.github.fbsobreira/gotron-mcp` on each stable release tag (vX.Y.Z), from v0.4.1, with the Docker image (stdio) and the hosted endpoint.

### Hosted (zero install)

Connect directly to `https://mcp.gotron.sh/mcp` — no installation needed.

### Claude Code plugin

The `gotron` plugin bundles the hosted server with skills for USDT transfers and energy estimates. The `gotron-local` plugin runs the `gotron-mcp` binary locally and supports keystore signing.

Public marketplace installation is not available yet. To connect today, use the Claude Code MCP setup below. Plugin source and configuration details are in the directories linked above.

## Claude Desktop Configuration

### Local mode```json
{
  "mcpServers": {
    "gotron": {
      "command": "gotron-mcp",
      "args": ["--network", "mainnet"],
      "env": {
        "GOTRON_NODE_API_KEY": "your-trongrid-api-key"
      }
    }
  }
}

Local mode with keystore signing```json

{
"mcpServers": {
"gotron": {
"command": "gotron-mcp",
"args": ["--network", "mainnet"],
"env": {
"GOTRON_NODE_API_KEY": "your-trongrid-api-key",
"GOTRON_MCP_KEYSTORE_PASSPHRASE": "your-keystore-passphrase"
}
}
}
}


### Hosted mode (zero install)```json
{
  "mcpServers": {
    "gotron": {
      "url": "https://mcp.gotron.sh/mcp"
    }
  }
}

Claude Code

Choose one of the following setup options.

Project-wide local server:```bash
claude mcp add gotron --scope project -- gotron-mcp --network mainnet


**User-wide local server with keystore signing:**

If a project-scoped `gotron` entry already exists, remove it first with `claude mcp remove gotron --scope project`. For a local-scoped entry, use `claude mcp remove gotron --scope local`. Check the selected entry with `claude mcp get gotron`: local and project entries take precedence over user entries, and their settings are not combined. See Claude Code's scope precedence.

Save an environment-variable reference rather than the passphrase itself. Keep the single quotes so your shell does not expand the reference while registering the server:```bash
claude mcp add gotron --scope user -e 'GOTRON_MCP_KEYSTORE_PASSPHRASE=${GOTRON_MCP_KEYSTORE_PASSPHRASE:-}' -- gotron-mcp --network mainnet

Then launch Claude from Bash or Zsh with a hidden passphrase prompt:```bash
(
set +x
printf 'Keystore passphrase: '
IFS= read -r -s GOTRON_MCP_KEYSTORE_PASSPHRASE || exit 1
printf '\n'
export GOTRON_MCP_KEYSTORE_PASSPHRASE
claude
)


The subshell limits the exported value to that Claude session. The prompt keeps the passphrase out of shell history and command-line arguments; it is still available in the environment of Claude and its MCP server. Repeat the prompt when starting a new signing session. Without a supplied passphrase, the reference expands to an empty value and wallet/signing tools stay disabled.

If you previously registered a literal passphrase with `-e`, it was stored in plain text in `~/.claude.json` and may also remain in shell history. Remove the old user-scoped entry with `claude mcp remove gotron --scope user`, register it again using the reference above, and remove the old history entry. See Claude Code's environment-variable expansion documentation.

**User-wide local server without keystore configuration:**```bash
claude mcp add gotron --scope user -- gotron-mcp --network mainnet

Hosted server (zero install):```bash
claude mcp add gotron --scope user --transport http https://mcp.gotron.sh/mcp


## Available Tools

### Read-Only (both modes)

| Tool | Description |
|------|-------------|
| `get_account` | Get account balance, bandwidth, energy, and details |
| `get_account_resources` | Get energy/bandwidth usage and limits |
| `get_trc20_balance` | Get TRC20 token balance for an account |
| `get_trc20_token_info` | Get TRC20 token name, symbol, and decimals |
| `analyze_transfer_cost` | Estimate TRX or TRC20 transfer costs, including account activation fees for new TRX recipients |
| `get_block` | Get block by number or latest |
| `get_transaction` | Get transaction details by ID |
| `list_witnesses` | List all super representatives |
| `get_contract_abi` | Get smart contract ABI |
| `estimate_energy` | Estimate energy cost for a contract call |
| `trigger_constant_contract` | Call read-only (view/pure) smart contract method |
| `decode_abi_output` | Decode ABI-encoded output or revert reasons from contract calls |
| `list_contract_methods` | Get human-readable summary of contract methods |
| `get_chain_parameters` | Get network parameters |
| `validate_address` | Validate a TRON address |
| `get_energy_prices` | Get energy price history |
| `get_bandwidth_prices` | Get bandwidth price history |
| `list_proposals` | List governance proposals |
| `get_network` | Get current network connection info |
| `get_pq_capabilities` | Report node and build support for post-quantum (TIP-899) signing |

### Transaction Builders (both modes)

| Tool | Description |
|------|-------------|
| `transfer_trx` | Build unsigned TRX transfer |
| `transfer_trc20` | Build unsigned TRC20 token transfer |
| `freeze_balance` | Build unsigned stake TRX for energy/bandwidth (Stake 2.0) |
| `unfreeze_balance` | Build unsigned unstake TRX (Stake 2.0) |
| `vote_witness` | Build unsigned vote for super representatives |
| `trigger_contract` | Build unsigned smart contract call |

### Sign & Broadcast (local mode + keystore)

| Tool | Description |
|------|-------------|
| `sign_transaction` | Sign transaction using local keystore |
| `broadcast_transaction` | Broadcast signed transaction to network |

### Post-quantum signing (TIP-899, Nile)

`create_wallet(name, key_type?)` accepts `ecdsa` (default), `ml_dsa_44` or `fn_dsa_512`; `list_wallets` and signing results report `key_type`. `sign_transaction`, `sign_and_broadcast`, `sign_and_confirm` and `request_limit_override` accept PQ wallets with the same policy limits, Telegram approval and elicitation as ECDSA wallets.

- TIP-899 is a draft, live only on Nile (`grpc.nile.trongrid.io:50051`); governance switches each scheme on or off and mainnet reports none. Use `get_pq_capabilities` to check the node and this build.
- Before any policy check or approval, a PQ signature requires that the node has the scheme enabled and that the wallet's address is a key of the transaction's permission (`permission_id`) on the owner account. A fresh PQ address must receive TRX first.
- PQ keys are stored encrypted with `GOTRON_MCP_KEYSTORE_PASSPHRASE` under `/pq-keys//` (wallet-cli compatible, same layout as tronctl). Point `--keystore-dir` at a tronctl config root (e.g. `~/.tronctl`) to reuse its keys; the passphrase must match their password. Wallet names are unique across ECDSA and PQ wallets; `list_wallets` flags `duplicate_name: true` and such a wallet cannot sign until one copy is renamed.
- The signature goes into `pq_auth_sig` (txid unchanged); a transaction carries at most 5 signatures, ECDSA and PQ combined. PQ transactions are about 10-22x larger than ECDSA ones (roughly 10x for FN-DSA-512, 22x for ML-DSA-44), so they use more bandwidth.
- ML-DSA-44 is pure Go and works in every build. FN-DSA-512 (Falcon-512, currently enabled on Nile) needs a build with `-tags falcon`, CGO and liboqs installed via pkg-config: `CGO_ENABLED=1 go build -tags falcon ./cmd/gotron-mcp`. Without it, FN-DSA create/sign returns an error pointing to the `gotron-mcp-pq` build; release binaries for it are planned (GOT-97).
- Not supported yet: adding a PQ key to an existing account's permissions from MCP (GOT-98; use tronctl or the SDK guide) and co-signing one transaction with several MCP wallets (GOT-99).

## Configuration

| Flag | Env Var | Default | Description |
|------|---------|---------|-------------|
| `--node` | `GOTRON_MCP_NODE` | (per network) | TRON gRPC node address |
| `--api-key` | `GOTRON_NODE_API_KEY` | — | TronGrid API key |
| `--network` | `GOTRON_MCP_NETWORK` | `mainnet` | Network: mainnet, nile, shasta |
| `--transport` | — | `stdio` | Transport: stdio, http |
| `--port` | — | `8080` | HTTP server port |
| `--bind` | — | `127.0.0.1` | HTTP server bind address |
| `--fallback-node` | `GOTRON_MCP_FALLBACK_NODE` | — | Fallback gRPC node (auto-failover) |
| `--keystore-dir` | `GOTRON_MCP_KEYSTORE_DIR` | `~/.gotron-mcp/wallets` | Wallet directory |
| `--keystore-pass` | `GOTRON_MCP_KEYSTORE_PASSPHRASE` | — | Keystore passphrase; wallet and sign tools are registered only when set |
| `--tls` | — | `false` | Use TLS for gRPC connection (default: plaintext) |

### Network Presets

| Network | Default Node |
|---------|-------------|
| mainnet | `grpc.trongrid.io:50051` |
| nile | `grpc.nile.trongrid.io:50051` |
| shasta | `grpc.shasta.trongrid.io:50051` |

Explicit `--node` overrides network presets.

Contract reads require a node with `vm.supportConstant = true`. If a node reports that constant execution is unsupported, reads try `--fallback-node` when configured. TRC20 reads also use the fallback for empty results, since token reads require return data. General contract simulations can succeed without return data. The fallback must serve the same network. This fallback applies per call, independently of block health checks; contract reverts are returned as errors.

For TRX transfers to unactivated recipients, `analyze_transfer_cost` reads the account creation fees and bandwidth multiplier from chain parameters. Only staked or delegated bandwidth can cover account creation; free bandwidth cannot. If recipient activation or the required fee parameters cannot be determined, the tool returns an error instead of quoting zero.

## Security

- The server **never** stores or manages private keys directly
- All write tools return **unsigned transaction hex** — the user decides how to sign
- Keystore signing is opt-in: wallet and sign tools are registered only when a keystore passphrase is set
- In hosted (HTTP) mode, all write and sign tools are automatically disabled
- API key is optional and only needed for TronGrid rate limits

## Development```bash
# Build
make build

# Format code
make fmt

# Run tests
make test

# Lint
make lint

# Run HTTP mode locally
make run-http

Community

Built and maintained by a CryptoChain community developer.

If you find this project useful, consider supporting TRON governance by voting for the CryptoChain Super Representative:

  • Vote on TronScan
  • SR Address: TKSXDA8HfE9E1y39RczVQ1ZascUEtaSToF

License

LGPL-3.0 — same as the GoTRON SDK.

Links

  • GoTRON SDK
  • GoTRON
  • MCP Specification

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
GoTRON MCP 怎么安装?

在客户端按下面的安装命令接入:gotron-mcp --network mainnet。装完在客户端配置里引用同一个包或端点。

GoTRON MCP 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

GoTRON MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

GoTRON MCP 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

GoTRON MCP 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

GoTRON MCP 能提供哪些能力?

资料显示能力标签包括 tron、smart contracts、blockchain、grpc、cryptocurrency、web3。具体工具清单以官方文档为准。

GoTRON MCP 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。