wallex

This WALLEX MCP Server exposes a set of tools and resources to interact with the Wallex trading API. Tools include place_order, cancel_order, and get_balance, enabling you to place and cancel orders as well as fetch account balances. Resources such as market_data, order_status, and instruments provide real-time market information, order tracking, and instrument metadata. The server is wired in a flow where a client (wallex_mcp.client) communicates with the Wallex REST API, and responses are validated and structured by wallex_mcp.schemas before being returned to the caller.

To use the server locally, run the development or production entry points provided. The development mode starts a FastMCP instance using the server module directly for rapid iteration, while the production mode wraps the same server with mcpo for a managed deployment that supports API key authentication and a persistent port. The tools and resources can be invoked from your MCP client to perform trading operations and query market data, with results flowing through the client wrapper and schema validation layers.

Prerequisites:

• Python 3.8+
• pip (or virtualenv)
• internet access to install dependencies

Installation steps:

1. Clone the repository or download the project folder.
2. Create and activate a virtual environment (recommended):
   • python -m venv venv
   • source venv/bin/activate # on macOS/Linux
   • .\venv\Scripts\activate # on Windows
3. Install dependencies:
   • pip install -r wallex_mcp/requirements.txt
4. Configure environment variables (see mcp_config.env examples below).
5. Run in development or production mode (examples shown):

Development (local fastmcp integration):

• python wallex_mcp/server.py

Production (via mcpo wrapper):

• mcpo --port 8001 --api-key "your-api-key" -- fastmcp run wallex_mcp/server.py

Environment variable examples:

• API_KEY=your-wallex-api-key
• WALLEX_API_BASE_URL=https://api.wallex.example
• PORT=8001
• LOG_LEVEL=INFO

Tips and common issues:

• Ensure your Wallex API credentials and base URL are correctly configured in environment variables before starting the server.
• If you see connection errors, verify network access to the Wallex API endpoints and that the API key has the necessary permissions.
• When running in production with mcpo, the --api-key flag should match the API key configured on the Wallex side if required by the deployment setup.
• The server relies on the wallex_mcp.schemas module to validate responses; if you modify schemas, restart the server to pick up changes.
• If you use Docker or other containerized environments, map the port specified in PORT and forward API requests appropriately.
• The available tools are: place_order, cancel_order, get_balance; resources: market_data, order_status, instruments.