Relay Protocol MCP server
Commit Nov 6, 2026Enables AI agents to perform cross-chain bridging, token swaps, and real-time blockchain data retrieval using the Relay Protocol.
Also known as relayprotocol/relay-mcp
- Stars
- 5
- Tools
- 16
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 6, 2026
- License
- —
What is Relay Protocol MCP?
Relay Protocol enables AI agents to perform cross-chain bridging, token swaps, and real-time blockchain data retrieval using the Relay Protocol. It exposes 16 tools, such as get_bridge_quote, get_swap_quote, estimate_fees.
Summary generated from the project's README
About Relay Protocol MCP server
Performing cross-chain bridging and token swaps through an AI agent is what relay-mcp enables for developers using Claude Desktop, Claude Code, or Cursor. This server connects your local environment to the Relay Protocol, allowing agents to retrieve real-time blockchain data, check chain health, and find quotes for moving assets between networks. It functions via stdio and requires an API key for specific tasks like retrieving transaction history, though it can operate without one for other functions.
The server provides sixteen specialized tools to handle various crypto tasks. Users can request quotes for bridging the same token across chains using get_bridge_quote or swap different tokens with get_swap_quote. It simplifies complex data retrieval by offering tools like get_token_details for market fundamentals and check_chain_status to monitor solver liquidity. Because the server is read-only, it provides the necessary information and deep links to the Relay web app for execution rather than signing or broadcasting transactions directly.
What you can do with it
- 1Calculate cross-chain bridge costsAsk the agent to provide a price quote and fee breakdown for moving a specific amount of ETH from Ethereum to Base.
- 2Monitor trending market assetsRequest a list of the most popular tokens currently trending on a specific blockchain network.
Written from the project's README. Every use case is checked against a quote from it.
Relay Protocol MCP tools 16
Detected from the READMEget_bridge_quoteget_swap_quoteestimate_feesget_supported_chainsget_supported_tokensget_trending_tokensget_token_priceget_token_detailsget_swap_sourcescheck_chain_statusget_transaction_statusget_transaction_history
Show all 16 toolsShow fewer tools
index_transactionget_app_feesget_relay_app_urlget_api_schema
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablerelayprotocol/relay-mcp is public and reachablegithub.com/relayprotocol/relay-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-06github.com/relayprotocol/relay-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model16 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubRelay MCP Server
A Model Context Protocol server for Relay Protocol — cross-chain bridge and swap tools for AI agents.
Tools (16)
Quoting & Routing
| Tool | Description |
|---|---|
get_bridge_quote |
Quote for bridging same token across chains |
get_swap_quote |
Quote for swapping between different tokens (same-chain or cross-chain) |
estimate_fees |
Fee breakdown for a bridge or swap route |
Token & Chain Discovery
| Tool | Description |
|---|---|
get_supported_chains |
List supported blockchain networks (slim response) |
get_supported_tokens |
Search for tokens across chains |
get_trending_tokens |
Currently trending tokens across Relay-supported chains |
get_token_price |
Current USD price of a token |
get_token_details |
Full token fundamentals: price, market cap, volume, liquidity, optional price chart |
get_swap_sources |
List DEX aggregators and AMMs that Relay routes through |
Chain Health
| Tool | Description |
|---|---|
check_chain_status |
Chain health, solver liquidity, and route configuration (3 API calls in 1 tool) |
Transaction Tracking
| Tool | Description |
|---|---|
get_transaction_status |
Check status by request ID or on-chain tx hash |
get_transaction_history |
Past transactions for a wallet |
index_transaction |
Tell Relay to index a transaction it may have missed |
Integrator Tools
| Tool | Description |
|---|---|
get_app_fees |
Claimable app fee balances and claim history (2 API calls in 1 tool) |
get_relay_app_url |
Deep link to the Relay web app with pre-filled parameters |
get_api_schema |
Discover Relay API endpoints and inspect their schemas |
Usage
Claude Desktop / Claude Code
Add to your claude_desktop_config.json or .claude.json:
{
"mcpServers": {
"relay": {
"command": "npx",
"args": ["-y", "@relayprotocol/relay-mcp"]
}
}
}
Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"relay": {
"command": "npx",
"args": ["-y", "@relayprotocol/relay-mcp"]
}
}
}
Run from source
npm install
npm run build
npm start
Environment variables
| Variable | Default | Description |
|---|---|---|
RELAY_API_URL |
https://api.relay.link |
Relay API base URL |
RELAY_API_KEY |
— | API key. Required by get_transaction_history (GET /requests/v3); optional elsewhere for higher rate limits |
MCP_TOKEN_SECRET |
random per process | HTTP mode only. Signs OAuth tokens; set it so tokens stay valid across restarts |
Features
- Chain name resolution — Pass
"base","ethereum","arb"instead of numeric chain IDs. Supports aliases and fuzzy matching. - Input validation — Addresses, amounts, and chain IDs are validated before hitting the API, with clear error messages.
- Bundled tools —
check_chain_statusandget_app_feescombine multiple API calls into single tools with parallel fetching. - Decision-tree descriptions — Tool descriptions guide agents to pick the right tool ("For just the price, use
get_token_price. For full fundamentals, useget_token_details."). - Slim responses — Responses are trimmed to essential fields. Chart data is downsampled from ~21KB to ~3KB.
- API schema discovery —
get_api_schemalets agents explore available endpoints on demand (progressive disclosure pattern). - Tx hash lookup —
get_transaction_statusaccepts either a request ID or an on-chain transaction hash. - Structured errors — Errors are categorized (validation, api, network, rate_limit, server, auth) with retryability hints.
Architecture
- Transport: Stdio (MCP spec)
- Runtime: Node.js >=20
- API: Direct HTTP calls to
api.relay.link(no SDK dependency) - Read-only: Returns quotes, fees, and status. Does not sign or broadcast transactions.
Agent flow examples
User: "Bridge 0.1 ETH from Ethereum to Base"
1. Agent calls get_bridge_quote(originChainId="ethereum", destinationChainId="base", ...)
→ chain names resolved automatically, quote returned with fees and ETA
2. Agent shows user the quote and a link to execute on relay.link
User: "What tokens are trending on Base?"
1. Agent calls get_trending_tokens(chainId="base")
→ returns token identities (no prices)
2. Agent calls get_token_price for each interesting token
→ returns current USD prices
License
MIT
Relay Protocol MCP questions
What tools does Relay Protocol MCP provide?
It exposes 16 tools, including get_bridge_quote, get_swap_quote, estimate_fees, get_supported_chains, get_supported_tokens.
Can this server execute transactions?
No, the server is read-only and does not sign or broadcast transactions; it provides quotes and links for execution.
What information can I get about tokens?
You can retrieve current USD prices, full fundamentals like market cap and liquidity, and identify trending tokens across supported chains.
Is an API key required?
An API key is required for the get_transaction_history tool, but it is optional for other tools, though it helps with rate limits.