testinguser1111111/sei-mcp-server

SEI MCP Server V2: The Autonomous Agent Toolkit for Sei 🚀

Sei Model Context Protocol (Sei MCP) server provides blockchain services for the Sei blockchain. This server enables AI assistants and agents to interact via unified interface.

🎥 Sei MCP V2 Demo Video

Watch the demo video to see Sei MCP V2 in action.

📦 Sei MCP V2 Package on npm

You can install the Sei MCP V2 package via npm:

npm install @sei-mcp-v2/sei-mcp-server

📋 Contents

• Overview
• Features
• Supported Networks
• Prerequisites
• Installation
• Server Configuration
• Usage
• API Reference
  • Tools
  • Resources
• Security Considerations
• Project Structure
• Development
• License

🔭 Overview

Our vision is to provide the foundational infrastructure that empowers AI to act as autonomous agents, simplifying complex on-chain actions—from DeFi trading to cross-chain bridging—into easy, natural language conversations.

To bring this vision to life, we've built SEI MCP V2, a massively expanded, multi-protocol infrastructure suite designed as the ultimate toolkit for AI agents on the Sei Network. This server transforms the core MCP concept into an all-in-one gateway to the Web3 ecosystem, accessible through a unified interface.

💪 Core Capabilities

• 🐝 Hive Natural Language Querying

  • A revolutionary tool allowing AI agents to query complex on-chain data with simple English prompts.
  • Example query: “What are the holdings in my wallet 0x...?”

• 💹 Advanced DeFi & NFT Trading SEI MCP V2 offers a complete suite for decentralized finance and NFT trading:

  • Citrex Perpetual Futures Exchange:

    • Place advanced orders (market, limit)
    • Manage orders in batches
    • Monitor account health and margin
    • Access real-time market data (order books, klines)

  • DragonSwap V3 DEX:

    • Execute atomic token swaps
    • Manage concentrated liquidity positions
    • Create new liquidity pools

  • OpenSea NFT Marketplace:

    • Discover collections and NFTs
    • Analyze stats
    • Create and fulfill listings and offers
    • Track event history and buy NFTs with a single command

  • Yei Finance Lending Protocol:

    • Supply assets to earn interest
    • Borrow against collateral
    • Utilize advanced features like flash loans and credit delegation

• 🌉 DEX & Bridge Aggregation Robust cross-chain capabilities through leading protocols:

  • Symphony & Kame DEX Aggregators:

    • Find optimal swap routes
    • Execute trades with advanced options
    • Discover supported tokens
    • Generate transaction calldata for offline use

  • Li.Fi & deBridge Cross-Chain Bridging:

    • Seamlessly bridge assets across different blockchains
    • Get quotes from multiple bridge providers
    • Track order status and manage the cross-chain transaction lifecycle

• 🪙 Complete Token Lifecycle Management Tools to manage on-chain assets:

  • Create new ERC20 and ERC721 (NFT) tokens from scratch
  • Deploy, verify, and mint tokens on Sei and on SeiTrace

• 📊 Rich Data & Analytics Comprehensive data integrations for a holistic view of the ecosystem:

  • SeiTrace: Deep on-chain analysis (wallets, transactions, token holders, etc.)
  • CoinGecko & DexScreener: Real-time market data, historical prices, live DEX analytics

SEI MCP V2 is built to be compatible with existing AI assistants like Claude or Cursor, enabling users and developers to interact with the entire Sei ecosystem through simple, conversational interfaces. This empowers the development of sophisticated, autonomous AI agents, capable of executing complex multi-step tasks effortlessly.

✨ Features

🌐 Supported Networks

• Sei Mainnet
• Sei Testnet
• Sei Devnet

🛠️ Prerequisites

• Bun 1.0.0 or higher
• Node.js 18.0.0 or higher (if not using Bun)

📦 Installation

# Clone the repository
git clone https://github.com/testinguser1111111/sei-mcp-server.git
cd sei-mcp-server

# Install dependencies with Bun
bun install

# Or with npm
npm install

⚙️ Server Configuration

The server uses the following default configuration:

• Default Chain ID: 1329 (Sei Mainnet)
• Server Port: 3001
• Server Host: 0.0.0.0 (accessible from any network interface)

These values are hardcoded in the application. If you need to modify them, you can edit the following files:

• For chain configuration: src/core/chains.ts
• For server configuration: src/server/http-server.ts

Environment Variables

The server supports loading configuration from environment variables:

• PRIVATE_KEY: Required private key for any blockchain operations that involve signing transactions (e.g., transferring tokens, interacting with smart contracts that modify state). This is the sole method for providing a private key. If this environment variable is not set when a transaction-signing tool is invoked, the tool will return an error message instructing the AI assistant to ask the user to set the PRIVATE_KEY environment variable and restart the MCP server.
• COINGECKO_PRO_API_KEY: Optional CoinGecko Pro API key for accessing CoinGecko API services.
• SEITRACE_API_KEY: Optional SeiTrace Insights API key for accessing SeiTrace Insights API services.
• OPENSEA_API_KEY: Optional OpenSea API key for accessing OpenSea API services.
• HIVE_INTELLIGENCE_API_KEY: Optional Hive Intelligence API key for accessing Hive Intelligence API services.

Create a .env file in the root directory based on the .env.example template:

# .env.example
PRIVATE_KEY=your_private_key_here
COINGECKO_PRO_API_KEY=your_coingecko_pro_api_key_here
SEITRACE_API_KEY=your_seitrace_api_key_here
OPENSEA_API_KEY=your_opensea_api_key_here
HIVE_INTELLIGENCE_API_KEY=your_hive_intelligence_api_key_here

SECURITY WARNING: Never commit your actual private key, API keys, or any sensitive information to version control. The .env file is included in .gitignore by default.

🚀 Usage

Using with Claude Desktop

1. Install the Claude Desktop.
2. Go to Settings > Developer > Edit Config.
3. Add the following to the mcpServers section:

{
  "mcpServers": {
    "sei": {
      "command": "npx",
      "args": [
        "-y",
        "@sei-mcp-v2/sei-mcp-server"
      ],
      "env": {
        "PRIVATE_KEY": "your_private_key_here",
        "COINGECKO_PRO_API_KEY": "your_coingecko_pro_api_key_here",
        "SEITRACE_API_KEY": "your_seitrace_api_key_here",
        "OPENSEA_API_KEY": "your_opensea_api_key_here",
        "HIVE_INTELLIGENCE_API_KEY": "your_hive_intelligence_api_key_here"
      }
    }
  }
}

4. Save the configuration file and restart Claude. When done, Claude will add new prompts, resources and tools. To access prompts, click "+" button in the bottom left corner. And then "Add from sei".

From there, click "Add from sei" to and for example, add a "my_wallet_address" prompt. Claude should invoke now get_address_from_private_key tool and return the wallet address. Sometimes, model may fail to understand tbe prompt or random question. Try to add a bit more context or retry with extensive thinking option.

All tools available could be found by clicking "Search And Tools" button and then "sei".

Using npx (No Installation Required)

You can run the Sei MCP Server directly without installation using npx:

# Run the server in stdio mode (for CLI tools)
npx @sei-mcp-v2/sei-mcp-server

# Run the server in HTTP mode (for web applications)
npx @sei-mcp-v2/sei-mcp-server --http

Running the Server Locally

Start the server using stdio (for embedding in CLI tools):

# Start the stdio server
bun start

# Development mode with auto-reload
bun dev

Or start the HTTP server with SSE for web applications:

# Start the HTTP server
bun start:http

# Development mode with auto-reload
bun dev:http

Connecting to the Server

Connect to this MCP server using any MCP-compatible client. For testing and debugging, you can use the MCP Inspector.

Connecting from Cursor

To connect to the MCP server from Cursor:

1. Open Cursor and go to Settings (gear icon in the bottom left)
2. Scroll down to "MCP" section
3. Click "Add new Global MCP server"
4. In mcp.json tab add the following configuration

{
  "mcpServers": {
    "sei-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@sei-mcp-v2/sei-mcp-server"
      ],
      "env": {
        "PRIVATE_KEY": "your_private_key_here",
        "COINGECKO_PRO_API_KEY": "your_coingecko_pro_api_key_here",
        "SEITRACE_API_KEY": "your_seitrace_api_key_here",
        "OPENSEA_API_KEY": "your_opensea_api_key_here",
        "HIVE_INTELLIGENCE_API_KEY": "your_hive_intelligence_api_key_here"
      }
    }
  }
}

Example: HTTP Mode with SSE

If you're developing a web application and want to connect to the HTTP server with Server-Sent Events (SSE), you can use this configuration:

{
  "mcpServers": {
    "sei-mcp-sse": {
      "url": "http://localhost:3001/sse"
    }
  }
}

This connects directly to the HTTP server's SSE endpoint, which is useful for:

• Web applications that need to connect to the MCP server from the browser
• Environments where running local commands isn't ideal
• Sharing a single MCP server instance among multiple users or applications

To use this configuration:

1. Create a .cursor directory in your project root if it doesn't exist
2. Save the above JSON as mcp.json in the .cursor directory
3. Restart Cursor or open your project
4. Cursor will detect the configuration and offer to enable the server(s)

Example: Using the MCP Server in Cursor

After configuring the MCP server with mcp.json, you can easily use it in Cursor. Here's an example workflow:

1. Create a new JavaScript/TypeScript file in your project:

// blockchain-example.js
async function main() {
  try {
    // Get Sei balance for an address
    console.log("Getting Sei balance for 0x1234...");
    
    // When using with Cursor, you can simply ask Cursor to:
    // "Check the Sei balance of 0x1234 on mainnet"
    // Or "Transfer 0.1 Sei from my wallet to 0x1234"
    
    // Cursor will use the MCP server to execute these operations 
    // without requiring any additional code from you
    
    // This is the power of the MCP integration - your AI assistant
    // can directly interact with blockchain data and operations
  } catch (error) {
    console.error("Error:", error.message);
  }
}

main();

2. With the file open in Cursor, you can ask Cursor to:

   • "Check the current Sei balance of 0x1234 on mainnet"
   • "Show me the latest block on Sei"
   • "Check if 0x1234... is a contract address"

3. Cursor will use the MCP server to execute these operations and return the results directly in your conversation.

The MCP server handles all the blockchain communication while allowing Cursor to understand and execute blockchain-related tasks through natural language.

Connecting using Claude CLI

If you're using Claude CLI, you can connect to the MCP server with just two commands:

# Add the MCP server
claude mcp add sei-mcp-server npx @sei-mcp/sei-mcp-server

# Start Claude with the MCP server enabled
claude

Example: Getting a Token Balance

// Example of using the MCP client to check a token balance
const mcp = new McpClient("http://localhost:3000");

const result = await mcp.invokeTool("get-token-balance", {
  tokenAddress: "0x3894085ef7ff0f0aedf52e2a2704928d1ec074f1", // USDC on Sei
  ownerAddress: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045", 
  network: "sei"
});

console.log(result);
// {
//   tokenAddress: "0x3894085ef7ff0f0aedf52e2a2704928d1ec074f1",
//   owner: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
//   network: "sei",
//   raw: "1000000000",
//   formatted: "1000",
//   symbol: "USDC",
//   decimals: 6
// }

📚 API Reference

Tools

The server provides the following MCP tools for agents.

Resources

🔒 Security Considerations

• Private keys are used only for transaction signing and are never stored by the server
• Consider implementing additional authentication mechanisms for production use
• Use HTTPS for the HTTP server in production environments
• Implement rate limiting to prevent abuse
• For high-value services, consider adding confirmation steps

📁 Project Structure

sei-mcp-server/
├── src/
│   ├── index.ts                # Main stdio server entry point
│   └── server/                 # Server-related files
│   │    ├── http-server.ts      # HTTP server with SSE
│   │    └── server.ts           # General server setup
│   └── core/
│       ├── chains.ts           # Chain definitions and utilities 
│       ├── config.ts           # MCP configuration
│       ├── resources.ts        # MCP resources implementation
│       ├── prompts.ts          # MCP prompts implementation
│       ├── services/           # Core blockchain logic and service implementations
│       │   ├── index.ts        # Service exports
│       │   ├── abi/            # Contract ABI definitions
│       │   ├── balance.ts      # Balance services
│       │   ├── blocks.ts       # Block services
│       │   ├── citrex.ts       # Citrex perpetuals exchange services
│       │   ├── clients.ts      # RPC client utilities
│       │   ├── coingecko.ts    # CoinGecko API service logic
│       │   ├── contracts.ts    # Smart contract interaction services
│       │   ├── deBridge.ts     # deBridge cross-chain service logic
│       │   ├── deployERC20.ts  # ERC20 deployment service logic
│       │   ├── deployERC721.ts # ERC721 deployment service logic
│       │   ├── dexscreener.ts  # Dexscreener API service logic
│       │   ├── dragonswap.ts   # DragonSwap V3 DEX API service logic
│       │   ├── hive_intelligence.ts         # Hive Intelligence Query service logic
│       │   ├── kame_ag.ts         # Kame DEX Aggregator service logic
│       │   ├── lifi.ts         # Li.Fi cross-chain service logic
│       │   ├── network.ts      # Network and block services
│       │   ├── opensea.ts      # OpenSea NFT marketplace service logic
│       │   ├── seitrace.ts     # SeiTrace API service logic
│       │   ├── symphony.ts     # Symphony DEX Aggregator service logic
│       │   ├── tokens.ts       # Token metadata services
│       │   ├── transactions.ts # Transaction services
│       │   ├── transfers.ts    # Transfers services
│       │   ├── utils.ts        # Utility services
│       │   ├── wrappedSei.ts   # WSEI wrapping and unwrapping services
│       │   └── yeifinance.ts   # Yei Finance API service logic
│       └── tools/              # MCP tool registrations
│           ├── index.ts        # Tool exports
│           ├── citrex.ts       # Citrex perpetuals exchange tools
│           ├── coingecko.ts    # CoinGecko market data tools
│           ├── deBridge.ts     # deBridge cross-chain tools
│           ├── deployERC20.ts  # ERC20 deployment & management tools
│           ├── deployERC721.ts # ERC721 deployment & management tools
│           ├── dexscreener.ts  # Dexscreener analytics tools
│           ├── dragonswap.ts   # DragonSwap V3 DEX tools
│           ├── hive_intelligence.ts         # Hive Intelligence Query tools
│           ├── kame_ag.ts         # Kame DEX Aggregator tools
│           ├── lifi.ts         # Li.Fi cross-chain tools
│           ├── network.ts      # Network and block tools
│           ├── opensea.ts      # OpenSea NFT marketplace tools
│           ├── seitrace.ts     # SeiTrace Insights tools
│           ├── symphony.ts     # Symphony DEX Aggregator tools
│           ├── token.ts        # Token and wallet tools
│           └── yeifinance.ts   # Yei Finance tools
├── .env.example                # Example environment variables
├── .gitignore                  # Git ignore file
├── .npmignore                  # NPM ignore file
├── CHANGELOG.md                # Project changelog
├── LICENSE                     # Project license
├── package.json                # Project dependencies and scripts
├── tsconfig.json               # TypeScript compiler configuration
└── README.md                   # Project documentation

🛠️ Development

To modify or extend the server:

1. Add new services in the appropriate file under src/core/services/
2. Add new tools in the appropriate file under src/core/tools/
3. Register new resources in src/core/resources.ts
4. Add new network support in src/core/chains.ts
5. To change server configuration, edit the hardcoded values in src/server/http-server.ts

📄 License

This project is licensed under the terms of the .

Made with ❤️ for Sei Ecosystem