LiFi

Provides cross-chain swap capabilities via MCP by exposing LI.FI API tools and optional keystore-signed transactions.
  • go

4

GitHub Stars

go

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "lifinance-lifi-mcp": {
      "command": "lifi-mcp",
      "args": []
    }
  }
}

You run a Li.FI Model Context Protocol (MCP) server that connects to the LI.FI API to enable cross-chain swaps across multiple liquidity pools and bridges. This server exposes a set of tools you can call through an MCP client, and it can operate with or without a keystore for signing transactions. When used with a keystore, you can execute and sign transactions directly from the server.

How to use

Set up your client to connect to the LiFi MCP server and discover the available tools. You can start the server in stdio mode for local use or integrate it into your MCP client workflow. Once connected, you can list all available tools, query token and chain information, obtain cross-chain quotes, check transfer status, and access wallet-related operations. If you enable the keystore feature, you gain the ability to execute signed transactions, approve tokens, and transfer assets through the server.

Practical usage patterns include: using the token and chain information tools to discover assets and networks, requesting quotes for cross-chain or same-chain transfers, and checking the status of ongoing transfers. If you are developing an application, you can embed the MCP server by creating an MCP client, connecting, initializing, and then invoking the desired tools by name (for example, to retrieve chain details or to get a swap quote). When running with a keystore, you can perform signed transactions such as token approvals and transfers through the provided transaction tools.

How to install

Prerequisites: ensure you have a Go toolchain installed on your development machine.

Install the LiFi MCP server tool for Go:

go install github.com/lifinance/lifi-mcp@latest

Run the MCP server

Start the MCP server in standard mode (stdio) for normal operation.

lifi-mcp

Start the MCP server with keystore support to enable transaction capabilities.

lifi-mcp --keystore <keystore-name> --password <keystore-password>

Version check

Verify the installed version to confirm the server is available and up to date.

lifi-mcp --version

Available tools

get-tokens

Fetch all tokens known to LI.FI services with filters for chains, chainTypes, and minimum price in USD.

get-token

Get detailed information about a specific token by chain and token address.

get-chains

Retrieve information about all supported chains with optional chainTypes filtering.

get-chain-by-id

Find a chain using its numeric ID.

get-chain-by-name

Find a chain by name, key, or ID (case-insensitive).

get-quote

Obtain a quote for a token transfer, whether cross-chain or within the same chain.

get-status

Check the status of an ongoing cross-chain transfer for a given transaction hash and bridge.

get-connections

Discover all possible connections between chains for a given token pair and chain types.

get-tools

List available bridges and exchanges that support the configured chains.

get-wallet-address

Return the Ethereum address associated with the loaded private key.

get-native-token-balance

Query the native token balance for a wallet using a provided RPC URL and address.

get-token-balance

Query the balance of a specific ERC20 token for a wallet.

get-allowance

Check the ERC20 allowance granted to a spender from a specific owner.

execute-quote

Execute a signed transaction from a stored private key (requires keystore).

approve-token

Approve a specific amount of an ERC20 token for spending by another address.

transfer-token

Transfer ERC20 tokens to another address.

transfer-native

Transfer native cryptocurrency to another address.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational