Meson Cross Chain Transfer

🚀 Meson Cross-chain Transaction MCP Server

A Meson cross-chain transaction MCP (Model Context Protocol) server developed based on Deno and TypeScript, which helps users conveniently transfer assets between different blockchains.

🚀 Quick Start

This server is designed to simplify the process of transferring assets across different blockchains. It offers a user - friendly experience with a comprehensive set of features and easy - to - follow setup steps.

✨ Features

• Cross - chain asset transfer based on the Meson Protocol.
• A conversational cross - chain transaction experience achieved through the MCP standard.
• Comprehensive integration of the cross - chain transaction process: transaction preparation, signature submission, and status query.
• Support for both mainnet and testnet environments.
• Secure configuration of private keys using environment variables.
• Runs on the Deno runtime, eliminating the need for complex dependency configurations.

📦 Installation

Dependencies

• Deno version 1.37.0 or higher.
• An Ethereum - compatible private key (for transaction signing).

Steps

1. Clone the repository

git clone <repository-url>
cd meson-mcp

2. Set environment variables

# Linux/MacOS
export MESON_PRIVATE_KEY=your_private_key

# Windows
set MESON_PRIVATE_KEY=your_private_key

3. Run the MCP server

deno run --allow-net --allow-env main.ts

📚 Documentation

MCP Configuration Guide

You can use Meson's cross - chain transaction MCP service by adding the following configuration to your MCP configuration file:

"meson_mcp": {
  "command": "npx",
  "args": [
    "deno",
    "run",
    "--allow-env",
    "--allow-net",
    "--allow-read",
    "jsr:@demcp/meson-mcp"
  ],
  "env": {
    "MESON_PRIVATE_KEY": "0x1234567890abcdef",
    "MESON_USE_MAINNET": "true"
  }
}

Configuration Parameters

Main Functional Modules

💻 Usage Examples

Basic Usage

The main functions of the server are divided into three parts: transaction preparation, signature submission, and status query.

// Transaction Preparation
async function prepareTransaction(data: any): Promise<void> {
    // The specific implementation depends on the Meson API
}

// Signature Submission
async function signAndSubmit(signedData: any): Promise<boolean> {
    try {
        const result = await mesonSdk.submitTransaction(signedData);
        return result.success;
    } catch (error) {
        console.error("Signature submission failed:", error);
        return false;
    }
}

// Status Query
async function checkStatus(transactionId: string): Promise<TransactionStatus> {
    const status = await mesonSdk.getTransactionStatus(transactionId);
    return {
        id: status.id,
        status: status.status,
        timestamp: status.timestamp
    };
}

🔧 Technical Details

• Developed based on the Model Context Protocol.
• Using Deno as the runtime environment.
• Conducting cross - chain transactions through the Meson API.
• Converting private keys to Address using ethers.

Important Notes

⚠️ Important Note

• Mainnet transactions involve real assets. Please carefully check the transaction details.
• The testnet is a safe testing environment. New users are recommended to operate on the testnet first.
• Ensure that the private key has enough .native tokens (e.g., ETH) to pay for transaction fees.

Supported Chains and Tokens

This MCP server supports all chains and tokens supported by the Meson Protocol, including but not limited to:

• Ethereum and its testnets
• Arbitrum
• Avalanche
• BSC
• Optimism
• Polygon
• Solana
• And other EVM and non - EVM chains

For a specific list of supported chains and tokens, please refer to the Meson official documentation.

📄 License

This project is licensed under the MIT license.