Relay Protocol

You can run the Relay Protocol MCP Server locally or in the cloud to enable cross-chain bridging, multi-chain swaps, real-time pricing, and token discovery via the MCP client. This guide walks you through practical usage, installation steps, configuration options, and common tips to get you up and running quickly.

How to use

Set up the server in a way that fits your workflow: run it locally for development or deploy it to a cloud provider for production access. You’ll configure an MCP client to connect either through a local stdio transport (for direct CLI/Claude Desktop integration) or through a cloud HTTP transport (via a deployment URL). Once connected, you can explore supported chains and tokens, request quotes for bridging and swaps, monitor execution status, and retrieve pricing and transaction data across 50+ networks and 1000+ tokens.

How to install

Prerequisites you need before installation are Node.js (version 20 or newer) and the pnpm package manager.

Install dependencies and build the server locally with these commands in order:

pnpm install
pnpm build

Run the development server during Local/Claude Desktop development:

pnpm dev

Run the production server locally:

pnpm start

For cloud deployment using SSE transport, build the server and start the SSE service. This uses the PORT environment variable or defaults to 3000 and supports cloud hosting platforms like Railway, Heroku, and Render. Use these commands to prepare and run in a cloud environment:

pnpm build
pnpm start:sse

pnpm dev:sse

MCP connecting configurations

You can connect your MCP client in two ways: a local stdio transport for Claude Desktop integration, or a cloud HTTP transport for remote access.

Local stdio transport configuration example (Claude Desktop) shows how to launch the local MCP server and connect via a path to the built dist index file.

Cloud HTTP transport configuration example uses a deployment URL you obtain from your cloud provider after deployment.

Configuration examples

Two common connection configurations are shown here. The HTTP method connects to a remote server, while the stdio method runs a local server process.

Common usage notes

• The server exposes 50+ blockchain networks and 1000+ tokens for cross-chain bridging and pricing. - No API keys are required for the public API. - Type-safe, with full TypeScript support and validation to help catch errors at compile time.

Troubleshooting

If you encounter issues during startup or while connecting the MCP client, verify that your environment satisfies Node.js 20.0.0 or newer and that you have completed the build step before starting the server. Check for syntax errors in configuration and ensure the cloud URL is reachable when using the HTTP transport.

Notes

This MCP server provides a robust set of capabilities for cross-chain actions, including bridging, multi-chain swaps, real-time pricing, request monitoring, and currency discovery across a wide range of networks and tokens.

Available tools

relay_get_chains

List supported blockchain networks across the Relay Protocol MCP Server, enabling you to see which chains are available for bridging and pricing.

relay_get_token_price

Fetch real-time token prices across all supported chains, helping you compare values and determine cost-efficient routes.

relay_get_currencies

Discover tokens with advanced filtering, including verified status and bridging support.

relay_get_quote

Generate quotes for bridging or swapping tokens between chains, enabling you to estimate costs and execution details.

relay_swap_multi_input

Execute multi-chain swaps by aggregating inputs from multiple chains into a single destination token.

relay_get_execution_status

Track the progress and results of a bridging or swapping request, including status updates.

relay_get_requests

Monitor the history of bridging and swapping requests to review past activity.

relay_transactions_index

Index transactions for tracking, enabling monitoring and correlation across chains.

relay_transactions_single

Index a specific transfer or wrap operation for focused monitoring and auditing.