Skip to main content
Glama
Delora MCP

Delora MCP

Official

Delora MCP

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

Install

npm install

Related MCP server: Relay Protocol MCP Server

Configuration

The server reads configuration from the process environment. It does not load a .env file on its own: export the variables in your shell, set them in your MCP client's env block, or copy env.example to .env and start the server with node --env-file=.env dist/index.js.

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:

npm run dev
# or
npm run build && npm start

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

npm run dev:http
# or
npm run build && npm run start:http

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

Cursor configuration

Stdio:

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

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

{
  "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:

docker build -t delora-mcp .
docker run -p 3000:3000 -e MCP_TRANSPORT=http delora-mcp

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.

Available Tools

6 tools
get_chainsAInspect

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

Inputs: chainTypes.

get_instructionsAInspect

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

Inputs: no named parameters.

get_quoteAInspect

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.

Inputs: originChainId (required), destinationChainId (required), amount (required), originCurrency (required), +6 more.

get_tokenBInspect

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

Inputs: chain (required), token (required).

get_tokensAInspect

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

Inputs: chains, chainTypes.

get_toolsAInspect

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

Inputs: chains.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource: chains, instructions, quote, token, tokens, tools. No overlapping purposes, clear differentiation.

    Naming Consistency5/5

    All tools follow a consistent 'get_' prefix with singular or plural nouns (get_chains, get_instructions, get_quote, get_token, get_tokens, get_tools). Predictable pattern.

    Tool Count5/5

    6 tools is well-scoped for a cross-chain quote server. Covers discovery, guidance, and quote retrieval without being excessive or too few.

    Completeness5/5

    The set covers all necessary operations: listing chains, tokens, and tools; retrieving a specific token; getting a quote; and providing instructions. No obvious gaps for its stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers