MCP ExplorerExplorer

Mcp Solana Dex

@waifuaion 10 months ago
1 MIT-0
FreeCommunity
AI Systems
FastMCP server implementing basic Solana DEX operations. ✨ Provides tools for sell order creation, cancellation, and retrieval. 👍 Executes orders using pre-signed token/SOL transactions (non-atomic). 🙏 Persists order book to JSON file. 📁 Associates orders with external ICO IDs. 🔗 Utilizes Solders & httpx for Solana interaction. ☀️

Overview

What is Mcp Solana Dex

mcp-solana-dex is a FastMCP server that implements basic decentralized exchange (DEX) operations on the Solana blockchain. It provides tools for creating, canceling, and retrieving sell orders, while executing orders using pre-signed token/SOL transactions.

Use cases

Use cases for mcp-solana-dex include creating and managing sell orders for tokens linked to ICOs, facilitating trading operations in a decentralized manner, and providing a simple interface for developers to integrate DEX functionalities into their applications.

How to use

To use mcp-solana-dex, ensure that dependencies are installed, navigate to the parent directory of the main project, and start the DEX server using the command poetry run python mcp_solana_dex/server.py. Interact with the server through an MCP client connected to its standard input/output.

Key features

Key features of mcp-solana-dex include: 1) MCP Tools for DEX functions such as create_order, cancel_order, execute_order, and get_orders; 2) File-based persistence that stores the order book in a JSON file; 3) Association of orders with specific ICO IDs.

Where to use

mcp-solana-dex can be used in the field of decentralized finance (DeFi), particularly for token trading associated with initial coin offerings (ICOs) on the Solana blockchain.

Content

MCP Solana DEX Server

This directory contains a a simple Decentralized Exchange (DEX) MCP server.

Purpose

This server provides basic DEX functionalities for tokens associated with ICOs managed by the main server:

  • Creating sell orders.
  • Cancelling sell orders.
  • Executing sell orders (buying from existing orders).
  • Retrieving the current order book for an ICO.

Features

  • MCP Tools: Exposes DEX functions as MCP tools (create_order, cancel_order, execute_order, get_orders).
  • File-Based Persistence: Stores the order book in a JSON file (data/order_book.json by default).
  • ICO Association: Orders are associated with specific ico_ids.

Disclaimer: This is a simplified example. The execute_order tool performs server-side pre-condition checks (buyer SOL balance, seller token balance) before updating the internal order book. It does NOT execute the on-chain atomic swap. Clients interacting with this server are responsible for constructing and submitting the actual atomic swap transaction after receiving a success response from execute_order. This is NOT suitable for production without a robust client-side atomic swap implementation.

Configuration (./.env)

Create a .env file in this directory (./) with the following:

# Configuration for MCP Solana DEX Sub-project

# Solana RPC Endpoint (use the same as the main project or specify a different one)
RPC_ENDPOINT="http://localhost:8899"

# Path to the order book data file (relative to this directory)
ORDER_BOOK_FILE="data/order_book.json"

# Optional: Define the token mint address if needed globally
# TOKEN_MINT_ADDRESS="TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"

Usage

This server is intended to be run as a separate process from the main ICO server.

  1. Ensure Dependencies: Make sure dependencies are installed (likely managed by the parent project’s poetry install).

  2. Navigate to Parent Directory: Open your terminal in the main project root.

  3. Start the DEX Server:

    poetry run python mcp_solana_dex/server.py
    
  4. Interact: Use an MCP client connected to the standard input/output of this process.

MCP Tools

  • create_order: Creates a new sell order.
    • ico_id: (String) The ID of the ICO for the token.
    • amount: (Integer) Amount of tokens to sell (base units).
    • price: (Float) Price per token in SOL.
    • owner: (String) Public key of the seller.
  • cancel_order: Cancels an existing order.
    • ico_id: (String) The ID of the ICO.
    • order_id: (String) The unique ID of the order to cancel.
    • owner: (String) Public key of the seller (must match order).
  • execute_order: Performs pre-condition checks for executing a sell order and updates the internal order book if checks pass. Does not execute the on-chain swap.
    • ico_id: (String) The ID of the ICO.
    • order_id: (String) The ID of the order to buy from.
    • buyer: (String) Public key of the buyer.
    • amount: (Integer) Amount of tokens to buy (base units).
    • token_mint_address: (String) Mint address of the token.
    • token_decimals: (Integer) Decimals of the token.
    • Note: Clients must construct and submit the actual atomic swap transaction separately after successful pre-checks.
  • get_orders: Retrieves the current sell orders for an ICO.
    • ico_id: (String) The ID of the ICO.
    • limit: (Integer, optional) Max orders to return (default 100).

Testing

This project uses pytest for integration testing. The tests primarily call the server’s tool functions directly, mocking necessary external interactions (like Solana RPC calls) to verify the server’s internal logic and state management.

  1. Install Development Dependencies:
    Make sure you have the main dependencies installed, then install the development dependencies which include pytest and pytest-asyncio:

    # Navigate to the project root directory (where pyproject.toml is)
    poetry install --with dev
    
  2. Run Tests:
    Execute pytest from the project root directory:

    poetry run pytest
    

    Pytest will automatically discover and run the tests located in the tests/ directory.

Future Considerations

  • Client-Side Atomic Swaps: Ensure clients interacting with this server implement secure, atomic order execution (combining SOL payment and token transfer) using appropriate Solana transaction construction. The server only performs pre-checks.
  • Database Persistence: Replace file storage with a database (e.g., SQLite, PostgreSQL) for better scalability and reliability.
  • Buy Orders: Add support for creating and matching buy orders.
  • Error Handling: Improve validation and error handling.
  • Testing: Add comprehensive unit and integration tests.

Tools

No tools

Comments

Recommend MCP Servers

View All MCP Servers