ton

This MCP server exposes a Ton wallet integration via the Ton MCP (Model Context Protocol) interface. It allows you to interact with a Ton wallet to perform operations such as sending transactions and querying balances, among other wallet-related actions supported by the Ton MCP backend. Once running, you can use your MCP-enabled application or tools to issue requests to the ton-mcp server, leveraging the standardized MCP endpoints to execute wallet operations, receive transaction results, and fetch account state. The server is configured to run with Bun and uses a LOG_LEVEL environment variable to control verbosity.

To use the server, start it with the provided command (bun run start) and ensure the environment variable LOG_LEVEL is set to your desired debugging level. Your MCP-enabled client can then communicate with the ton-mcp server through the MCP API surface, invoking wallet actions like sending transactions, retrieving balances, and querying transaction history according to the MCP protocol guidelines.

Prerequisites:

• Node-like runtime Bun installed on your system (https://bun.sh/)
• Access to the Ton MCP server repository (ton-mcp)

Installation steps:

1. Install Bun if you haven’t already:

curl -fsSL https://bun.sh/install | bash

2. Clone the repository (ton-mcp) to your environment:

git clone https://github.com/your-org/ton-mcp.git
cd ton-mcp

3. Install dependencies if needed (Bun will handle dependencies defined in package.json or bunfig.toml).

bun install

4. Run the MCP server:

LOG_LEVEL=3 bun run start

5. Confirm the server is listening and accepting MCP requests, then integrate your MCP-enabled client against the ton-mcp server endpoint as defined by your MCP environment.

Tips and notes:

• The server uses Bun; ensure Bun is installed and available in your PATH.
• The LOG_LEVEL environment variable controls logging verbosity; set to a higher value for more detailed output during debugging.
• Ensure your MCP client adheres to the MCP protocol when constructing requests to the ton-mcp server (wallet operations like sendTransaction, getBalance, etc.).
• If you encounter issues, check server logs for startup errors, network binding problems, or missing environment configurations.
• The configuration example uses the server name ton-mcp; you can rename it in your mcpServers configuration as needed, but keep the command and arguments consistent with how you start the server.