Delora MCP

io.github.DeloraProtocolPublished by GitHub account DeloraProtocolv0.1.5Updated Oct 24, 2026

Delora MCP server for cross-chain quotes, supported chains, tokens, and tools.

VerifiedStreamable HTTPWeb executableFinance Developer Tools

Server details

Identifier: io.github.DeloraProtocol/delora-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account DeloraProtocol for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.DeloraProtocol%2Fdelora-mcp.svg)](https://sourceweft.com/mcp/io.github.DeloraProtocol%2Fdelora-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Delora MCP gives an assistant cross-chain swap quotes plus the supported chains, tokens and bridge/DEX tools behind them.

What you can do: Fetch a cross-chain quote with best route, output amount, calldata and gas
List supported chains, optionally filtered by chain type such as EVM or SVM
List supported tokens, filtered by chain or chain type, and look up a single token by chain and address or symbol
List available tools such as bridges and DEXes, optionally filtered by chain
Retrieve the server's own usage guide
When to use it: Useful when an assistant needs to plan or price a cross-chain token transfer: resolving chain IDs and token addresses, comparing routes, and getting calldata and gas estimates before a swap is executed elsewhere.
Requirements: Runs as a remote streamable HTTP endpoint or as a local npm package over stdio; the README also documents an HTTP mode with configurable port, host and API base URL. An optional Delora API key can be supplied via DELORA_API_KEY or an x-api-key header; network access to the Delora API is required.

Before you install

The API key is forwarded upstream as x-api-key, and in HTTP mode incoming x-api-key or Bearer headers take priority over DELORA_API_KEY, so run your own instance carefully. Quotes include calldata and gas for on-chain swaps; the server only returns data, but acting on it moves funds, so verify routes and amounts before signing. Quote data is sent to the Delora API.

Installation

In SourceWeft

Open Delora MCP in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.DeloraProtocol%2Fdelora-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "delora": {
      "type": "http",
      "url": "https://mcp.delora.build/mcp"
    }
  }
}

README

Delora MCP

MCP (Model Context Protocol) server for the Delora API: cross-chain quotes, supported chains, tokens, and tools.

Install

Configuration

Copy env.example to .env and adjust:

Variable	Description	Default
`DELORA_API_URL`	Delora API base URL	`https://api.delora.build`
`DELORA_API_KEY`	Optional API key forwarded to Delora API as `x-api-key`	unset
`MCP_TRANSPORT`	`stdio` or `http`	`stdio`
`PORT`	HTTP server port (when `MCP_TRANSPORT=http`)	`3000`
`HOST`	HTTP bind address	`0.0.0.0`

When DELORA_API_KEY is set, the MCP server forwards it to Delora API as the x-api-key header. In HTTP mode, the server also accepts incoming x-api-key or Authorization: Bearer ... headers and forwards the resolved key upstream. For HTTP requests, incoming headers take priority over DELORA_API_KEY. For stdio, DELORA_API_KEY remains the way to provide the key.

Run

Stdio (default) — for Cursor/IDE MCP over stdio:

HTTP — for streamable HTTP (e.g. behind a reverse proxy):

Server listens on http://0.0.0.0:3000/mcp.

Cursor configuration

Stdio:

json

{  "mcpServers": {    "delora": {      "command": "node",      "args": ["/path/to/delora-mcp/dist/index.js"]    }  }}

{  "mcpServers": {    "delora": {      "command": "node",      "args": ["/path/to/delora-mcp/dist/index.js"]    }  }}

Streamable HTTP (e.g. after deploying to https://mcp.delora.build):

json

{  "mcpServers": {    "delora": {      "url": "https://mcp.delora.build/mcp",      "transport": "streamable-http",      "headers": {        "x-api-key": "YOUR_API_KEY"      }    }  }}

{  "mcpServers": {    "delora": {      "url": "https://mcp.delora.build/mcp",      "transport": "streamable-http",      "headers": {        "x-api-key": "YOUR_API_KEY"      }    }  }}

You can also use Authorization: Bearer YOUR_API_KEY instead of x-api-key when your MCP client supports custom HTTP headers.

Docker

Build and run:

For production behind a domain (e.g. mcp.delora.build): run the container with MCP_TRANSPORT=http and put nginx/traefik (or another reverse proxy) in front with HTTPS; then use the URL https://mcp.delora.build/mcp with streamable-http in Cursor.

API

Delora API — base URL for all /v1/* endpoints (quotes, chains, tokens, tools, token).

Tools

Tool	Description
`get_instructions`	Returns this guide (call first for workflow).
`get_quote`	GET /v1/quotes — cross-chain quote.
`get_chains`	GET /v1/chains — supported chains.
`get_tools`	GET /v1/tools — available tools.
`get_tokens`	GET /v1/tokens — supported tokens.
`get_token`	GET /v1/token — single token by chain + token.

Source: README.md at commit d7ff951

Tools

get_instructions

CALL THIS FIRST. Returns the guide for Delora MCP: how to get quotes, chains, tokens, tools…

Takes no parameters.

get_quote

Get a cross-chain quote: best route, output amount, calldata, gas. Use get_chains and get_tokens first to resolve chain IDs and token addresses.

ParametersfeeamountrequiredslippageintegratororiginChainIdrequiredsenderAddressoriginCurrencyrequiredreceiverAddressdestinationChainIdrequireddestinationCurrencyrequired

get_chains

List supported chains. Optionally filter by chainTypes (e.g. EVM,SVM).

ParameterschainTypes

get_tools

List available tools (e.g. bridges, DEXes). Optionally filter by chains (comma-separated).

Parameterschains

get_tokens

List supported tokens. Optionally filter by chains and/or chainTypes.

ParameterschainschainTypes

get_token

Get a single token by chain and token address/symbol.

Parameterschainrequiredtokenrequired

Version history

v0.1.5LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts