home / mcp / bridge rates mcp server
Provides real-time cross-chain bridge rates, supported chains, and bridge options for on-chain AI decision making.
Configuration
View docs{
"mcpServers": {
"kukapay-bridge-rates-mcp": {
"command": "node",
"args": [
"/absolute/path/to/bridge-rates-mcp/index.js"
]
}
}
}Bridge Rates MCP Server provides real-time cross-chain bridge rates and optimal transfer routes to support decision-making by onchain AI agents. You can query, compare, and summarize bridge options across chains, including rates in USD and gas costs, using a standard MCP client. This server is designed to be integrated into MCP-enabled workflows so you can automate decision making and route selection.
You interact with the Bridge Rates MCP Server through an MCP-compatible client. After configuring the client to connect to the server, you can request bridge rates for token pairs, list supported chains, and list available bridges. Your client will present the results in a structured format suitable for onchain AI agents, including Markdown tables and concise metadata like providers and tags.
Typical workflows you can perform include: getting current cross-chain bridge rates for a specific token pair, discovering which chains are supported for bridging, and seeing which bridges or exchanges are available for transfers. Use these results to evaluate routing options and optimize transfer costs.
Prerequisites you need before running the server:
• Node.js: Version 18 or higher.
• npm: For dependency management.
• MCP Client: An MCP-compatible client (for example, Claude Desktop) to interact with the server.
# Clone the repository
git clone https://github.com/kukapay/bridge-rates-mcp.git
cd bridge-rates-mcp
# Install dependencies
npm install
# Integrate with an MCP client (example shown for Claude Desktop)
# Create or edit the MCP client configuration to connect to this server
# Example configuration (Claude Desktop) might look like this:MCP client integration example shows how to wire the server into a local MCP client. You typically configure the client to start the server as a local process and expose it under an MCP name such as bridge_rates. Restart your MCP client after making changes to ensure the tool becomes available.
{
"mcpServers": {
"bridge_rates": {
"command": "node",
"args": ["/absolute/path/to/bridge-rates-mcp/index.js"]
}
}
}Fetches cross-chain bridge rates for a token pair between two chains, returning all available routes in a Markdown table.
Fetches a sorted list of chains supported by LI.FI for cross-chain bridging, presented in a Markdown table.
Fetches a sorted list of bridges and exchanges supported by LI.FI, presented in a Markdown table.