Permet aux clients IA d'interroger directement les liteservers TON pour consulter les soldes, l'état des comptes, les transactions, les get-methods et de construire des swaps non signés.
Aussi connu sous tonnode/mcp, mcp, @tonnode/mcp
- Étoiles
- 20
- Outils
- 16
- Téléchargements, 30 jours
- —
- Dernière version
- 0.9.2
- Dernier commit
- 8 oct. 2026
- Licence
- MIT
Qu'est-ce que TON MCP ?
TON est un serveur MCP. Permet aux clients IA d'interroger directement les liteservers TON pour consulter les soldes, l'état des comptes, les transactions, les get-methods et de construire des swaps non signés. Il expose 16 outils, comme get_balance, get_jetton_balance, get_jetton_info.
Résumé généré à partir du README du projet
À propos du MCP server TON
Ce serveur permet d'interroger directement la blockchain TON depuis des agents IA. En offrant un accès direct aux liteservers via le protocole natif ADNL, il contourne les passerelles HTTP traditionnelles pour récupérer les états de compte, l'historique des transactions et les soldes de jettons. Les développeurs peuvent intégrer cela dans des clients comme Claude Desktop, Cursor ou ChatGPT en utilisant une simple commande npx pour un usage local, ou via un endpoint HTTP hébergé pour des déploiements distants.
Au-delà de la simple récupération de données, le serveur permet aux agents d'agir comme des traders. Il prend en charge la construction de transactions de swap non signées pour le GRAM et divers jettons via le protocole Omniston, ainsi que la gestion de swaps cross-chain complexes impliquant des réseaux comme Ethereum, Arbitrum et Avalanche. Il inclut également des outils pour générer de nouveaux portefeuilles avec des versions de contrat spécifiques comme v4 ou highload_v3. Pour ceux qui utilisent une version hébergée, le serveur gère l'authentification via des clés Bearer et propose une limitation de débit granulaire pour garantir des performances stables.
Ce que vous pouvez faire avec
- 1Vérifier les soldes des portefeuillesUn agent IA peut déterminer les avoirs actuels en GRAM ou USDT d'une adresse spécifique.
- 2Préparer des swaps décentralisésUn développeur peut demander à une IA de générer une transaction non signée pour un échange de jetons, prête à être signée par un portefeuille.
- 3Exécuter des transactions cross-chainUn agent peut gérer le cycle de vie d'un trade déplaçant des actifs de TON vers des réseaux comme Polygon ou Base.
- 4Créer de nouvelles identitésVous pouvez ordonner à une IA de générer un nouveau portefeuille avec une phrase mnémotechnique de 24 mots et une version de contrat spécifique.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer TON MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller TON MCP dans Claude Code
$ claude mcp add mcp -- npx -y @tonnode/mcpInstaller TON MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@tonnode/mcp"
]
}
}
}Installer TON MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@tonnode/mcp"
]
}
}
}Installer TON MCP dans VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@tonnode/mcp"]}'Installer TON MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@tonnode/mcp"
]
}
}
}Installer TON MCP dans Codex
$ codex mcp add mcp -- npx -y @tonnode/mcpInstaller TON MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@tonnode/mcp"]
Installer TON MCP dans Gemini CLI
$ gemini mcp add -s user mcp npx -- -y @tonnode/mcpInstaller TON MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@tonnode/mcp"
]
}
}
}Outils MCP TON 16
Détectés depuis le 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 | — |
Afficher les 16 outilsAfficher moins d'outils
track_crosschain_swapdisclose_crosschain_secretbuild_crosschain_refundgenerate_wallet
| track_crosschain_swap | — | |
| disclose_crosschain_secret | — | |
| build_crosschain_refund | — | |
| generate_wallet | — |
Configuration
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.
| Nom | Description | Type |
|---|---|---|
| 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. |
Vérifications automatisées
Exécuté le 13 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibleRéussi
- Licence open source (OSI)Réussi
- Commit ou version publiée au cours de l'année écouléeRéussi
- Nom du package non proche d'un package populaireRéussi
- L'endpoint distant utilise HTTPSRéussi
- Les outils destructifs sont étiquetésRéussi
- Aucune instruction cachée destinée au modèleRéussi
- Aucun avis critique dans le package ou ses dépendancesRéussi
README
Voir sur 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
Questions sur TON MCP
Comment ajouter TON MCP à Claude Code ?
Exécutez claude mcp add mcp -- npx -y @tonnode/mcp dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter TON MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Quels outils TON MCP fournit-il ?
Il expose 16 outils, dont get_balance, get_jetton_balance, get_jetton_info, get_transactions, get_account_state.
Que peut faire un agent IA avec le MCP server TON ?
Il peut interroger les liteservers TON pour obtenir les soldes en GRAM et jettons, l'état des comptes, l'historique des transactions et les get-methods de contrats, ainsi que des devis de swap pour construire des transactions non signées.
Le serveur signe-t-il ou diffuse-t-il les transactions de swap ?
Non. Il renvoie des messages non signés, prêts pour TonConnect ; la signature et l'envoi restent à la charge du propriétaire du portefeuille.
Comment connecter Claude Desktop ou Cursor à ce serveur ?
Ajoutez le serveur à la configuration de votre client MCP avec npx -y @tonnode/mcp ; il se connecte au mainnet TON via la configuration globale publique par défaut.
Comment le mode hosted HTTP est-il authentifié ?
Il utilise des clés API Bearer transmises via les en-têtes Authorization ou X-API-Key, avec une limitation de débit par clé.
Quels portefeuilles la commande generate_wallet peut-elle créer ?
Elle génère une phrase mnémotechnique de 24 mots, une paire de clés ed25519 et une adresse pour les versions de contrat v4, v3r2, v5r1 ou highload_v3.