deploy-chainLABSCO SUMMARY
It signs real transactions with the key you give it.
Deploying core contracts and transferring assets both spend gas from the private key in the config, so this belongs on a key funded for the purpose and not on your main one. What it buys you is sequencing: deploy, bring up the validator and relayer, and send the first message as one continuous thread instead of a series of CLI invocations you have to get in the right order.
What it is
An MCP server over Hyperlane's cross-chain infrastructure. It keeps a local registry of chain metadata, deployed contracts and warp route configuration, deploys core contracts, and runs validators and relayers as Docker containers so each stays isolated.
What you get
deploy-chain— deploy Hyperlane core contracts to a new chainrun-validatorandrun-relayer— start the two pieces that make messages verifiable and deliverable, each in its own Docker containercross-chain-message-transfer— send a message from one chain to anotherdeploy-warp-routeandcross-chain-asset-transfer— stand up a route for asset transfers, then move tokens over it, including multi-hop- Warp route configuration readable as a resource under the URI pattern
hyperlane-warp:///{symbol}/{/chain*} - Connections to several networks at once through Hyperlane's MultiProvider
Requirements
A private key with enough native tokens to pay gas on every chain you touch, supplied as PRIVATE_KEY without the 0x prefix, and a GitHub personal access token as GITHUB_TOKEN for registry access. Docker must be running, since validators and relayers are containers. Node.js v18 or higher and pnpm; clone the repository, pnpm install, pnpm build, and point the client at build/index.js. CACHE_DIR moves the local registry off its default of ~/.hyperlane-mcp. You also need RPC endpoints for the chains involved.
Setup effort
Build from source — git clone https://github.com/Suryansh-23/hyperlane-mcp.git
USE CASES
01
Bringing Hyperlane up on a chain it does not support yet
Deploy the core contracts, then start the validator and relayer for that chain in the same session.
02
Proving a cross-chain path works
Send a message between the two chains and watch it get verified and delivered before building on top of it.
03
Moving a token between chains
Deploy a warp route for the asset, then transfer over it — including a multi-hop path.
04
Checking how a route is configured
Read the warp route config as a resource by symbol and chain instead of digging through the registry files.
6 tools
Listed in project docs. Your client may show a different list.
run-validatorrun-relayercross-chain-message-transfercross-chain-asset-transferdeploy-warp-routeBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- Node.js v18 or later
- PRIVATE_KEY in your environment
- GITHUB_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/Suryansh-23/hyperlane-mcp.git
cd hyperlane-mcp
npm install -g pnpm
pnpm install
pnpm build
node build/index.jsMCP Clients
Claude Desktop, Any MCP client
JSON
{
"mcpServers": {
"hyperlane": {
"command": "node",
"args": [
"<YOUR_PATH_TO_HYPERLANE_MCP>/build/index.js"
],
"env": {
"PRIVATE_KEY": "<YOUR_PRIVATE_KEY>",
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>",
"CACHE_DIR": "<YOUR_CACHE_DIR>"
}
}
}
}
