The Delora MCP Server exposes the following tools. Each tool maps to a corresponding Delora API endpoint under https://api.delora.build/v1.
Workflow & Instructions
get_instructions
Call this first. Returns the guide for using the Delora MCP server: how to get quotes, chains, tokens, and tools.
No parameters required.
Use get_instructions at the start of a session to understand the recommended workflow (get_chains → get_tokens/get_token → get_quote).
Quote & Routing
get_quote
Get a cross-chain quote: best route, estimated output amount, calldata, and gas. Use get_chains and get_tokens (or get_token) first to resolve chain IDs and token addresses.
| Parameter | Required | Description |
|---|
originChainId | Yes | Origin chain ID (e.g. 1 for Ethereum, 42161 for Arbitrum) |
destinationChainId | Yes | Destination chain ID |
amount | Yes | Amount in smallest units (wei/smallest decimals) |
originCurrency | Yes | Token address on origin chain; use 0x0... for native currency |
destinationCurrency | Yes | Token address on destination chain; use 0x0... for native |
senderAddress | Yes | Sender wallet address |
receiverAddress | No | Receiver wallet address. Defaults to sender only when origin/destination chain types match; otherwise required |
integrator | No | Integrator string configured for your Delora integration; used for attribution and fee handling |
fee | No | Fee 0–0.1; only valid when integrator is also provided |
slippage | No | Slippage tolerance 0–1 (e.g. 0.005 for 0.5%) |
inputAmount, outputAmount, adapter, a single calldata object (transaction data for the wallet), and optional fees, gas, and warnings details.
Use the same integrator string that is configured for your Delora integration. If you want Delora to apply an integrator fee, send both integrator and fee. The Delora API key is not passed as a tool parameter; configure it on the MCP server with DELORA_API_KEY or send it to the HTTP MCP endpoint via x-api-key / Authorization when your client supports custom headers.
Address behavior follows the REST API contract:
senderAddress is always required.receiverAddress is optional only when the origin and destination chain types match.- If the chain types differ,
receiverAddress must be provided explicitly.
get_chains
List supported chains. Returns chain IDs, names, chain types, RPC URLs, block explorer links, and native token info.
| Parameter | Required | Description |
|---|
chainTypes | No | Comma-separated chain types (e.g. EVM, SVM) |
get_tokens
List supported tokens. Use this to discover available tokens before requesting quotes. Optionally filter by chains and/or chain types.
| Parameter | Required | Description |
|---|
chains | No | Comma-separated chain IDs or identifiers |
chainTypes | No | Chain types (e.g. EVM, SVM) |
get_token
Get details about a single token by chain and token address or symbol (price, decimals, name, etc.).
| Parameter | Required | Description |
|---|
chain | Yes | Chain ID or chain identifier (e.g. 1 or eth) |
token | Yes | Token address or symbol (e.g. USDC, WETH) |
| Parameter | Required | Description |
|---|
chains | No | Comma-separated chain IDs or identifiers to filter results |
Use the key values returned by get_tools when interpreting quote responses (e.g. which bridge or exchange was selected).
API Base URL
All tools call the Delora API at https://api.delora.build/v1. The MCP server can be configured with a different base URL via the DELORA_API_URL environment variable when self-hosting. 
