Provides tools for cross-chain bridging and swapping assets on Ethereum, including chain and token support discovery, fee estimation, and transaction data generation for AI agents.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Relay MCP ServerBridge 0.1 ETH from Ethereum to Base"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Relay MCP Server
A Model Context Protocol server for Relay Protocol — cross-chain bridge and swap tools for AI agents.
Tools
Tool | Description |
| List supported blockchain networks |
| Search for tokens across chains |
| Quote for bridging same token across chains |
| Quote for swapping between different tokens |
| Fee breakdown for a bridge or swap |
| Get unsigned transaction data for execution |
| Check status of a relay transaction |
| Past transactions for a wallet |
| Deep link to the Relay web app with pre-filled parameters |
Usage
Claude Desktop / Claude Code
{
"mcpServers": {
"relay": {
"command": "npx",
"args": ["-y", "@relayprotocol/relay-mcp"]
}
}
}Run from source
npm install
npm run build
npm startEnvironment variables
Variable | Default | Description |
|
| Relay API base URL |
| — | Optional API key for higher rate limits |
Architecture
Transport: Stdio (MCP spec)
Runtime: Node.js
API: Direct HTTP calls to
api.relay.link(no SDK dependency)Signing: The server returns unsigned transactions. Your agent's wallet infrastructure (Privy, Dynamic, Turnkey, etc.) handles signing and broadcasting.
Agent flow example
User: "Bridge 0.1 ETH from Ethereum to Base"
1. Agent calls get_supported_chains → resolves Ethereum=1, Base=8453
2. Agent calls get_bridge_quote → gets quote with fees and ETA
3. Agent shows user the quote for confirmation
4. Agent calls execute_bridge → gets unsigned transaction + requestId
5. Agent signs and broadcasts tx via wallet infrastructure
6. Agent calls get_transaction_status(requestId) → polls until success
7. Agent confirms completion to userLicense
MIT