iz-tolk-mcp — Tolk Compiler for TON

io.github.izzzzziPublished by GitHub account izzzzziv1.2.1Updated Oct 24, 2026

Tolk smart contract compiler for TON — compile, check, and deploy from AI assistants

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

Local MCP server that brings the Tolk smart contract compiler for the TON blockchain into an AI assistant for compiling, checking and preparing deployment.

What you can do
  • Compile Tolk smart contract sources, including multi-file projects, and get Fift output, BoC, code hash and compiler version
  • Check Tolk code for syntax and type errors without full compilation output
  • Read the bundled compiler version
  • Generate TON deployment deeplinks and Tonkeeper links with a computed contract address
  • Read bundled Tolk documentation and example contracts, and use guided prompts for writing, reviewing and debugging contracts
When to use it
Useful when developing TON smart contracts in Tolk and you want the assistant to compile, lint and iterate on code inside the conversation, or to produce a wallet deployment link for a compiled contract.
Requirements
Runs locally over stdio via npx (or a global npm install), requiring Node.js 18 or newer. No accounts, API keys or environment variables are declared; the compiler is bundled as WASM and runs locally.
Before you install
Deployment links carry a deploy amount in nanoTON (default 0.05 TON) and are meant to be opened in a wallet, so check the amount, workchain and address before confirming any on-chain deployment. Compilation and checking only process code you supply.

Installation

In SourceWeft

  1. Open iz-tolk-mcp — Tolk Compiler for TON in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

iz-tolk-mcp

MCP server for the Tolk smart contract compiler — compile, check, and deploy TON blockchain smart contracts from any AI assistant

[CI] [npm version] [npm downloads] [License: MIT] [TypeScript] [Node.js]

🇷🇺 Русский | 🇬🇧 English


MCP server that brings the Tolk smart contract compiler directly into AI assistants like Claude — write, compile, check, and deploy TON contracts without leaving the conversation.


📖 Overview

iz-tolk-mcp is a Model Context Protocol (MCP) server that integrates the Tolk smart contract compiler into AI assistants, enabling a seamless write-compile-deploy workflow for TON blockchain development.

  • Tolk is the next-generation smart contract language for the TON blockchain, designed as a modern successor to FunC with familiar syntax (C/TypeScript-like), type safety, and cleaner semantics.
  • MCP (Model Context Protocol) is an open standard that lets AI assistants use external tools, access data sources, and follow guided workflows — turning them into capable development environments.

✨ Features

FeatureDescription
🔨 4 MCP Toolscompile_tolk, check_tolk_syntax, get_compiler_version, generate_deploy_link
📄 6 MCP ResourcesLanguage guide, stdlib reference, changelog, FunC migration guide, example contracts
💬 3 MCP PromptsGuided workflows for writing, reviewing, and debugging smart contracts
⚙️ Full Compiler OptionsOptimization levels (0-2), stack comments, path mappings, multi-file compilation
📦 Multi-file SupportCompile projects with multiple .tolk source files, @stdlib/* and @fiftlib/* imports
🔗 Deployment LinksGenerate ton:// deeplinks and Tonkeeper URLs for wallet deployment
🚀 Zero ConfigurationRuns via npx with no external dependencies beyond Node.js

🚀 Quick Start

bash
npx iz-tolk-mcp

The server communicates over stdio and is designed to be launched by an MCP client.


📦 Installation

Using npx (no install needed)

MCP clients launch the server automatically — just add it to your configuration (see below).

Global install

bash
npm install -g iz-tolk-mcp

From source

bash
git clone https://github.com/izzzzzi/izTolkMcp.gitcd izTolkMcpnpm installnpm run build

Requirement: Node.js >= 18


🔧 MCP Client Configuration

Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "tolk": {      "command": "npx",      "args": ["-y", "iz-tolk-mcp"]    }  }}
Claude Code
bash
claude mcp add tolk -- npx -y iz-tolk-mcp
Cursor

Add to .cursor/mcp.json:

json
{  "mcpServers": {    "tolk": {      "command": "npx",      "args": ["-y", "iz-tolk-mcp"]    }  }}
Windsurf

Add to ~/.windsurf/mcp.json:

json
{  "mcpServers": {    "tolk": {      "command": "npx",      "args": ["-y", "iz-tolk-mcp"]    }  }}
VS Code (Copilot)

Add to .vscode/mcp.json:

json
{  "servers": {    "tolk": {      "command": "npx",      "args": ["-y", "iz-tolk-mcp"]    }  }}
Local build (any client)
json
{  "mcpServers": {    "tolk": {      "command": "node",      "args": ["/absolute/path/to/izTolkMcp/dist/cli.js"]    }  }}

🛠️ MCP Tools

🔍 get_compiler_version

Returns the version of the Tolk compiler bundled in @ton/tolk-js (WASM).

ParameterTypeRequiredDescription
(none)——No parameters

🔨 compile_tolk

Compiles Tolk smart contract source code. Returns Fift output, BoC (Bag of Cells) in base64, code hash, and compiler version.

ParameterTypeRequiredDescription
entrypointFileNamestring✅The main .tolk file to compile (e.g., "main.tolk")
sourcesobject✅Map of filename -> source code. Must include the entrypoint file.
optimizationLevelnumber—Optimization level 0-2 (default: 2)
withStackCommentsboolean—Include stack layout comments in Fift output
pathMappingsobject—Maps @alias prefixes to folder paths for import resolution

✅ check_tolk_syntax

Checks Tolk source code for syntax and type errors without returning full compilation output. Faster feedback loop for iterative development.

ParameterTypeRequiredDescription
entrypointFileNamestring✅The main .tolk file to check
sourcesobject✅Map of filename -> source code
pathMappingsobject—Maps @alias prefixes to folder paths for import resolution

🔗 generate_deploy_link

Generates TON deployment deeplinks for a compiled contract. Computes the deterministic contract address and returns ton:// and Tonkeeper links ready for wallet deployment.

ParameterTypeRequiredDescription
codeBoc64string✅Base64-encoded BoC of compiled contract code (from compile_tolk)
initialDataBoc64string—Base64-encoded BoC for initial data cell (default: empty cell)
workchainnumber—Target workchain ID (default: 0)
amountstring—Deploy amount in nanoTON (default: "50000000" = 0.05 TON)

📄 MCP Resources

ResourceURIDescription
📘 language-guidetolk://docs/language-guideComplete Tolk language syntax reference
📗 stdlib-referencetolk://docs/stdlib-referenceStandard library modules and functions reference
📋 changelogtolk://docs/changelogTolk compiler version history from v0.6 to latest
🔄 tolk-vs-functolk://docs/tolk-vs-funcFunC to Tolk migration guide — key differences and comparison
📝 example-countertolk://examples/counterSimple counter smart contract example in Tolk
💎 example-jettontolk://examples/jettonJetton (fungible token) minter contract example in Tolk

💬 MCP Prompts

write_smart_contract

Guided workflow for writing a new Tolk smart contract on TON. Injects the language reference and a relevant example contract into the conversation context.

ArgumentTypeRequiredDescription
descriptionstring✅Description of what the smart contract should do
contractTypestring—"counter" | "jetton" | "nft" | "wallet" | "custom" (default: "custom")

review_smart_contract

Security-focused review of a Tolk smart contract. Checks for access control, message handling, integer overflow, gas management, storage integrity, and TON-specific vulnerabilities.

ArgumentTypeRequiredDescription
codestring✅The Tolk smart contract source code to review

debug_compilation_error

Diagnose and fix a Tolk compilation error. Analyzes the error against the language reference and provides corrected code.

ArgumentTypeRequiredDescription
errorMessagestring✅The compilation error message from the Tolk compiler
codestring✅The Tolk source code that failed to compile

💡 Usage Examples

Once configured, interact with the Tolk MCP server through natural language in your AI assistant:

Compile a contract:

"Compile this Tolk smart contract:"

tolk
import "@stdlib/tvm-dicts";
fun onInternalMessage(myBalance: int, msgValue: int, msgFull: cell, msgBody: slice) {    // handle messages}

Write a new contract from scratch:

"Write a simple counter contract for TON that stores a number and lets anyone increment it. Include a getter to read the current value."

Review an existing contract:

"Review this contract for security issues" (paste code)

Debug a compilation error:

"I'm getting this error when compiling: unexpected token 'fun' — here's my code:" (paste code)

Generate a deploy link:

"Generate a deployment link for the contract we just compiled."


📁 Project Structure

src/├── index.ts        — Server initialization and stdio transport├── tools.ts        — 4 MCP tools (compile, check, version, deploy)├── resources.ts    — 6 MCP resources (docs, examples)├── prompts.ts      — 3 MCP prompts (write, review, debug)└── content/        — Bundled documentation and example contracts    ├── language-guide.md    ├── stdlib-reference.md    ├── changelog.md    ├── tolk-vs-func.md    ├── example-counter.tolk    └── example-jetton.tolk

Key dependencies:

  • @modelcontextprotocol/sdk — MCP server framework
  • @ton/tolk-js — Tolk compiler (WASM, runs locally)
  • @ton/core — TON primitives for address computation and cell serialization
  • zod — Schema validation for tool parameters

🧑‍💻 Development

bash
npm install          # Install dependenciesnpm run build        # Compile TypeScript + copy content filesnpm run dev          # Run with tsx (hot reload for development)npm test             # Run test suite (vitest)npm run lint         # Check for lint errorsnpm run lint:fix     # Fix lint errors automaticallynpm run format       # Format code with Biome

Pre-commit hooks enforce code quality automatically:

  • Biome — fast linter and formatter for TypeScript
  • Husky — Git hooks manager
  • lint-staged — runs checks only on staged files

Source: README.md at commit e5b016e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts