Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOME | No | Home directory (fallback for CACHE_DIR) | |
| CACHE_DIR | No | Directory for storing local data | ~/.hyperlane-mcp |
| PRIVATE_KEY | Yes | Private key for signing transactions (without 0x prefix) | |
| GITHUB_TOKEN | Yes | GitHub Personal Access Token for accessing Hyperlane registry |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cross-chain-message-transfer | Transfers a cross-chain message. |
| cross-chain-asset-transfer | Transfers tokens/assets between multiple blockchain networks using Hyperlane's cross-chain infrastructure. FUNCTIONALITY: • Moves tokens from one blockchain to another (e.g., USDC from Ethereum to Polygon) • Supports sequential transfers across multiple chains in a single operation • Handles various token types including native tokens, ERC20 tokens, and synthetic tokens PREREQUISITES:
• A warp route must exist for the specified token symbol and chain combination
• If no warp route exists, deploy one first using the PARAMETERS: • symbol: The token identifier (e.g., "USDC", "ETH", "WBTC") • chains: Array of blockchain names in transfer order (e.g., ["ethereum", "polygon", "arbitrum"]) • amount: Token amount in wei or smallest token units (e.g., "1000000" for 1 USDC with 6 decimals) • recipient: Destination wallet address (defaults to sender if not specified) OUTPUT: • Returns transaction hashes and message IDs for each cross-chain transfer • Each transfer between adjacent chains generates one transaction • Use message IDs to track delivery status across chains EXAMPLE USE CASES: • Bridge USDC from Ethereum to Polygon • Multi-hop transfer: ETH from Ethereum → Arbitrum → Base • Cross-chain token arbitrage or yield farming |
| deploy-warp-route | Deploys a warp route. |
| deploy-chain | Deploys a new chain to the Hyperlane network. |
| run-validator | Runs a validator for a specific chain. |
| run-relayer | Runs a relayer for specified chains. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |