Skip to main content
Glama

OPENOCEAN-MCP Server

An MCP server for executing token swaps across multiple decentralized exchanges using OpenOcean's aggregation API.

Overview

This project implements a Model Context Protocol (MCP) server to interact with decentralized exchanges (DEXs). It allows MCP-compatible clients (like AI assistants, IDE extensions, or custom applications) to access functionalities such as getting quotes for swaps and executing swaps across multiple chains.

This server is built using TypeScript and fastmcp.

Related MCP server: SEI DEX MCP

Features (MCP Tools)

The server exposes the following tools that MCP clients can utilize:

  • CHAIN_LIST: Fetch chain list.

    • Parameters:

  • GAS_PRICE: Fetch gas price.

    • Parameters: chain (string)

  • QUOTE: Fetch a quote for a swap.

    • Parameters: chain (string), inTokenAddress (string), outTokenAddress (string), amount (string), slippage (string)

  • SWAP: Building swap transaction.

    • Parameters: chain (string), inTokenAddress (string), outTokenAddress (string), amount (string), slippage (string), account (string)

  • GET_TRANSACTION: Fetch transaction info.

    • Parameters: chain (string), hash (string)

  • TOKEN_LIST: Fetch token list.

    • Parameters: chain (string)

  • DEX_LIST: Fetch dex list.

    • Parameters: chain (string)

Parameter breakdown

  • chain: The chain code of the DEX.

  • inTokenAddress: The token you want to sell.

  • outTokenAddress: The token you want to buy.

  • amount: Token amount with decimals. For example, if 1 USDT is input, use 1000000 (1 USDT * 10^6).

  • slippage: Define the acceptable slippage level by inputting a percentage value within the range of 0.05 to 50. 1% slippage set as 1.

  • account: user's wallet address.

  • hash: Hash from the OpenOcean contract on the blockchain.

Prerequisites

Installation

There are a few ways to use openocean-mcp:

1. Using pnpm dlx (Recommended for most MCP client setups):

You can run the server directly using pnpm dlx without needing a global installation. This is often the easiest way to integrate with MCP clients. See the "Running the Server with an MCP Client" section for examples. (pnpm dlx is pnpm's equivalent of npx)

2. Global Installation from npm (via pnpm):

Install the package globally to make the openocean-mcp command available system-wide:

pnpm add -g openocean-mcp

3. Building from Source (for development or custom modifications):

  1. Clone the repository:

    git clone https://github.com/openocean-finance/openocean-mcp.git
    cd openocean-mcp
  2. Install dependencies:

    pnpm install
  3. Build the server: This compiles the TypeScript code to JavaScript in the dist directory.

    pnpm run build

    The prepare script also runs pnpm run build, so dependencies are built upon installation if you clone and run pnpm install.

Configuration (Environment Variables)

This MCP server may require certain environment variables to be set by the MCP client that runs it. These are typically configured in the client's MCP server definition (e.g., in a mcp.json file for Cursor, or similar for other clients).

  • Any necessary environment variables for wallet providers or API keys.

Running the Server with an MCP Client

MCP clients (like AI assistants, IDE extensions, etc.) will run this server as a background process. You need to configure the client to tell it how to start your server.

Below is an example configuration snippet that an MCP client might use (e.g., in a mcp_servers.json or similar configuration file). This example shows how to run the server using the published npm package via pnpm dlx.

{
  "mcpServers": {
    "openocean-mcp-server": {
      "command": "pnpm",
      "args": ["dlx", "openocean-mcp"]
    }
  }
}

Alternative if Globally Installed:

If you have installed openocean-mcp globally (pnpm add -g openocean-mcp), you can simplify the command and args:

{
  "mcpServers": {
    "openocean-mcp-server": {
      "command": "openocean-mcp",
      "args": []
    }
  }
}
  • command: The executable to run.

    • For pnpm dlx: "pnpm" (with "dlx" as the first arg)

    • For global install: "openocean-mcp"

  • args: An array of arguments to pass to the command.

    • For pnpm dlx: ["dlx", "openocean-mcp"]

    • For global install: []

  • env: An object containing environment variables to be set when the server process starts. This is where you provide any necessary environment variables.

  • workingDirectory: Generally not required when using the published package via pnpm dlx or a global install, as the package should handle its own paths correctly. If you were running from source (node dist/index.js), then setting workingDirectory to the project root would be important.

Available Tools

7 tools
CHAIN_LISTC

Get chain list

Inputs: no named parameters.

DEX_LISTC

Get dex list

Inputs: chain.

GAS_PRICEC

Get gas price

Inputs: chain.

GET_TRANSACTIOND

Get Transaction

Inputs: hash (required), chain.

QUOTEC

Quote the price of a specific trading pair

Inputs: inTokenAddress (required), outTokenAddress (required), amount (required), chain, +1 more.

SWAPC

Building swap transaction

Inputs: inTokenAddress (required), outTokenAddress (required), amount (required), account (required), +2 more.

TOKEN_LISTC

Get token list

Inputs: chain.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    C2.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different aspects of DeFi operations: chain management, DEX listings, gas pricing, transaction retrieval, price quoting, swap building, and token listings. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., GET_TRANSACTION, GAS_PRICE, TOKEN_LIST), but there are minor deviations: CHAIN_LIST and DEX_LIST use noun_verb order, and QUOTE and SWAP are single verbs without nouns. The naming is still readable and mostly predictable.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a DeFi/blockchain utility, covering essential operations like listing resources, pricing, transactions, and swaps. Each tool earns its place without feeling bloated or insufficient for the domain.

    Completeness4/5

    The toolset provides strong coverage for core DeFi workflows: resource listing (chains, DEXs, tokens), pricing (gas, quotes), and transaction handling (get, build swaps). A minor gap is the lack of tools for managing user accounts or executing swaps directly, but agents can work around this with the provided building blocks.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with DeFi trading and portfolio analytics through Odos DEX aggregation and Zerion APIs. Provides access to swap quotes, liquidity operations, token pricing, portfolio analysis, and transaction history across multiple blockchain networks.
      3
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with decentralized exchanges on the SEI blockchain through natural language commands. Supports token swapping, wrapping, liquidity pool queries, and automated trading strategies on DragonSwap.
      ISC