- Explore MCP Servers
- meson_mcp
Meson Mcp
What is Meson Mcp
Meson_mcp is a cross-chain transaction MCP (Model Context Protocol) server built with Deno and TypeScript, designed to facilitate the transfer of assets across different blockchains conveniently.
Use cases
Use cases include transferring tokens between Ethereum and other blockchains, enabling liquidity pools that span multiple chains, and facilitating cross-chain decentralized applications (dApps) that require asset interoperability.
How to use
To use meson_mcp, clone the repository, set the required environment variables for your private key, and run the MCP server using Deno. The server provides tools for preparing, signing, and executing cross-chain transactions.
Key features
Key features include cross-chain asset transfer based on the Meson Protocol, a conversational transaction experience using the MCP standard, complete integration of the transaction process, support for both mainnet and testnet environments, and secure private key configuration through environment variables.
Where to use
Meson_mcp can be used in various fields such as decentralized finance (DeFi), cross-chain asset trading platforms, and any application requiring seamless asset transfers between different blockchain networks.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Overview
What is Meson Mcp
Meson_mcp is a cross-chain transaction MCP (Model Context Protocol) server built with Deno and TypeScript, designed to facilitate the transfer of assets across different blockchains conveniently.
Use cases
Use cases include transferring tokens between Ethereum and other blockchains, enabling liquidity pools that span multiple chains, and facilitating cross-chain decentralized applications (dApps) that require asset interoperability.
How to use
To use meson_mcp, clone the repository, set the required environment variables for your private key, and run the MCP server using Deno. The server provides tools for preparing, signing, and executing cross-chain transactions.
Key features
Key features include cross-chain asset transfer based on the Meson Protocol, a conversational transaction experience using the MCP standard, complete integration of the transaction process, support for both mainnet and testnet environments, and secure private key configuration through environment variables.
Where to use
Meson_mcp can be used in various fields such as decentralized finance (DeFi), cross-chain asset trading platforms, and any application requiring seamless asset transfers between different blockchain networks.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Content
Meson Cross-Chain Transaction MCP Server
A Meson cross-chain transaction MCP (Model Context Protocol) server implemented with Deno and TypeScript, helping users transfer assets conveniently between different blockchains.
Features
- Cross-chain asset transfer based on Meson Protocol
- Conversational cross-chain transaction experience using MCP standard
- Integration of complete cross-chain transaction process: transaction preparation, signature submission, status query
- Support for mainnet and testnet environments
- Private key configuration using environment variables for security
- Based on Deno runtime, no complex dependency configuration required
Requirements
- Deno 1.37.0 or higher
- Ethereum compatible private key (for transaction signing)
Installation and Running
- Clone the repository
git clone <repository-url>
cd meson-mcp
- Set environment variables
# Linux/MacOS
export MESON_PRIVATE_KEY=your_private_key
# Windows
set MESON_PRIVATE_KEY=your_private_key
- Run the MCP server
deno run --allow-net --allow-env main.ts
Main Functions
The MCP server provides three core tools:
1. Prepare Cross-Chain Transaction (prepareSwap)
Prepares a cross-chain transaction and generates data for signing.
Parameters:
fromChain: Source chain IDtoChain: Destination chain IDfromToken: Source token symboltoToken: Destination token symbolamount: Swap amountfromAddress: Sender addressrecipient: Recipient address (optional, defaults to sender)
Returns:
- Price information
- Encoded transaction data
- Data to be signed
2. Sign and Execute Transaction (executeSwap)
Signs the transaction data and submits it to the Meson network.
Parameters:
encoded: Encoded transaction datasigningRequest: Data to be signed (containing message and hash)fromAddress: Sender addressrecipient: Recipient address
Returns:
- Transaction ID
- Transaction result information
3. Query Transaction Status (checkSwapStatus)
Checks the status of a submitted transaction.
Parameters:
swapId: Transaction ID
Returns:
- Transaction status
- Detailed information
Usage Example
Here’s a complete cross-chain transaction flow example:
- Set environment (testnet/mainnet)
I want to perform a cross-chain transaction on testnet
- Prepare cross-chain transaction
Please prepare a transaction from Ethereum Sepolia testnet to transfer 10 USDC to Arbitrum Sepolia, my address is 0x1234...abcd
- Sign and execute transaction
Please sign and submit the transaction prepared above
- Query transaction status
Please check the status of the transaction I just submitted
Important Notes
- Private keys are only stored in environment variables and will not be sent to any external services
- Transaction signing is completed locally, and signed data is submitted through the Meson API
- Mainnet transactions involve real assets, please be sure to verify transaction details
- Testnet is a safe testing environment, new users are recommended to try on testnet first
- Ensure the private key has enough native tokens (ETH, etc.) to pay for transaction fees
Supported Chains and Tokens
This MCP server supports all blockchains and tokens supported by the Meson protocol, including but not limited to:
- Ethereum and its testnets
- Arbitrum
- Avalanche
- BSC
- Optimism
- Polygon
- Solana
- And many other EVM and non-EVM chains
For specific supported chains and tokens, please refer to the Meson official documentation.
Technical Details
- Implemented based on Model Context Protocol
- Using Deno as the runtime environment
- Cross-chain transactions through Meson API
- Transaction signing using ethers library
License
MIT
Dev Tools Supporting MCP
The following are the main code editors that support the Model Context Protocol. Click the link to visit the official website for more information.










