Memungkinkan AI client untuk melakukan query langsung ke TON liteservers guna mengecek saldo, status akun, transaksi, get-methods, serta menyusun unsigned swaps.
Juga dikenal sebagai tonnode/mcp, mcp, @tonnode/mcp
- Stars
- 20
- Tools
- 16
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.9.2
- Commit terakhir
- 8 Okt 2026
- Lisensi
- MIT
Apa itu TON MCP?
TON adalah MCP server. Memungkinkan AI client untuk melakukan query langsung ke TON liteservers guna mengecek saldo, status akun, transaksi, get-methods, serta menyusun unsigned swaps. Server ini menyediakan 16 tool, seperti get_balance, get_jetton_balance, get_jetton_info.
Ringkasan dibuat dari README proyek
Tentang TON MCP server
Server ini memungkinkan AI agent untuk melakukan query langsung ke blockchain TON. Dengan menyediakan akses langsung ke liteservers melalui protokol native ADNL, server ini melewati HTTP gateway tradisional untuk mengambil data status akun, riwayat transaksi, dan saldo jetton. Developer dapat mengintegrasikan ini ke dalam client seperti Claude Desktop, Cursor, atau ChatGPT menggunakan perintah npx sederhana untuk penggunaan lokal, atau melalui endpoint hosted HTTP untuk deployment jarak jauh.
Selain pengambilan data sederhana, server ini juga memungkinkan agent untuk bertindak sebagai trader. Server mendukung penyusunan unsigned swap transactions untuk GRAM dan berbagai jetton menggunakan protokol Omniston, serta mengelola cross-chain swaps yang kompleks yang melibatkan jaringan seperti Ethereum, Arbitrum, dan Avalanche. Server ini juga menyertakan tool untuk membuat wallet baru dengan versi contract spesifik seperti v4 atau highload_v3. Bagi pengguna versi hosted, server mengelola autentikasi melalui Bearer keys dan menyediakan rate limiting yang granular untuk memastikan performa yang stabil.
Apa yang bisa Anda lakukan dengannya
- 1Cek saldo walletAI agent dapat menentukan jumlah kepemilikan GRAM atau USDT saat ini dari sebuah address tertentu.
- 2Siapkan decentralized swapsDeveloper dapat meminta AI untuk membuat unsigned transaction untuk pertukaran token yang siap ditandatangani oleh wallet.
- 3Eksekusi cross-chain tradesAgent dapat mengelola siklus hidup trade yang memindahkan aset dari TON ke jaringan lain seperti Polygon atau Base.
- 4Buat identitas baruAnda dapat menginstruksikan AI untuk membuat wallet baru lengkap dengan mnemonic 24 kata dan versi contract tertentu.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal TON MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal TON MCP di Claude Code
$ claude mcp add mcp -- npx -y @tonnode/mcpInstal TON MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@tonnode/mcp"
]
}
}
}Instal TON MCP di VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@tonnode/mcp"
]
}
}
}Instal TON MCP di VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@tonnode/mcp"]}'Instal TON MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@tonnode/mcp"
]
}
}
}Instal TON MCP di Codex
$ codex mcp add mcp -- npx -y @tonnode/mcpInstal TON MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@tonnode/mcp"]
Instal TON MCP di Gemini CLI
$ gemini mcp add -s user mcp npx -- -y @tonnode/mcpInstal TON MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@tonnode/mcp"
]
}
}
}Tool TON MCP 16
Terdeteksi dari READMEget_balanceget_jetton_balanceget_jetton_infoget_transactionsget_account_staterun_get_methodparse_addressget_masterchain_infoget_swap_quotebuild_swap_txget_crosschain_quotebuild_crosschain_swap_tx
| get_balance | — | |
| get_jetton_balance | — | |
| get_jetton_info | — | |
| get_transactions | — | |
| get_account_state | — | |
| run_get_method | — | |
| parse_address | — | |
| get_masterchain_info | — | |
| get_swap_quote | — | |
| build_swap_tx | — | |
| get_crosschain_quote | — | |
| build_crosschain_swap_tx | — |
Tampilkan semua 16 toolTampilkan lebih sedikit tool
track_crosschain_swapdisclose_crosschain_secretbuild_crosschain_refundgenerate_wallet
| track_crosschain_swap | — | |
| disclose_crosschain_secret | — | |
| build_crosschain_refund | — | |
| generate_wallet | — |
Konfigurasi
TONNODE_KEYSTON_LITESERVERSOptional JSON array of private liteserver entries: [{"ip":"host","port":41000,"key":"<base64 ed25519>"}]. Defaults to the public global config.
TON_NETWORKSet to "testnet" to use the testnet global config.
| Nama | Deskripsi | Tipe |
|---|---|---|
| TONNODE_KEYS | — | |
| TON_LITESERVERS | Optional JSON array of private liteserver entries: [{"ip":"host","port":41000,"key":"<base64 ed25519>"}]. Defaults to the public global config. | |
| TON_NETWORK | Set to "testnet" to use the testnet global config. |
Pengecekan otomatis
Berjalan 13 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauLolos
- Lisensi open source (OSI)Lolos
- Ada commit atau release dalam satu tahun terakhirLolos
- Nama package tidak mirip dengan package populerLolos
- Remote endpoint menggunakan HTTPSLolos
- Tools yang bersifat destruktif telah diberi labelLolos
- Tidak ada instruksi tersembunyi untuk modelLolos
- Tidak ada advisory kritis pada paket atau dependensinyaLolos
README
Lihat di GitHub@tonnode/mcp
MCP server that gives AI agents direct liteserver access to The Open Network (TON) — no HTTP gateways in the middle. Balances, account state, transaction history and contract get-methods over TON's native ADNL protocol.
Built by TONNode — private TON liteservers, archive nodes, a mempool stream and a REST API (early access, on request).
Quick start
Add to Claude Desktop, Claude Code, ChatGPT, Cursor, Codex or any MCP client:
{
"mcpServers": {
"ton": {
"command": "npx",
"args": ["-y", "@tonnode/mcp"]
}
}
}
That's the whole integration. The server connects to TON mainnet via the public global config by default. Ready-made configs for every client — plus programmatic Node.js usage — live in examples/.
Tools
Naming note: the native coin was renamed from Toncoin to GRAM in June 2026; the network itself is still called TON. Tool outputs use
*_gramfields.
| Tool | What it does | Typical question |
|---|---|---|
get_balance |
GRAM balance of an address | "How much GRAM does EQ… hold?" |
get_jetton_balance |
Jetton/token balance (USDT and any TEP-74 token) | "How much USDT is on this wallet?" |
get_jetton_info |
Token metadata: name, symbol, decimals, supply | "What are this jetton's decimals?" |
get_transactions |
Recent transactions: values, senders, fees | "Did my payment arrive?" |
get_account_state |
Status, deployment flags, last-tx pointer | "Is this contract deployed?" |
run_get_method |
Read-only get-methods on contracts | "Call get_jetton_data on this master" |
parse_address |
Convert/validate EQ…/UQ…/raw forms, offline | "Are these two addresses the same?" |
get_masterchain_info |
Masterchain head: seqno, shard, hashes | "Is the network (or my endpoint) alive?" |
get_swap_quote |
Firm DEX swap quote (GRAM ⇄ any jetton) via Omniston | "How much USDT for 100 GRAM right now?" |
build_swap_tx |
Unsigned, TonConnect-ready swap transaction | "Prepare that swap for my wallet to sign" |
get_crosschain_quote |
Quote TON → Ethereum/Arbitrum/Base/BNB/Polygon/Avalanche | "How much USDT on Ethereum for my TON USDT?" |
build_crosschain_swap_tx |
Unsigned HTLC escrow transaction + its secret | "Start that cross-chain swap" |
track_crosschain_swap |
Live phases of a cross-chain trade on both chains | "Did the resolver lock my USDT on Ethereum?" |
disclose_crosschain_secret |
Reveal the secret — atomically settles both sides | "Complete the swap" |
build_crosschain_refund |
Unsigned cancellation that reclaims escrowed funds | "The trade stalled — get my money back" |
generate_wallet |
Mint a fresh TON wallet (mnemonic + keys + address) | "Create a wallet for my agent to use" |
Wallet generation
generate_wallet mints a brand-new wallet — a 24-word mnemonic, its ed25519 keypair and the address for the chosen contract version (v4 default, plus v3r2, v5r1 and highload_v3 for mass payouts). The v3r2/v4/v5r1 addresses come from @ton/ton's canonical contracts; highload_v3 is derived from the official contract code and cross-checked against a maintained reference implementation.
⚠️ This returns secret key material. In hosted mode the keys are generated on the server and returned over TLS — treat every generated wallet as hot: fine for programmatic/ephemeral use, but move any meaningful balance to cold storage, and keep the response out of logs and shared transcripts. The server never stores or logs the mnemonic or private key (only the public address). Operators can set
TONNODE_DISABLE_WALLET_GEN=1to remove the tool entirely.
Swaps — agents that can actually trade
get_swap_quote and build_swap_tx are powered by Omniston, STON.fi's RFQ protocol aggregating STON.fi and DeDust liquidity. No API key needed.
The flow is strictly non-custodial — the server never sees a private key, never signs and never broadcasts:
get_swap_quotelocks a firm quote (amounts in raw indivisible units; the answer includes the slippage floor, price impact, gas budget and DEX route).build_swap_txturns the quote into unsigned messages in exactly the shapetonConnectUi.sendTransaction()expects — signing and sending stay with the wallet owner.
Quotes expire in about a minute, so build promptly. Omniston emulates the transfer while building: if the wallet doesn't hold the input amount, the build fails up front instead of burning gas on-chain.
Cross-chain
The *_crosschain_* tools take the same idea across blockchains: pay in GRAM or any TON jetton, receive USDT/USDC/native coins on Ethereum, Arbitrum, Base, BNB, Polygon or Avalanche — settled through Omniston's atomic HTLC escrow, typically in well under a minute. TON is always the source chain (the signer is a TON wallet).
The agent drives the full atomic-swap lifecycle: quote → build (the tool generates the HTLC secret and hands it to the caller — the server keeps nothing) → sign & send → track both chains → disclose the secret to settle, or build a refund if the trade stalls. At no point can the server, the resolver or anyone else redirect the funds: the secret only completes the trade as quoted, and an unfilled escrow is always reclaimable by the owner wallet.
Hosted / self-hosted HTTP mode
The package also ships a Streamable-HTTP entry for remote deployments (this is what powers mcp.tonnode.io):
TONNODE_KEYS=tn_live_abc,tn_live_def PORT=8808 npx -y @tonnode/mcp --http
Want a ready-made hosted endpoint instead of running your own? Keys for mcp.tonnode.io are issued at tonnode.io/mcp. Clients connect without installing anything:
{
"mcpServers": {
"ton": {
"url": "https://your-host/mcp",
"headers": { "Authorization": "Bearer tn_live_abc" }
}
}
}
Requests are authenticated with Bearer keys and rate-limited per key (RATE_LIMIT_RPM, default 300). Besides Authorization: Bearer <key>, the server accepts a bare Authorization: <key> and X-API-Key: <key> — for gateways (e.g. Smithery) that reserve the Authorization header for themselves. Keys come from either TONNODE_KEYS (comma-separated, fixed) or TONNODE_KEYS_FILE — a JSON array of {"key", "label"?, "rpm"?, "expires"?} that is hot-reloaded on change and on SIGHUP: add or revoke customer keys with no restart, per-key rate limits, and self-expiring keys for subscription plans. A revoked key's live sessions are closed immediately. GLOBAL_RATE_LIMIT_RPM adds a total ceiling across all keys to protect the backend liteserver. Sessions are private to the key that opened them, idle sessions are swept after SESSION_TTL_MIN (default 30 minutes), and concurrent sessions are capped per key and globally. Without keys the server refuses to start; set TONNODE_ALLOW_OPEN=1 to explicitly run keyless behind your own firewall. GET /healthz for monitoring, deploy/tonnode-keys.sh for key management.
The server binds 127.0.0.1 by default — put a TLS reverse proxy (Caddy, nginx) in front and set HOST=0.0.0.0 only if the proxy runs on another machine. Ready-made systemd + Caddy configs live in deploy/.
Configuration
| Env var | Meaning |
|---|---|
TON_LITESERVERS |
Use your own liteservers instead of the public config: [{"ip":"1.2.3.4","port":40004,"key":"<base64 ed25519>"}] |
TON_CONFIG_URL |
Alternative global-config URL |
TON_NETWORK=testnet |
Use the testnet config (or pass --testnet) |
TONNODE_KEYS |
HTTP mode: comma-separated Bearer API keys (simple, fixed) |
TONNODE_KEYS_FILE |
HTTP mode: JSON key file with labels, per-key rpm, expires — hot-reloaded |
HOST |
HTTP mode: bind address (default 127.0.0.1) |
PORT |
HTTP mode: listen port (default 8808) |
RATE_LIMIT_RPM |
HTTP mode: default requests per minute per key (default 300) |
GLOBAL_RATE_LIMIT_RPM |
HTTP mode: total ceiling across all keys (default off) |
SESSION_TTL_MIN |
HTTP mode: idle minutes before a session is swept (default 30) |
MAX_SESSIONS / MAX_SESSIONS_PER_KEY |
HTTP mode: concurrent session caps (default 500 / 50) |
OMNISTON_API_URL |
Swap tools: alternative Omniston WebSocket endpoint (default wss://omni-ws.ston.fi) |
OMNISTON_INTEGRATOR_ADDRESS / OMNISTON_INTEGRATOR_FEE_BPS |
Swap tools: optional integrator revenue share in bps of the output — always visible to the caller as integrator_fee_units in every quote (default off) |
TONNODE_DISABLE_WALLET_GEN |
Set to 1 to remove the generate_wallet tool (e.g. on a shared hosted endpoint where you don't want key material generated server-side) |
A note on public liteservers
The default public-config liteservers are shared, rate-limited and keep no deep history — get_transactions beyond recent blocks will answer lt not in db. Agents also tend to query in bursts, which public gateways throttle.
For your own rate limit and archive history, point TON_LITESERVERS at a private liteserver — a keypair and a global.config.json from the console, paid from a balance funded in GRAM or USDT. How the config file, ADNL keys and archive routing work is covered in the TON Liteserver guide.
Mempool stream
Pending messages are not exposed through this MCP server — none of the tools above read the mempool. TONNode offers the mempool as a separate WebSocket feed at wss://mempool.tonnode.io/v1/stream: one JSON object per external message as TONNode's node receives it from the public overlay, before it lands in a block, with filters by destination wallet, op code or DEX pool and a short replay after a reconnect. Plans are priced by the number of simultaneous connections on one key. Coverage is partial — the node sees only what reaches it over the overlay, and no completeness or speed figures are promised — and messages sent through TONNode's liteservers usually do not appear in it (the node does not publish its own broadcasts; a copy relayed back by other nodes showed up for 2 of 20 sends in a test on 8 October 2026). Protocol, keys and plans: tonnode.io/en/docs/mempool.
License
MIT © TONNode
Pertanyaan tentang TON MCP
Bagaimana cara menambahkan TON MCP ke Claude Code?
Jalankan claude mcp add mcp -- npx -y @tonnode/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan TON MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan TON MCP?
Server ini menyediakan 16 tool, termasuk get_balance, get_jetton_balance, get_jetton_info, get_transactions, get_account_state.
Apa yang bisa dilakukan AI agent dengan TON MCP server ini?
Agent dapat melakukan query ke TON liteservers untuk mengecek saldo GRAM dan jetton, status akun, riwayat transaksi, contract get-methods, serta mendapatkan swap quotes untuk menyusun unsigned transactions.
Apakah server ini melakukan signing atau broadcast transaksi swap?
Tidak. Server hanya mengembalikan pesan unsigned yang sudah siap untuk TonConnect; proses signing dan pengiriman tetap dilakukan oleh pemilik wallet.
Bagaimana cara menghubungkan Claude Desktop atau Cursor ke server ini?
Tambahkan server ke config MCP client Anda menggunakan npx -y @tonnode/mcp; secara default, server akan terhubung ke TON mainnet melalui public global config.
Bagaimana autentikasi pada mode hosted HTTP?
Menggunakan Bearer API keys yang dikirim melalui header Authorization atau X-API-Key, lengkap dengan rate limiting untuk setiap key.
Wallet jenis apa yang bisa dibuat melalui generate_wallet?
Server dapat menghasilkan mnemonic 24 kata, ed25519 keypair, dan address untuk versi contract v4, v3r2, v5r1, atau highload_v3.