Meson Cross-Chain Transaction

Provides cross-chain asset transfers via Meson Protocol with MCP-style prepare, sign, and status query workflows.

typescript

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

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

You can transfer assets across different blockchains with the Meson MCP Server. Built on Deno and TypeScript, it guides you through cross-chain preparation, signing, and status checks using the MCP standard, enabling secure, private key-backed operations in both mainnet and testnet environments.

How to use

You will interact with three core MCP functions from your MCP client: prepareSwap to assemble and return data for signing, executeSwap to sign and submit the transaction to the Meson network, and checkSwapStatus to monitor the outcome. Use them in sequence to perform a cross-chain transfer: prepare data, sign and submit, then poll for the final status.

How to install

Prerequisites: ensure you have Deno installed (version 1.37.0 or higher) and an Ethereum-compatible private key for signing.

Clone the MCP server package and enter its directory.
Set your private key as an environment variable.
Run the MCP server with network and environment access authorized.

Configuration and runtime

"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"
  }
}

Security and environment

Private keys are stored in environment variables and never sent to external services. Signing happens locally and only signed data is transmitted through the MCP interface. In production, manage private keys securely and avoid exposing them.

Tools and endpoints

The MCP server exposes three primary tools for cross-chain transactions: prepareSwap, executeSwap, and checkSwapStatus. These tools enable you to prepare data for signing, submit the signed transaction, and query the transaction status respectively.

Notes on usage

Choose testnet for experimentation to minimize risk. Ensure your private key has enough native tokens to cover transaction fees on the chosen network.

Supported flows

The server supports a complete cross-chain transaction flow: prepareCrossChain, sign and execute, then monitor the resulting swap status. All steps are performed through the MCP protocol with local signing to protect your keys.

Example environment variables

MESON_PRIVATE_KEY: Your Ethereum-compatible private key used for signing MESON_USE_MAINNET: "true" to target the mainnet, or omit/set to "false" for testnet

Available tools

prepareSwap

Prepares a cross-chain transaction and generates data for signing, including price information and encoded transaction data.

executeSwap

Signs the prepared transaction data and submits it to the Meson network, returning the transaction ID and result.

checkSwapStatus

Queries the status of a previously submitted cross-chain transaction to provide detailed status information.

Built by

VeilStrat

AI signals for GTM teams