Openocean

What is Openocean?

Openocean is an MCP server that integrates with OpenOcean’s aggregation API to enable token swaps across multiple decentralized exchanges. It is designed for MCP-compatible clients such as AI assistants, IDE extensions, or custom applications.

How to use Openocean?

Install the server via pnpm dlx openocean-mcp, a global install (pnpm add -g openocean-mcp), or by building from source. Configure your MCP client to run the server using the command pnpm with args ["dlx", "openocean-mcp"] (or "openocean-mcp" for global install) and provide any required environment variables. Invoke the exposed tools—such as QUOTE and SWAP—from the client to perform on-chain operations.

Key features of Openocean

• Provides tools for chain list, gas price, and token list.
• Fetches swap quotes and builds swap transactions.
• Retrieves transaction information from the blockchain.
• Supports multiple chains via chain code parameters.
• Allows slippage configuration from 0.05% to 50%.
• Built with TypeScript and fastmcp.

Use cases of Openocean

• Fetching real-time quotes for token swaps across DEXs.
• Executing token swaps directly from an MCP client.
• Checking gas prices on supported chains.
• Building and retrieving swap transaction details.

FAQ from Openocean

What is the purpose of this server?

It enables MCP-compatible clients to execute token swaps across multiple decentralized exchanges using OpenOcean’s aggregation API.

What are the prerequisites for using the server?

Node.js v18 or newer and pnpm are required.

How is slippage configured in swap requests?

Slippage is passed as a percentage parameter (range 0.05 to 50) to the QUOTE and SWAP tools, with 1 representing 1% slippage.

What data does the server access?

It fetches on-chain data including quotes, gas prices, token lists, DEX lists, and transaction information via OpenOcean’s API.

How is the server invoked by an MCP client?

The client runs the server as a background process, typically set up with a command and arguments in the client’s MCP server configuration (e.g., using pnpm dlx or a global install).