asterdex

The aster-mcp-server provides a comprehensive MCP server for Aster DEX perpetual futures, exposing real-time market data, trading capabilities, risk management, and automation tools to Claude and other MCP-compatible AIs. It bundles 56 tools across market data, perpetual and spot trading, account & risk, VPVR analytics, scanners, Binance intelligence, QFL signals, strategy automation, grid engine, and infrastructure controls, enabling end-to-end interaction with Aster DEX from analysis to live order execution. To use it, configure the server with your Aster API credentials and run the server so that MCP clients can connect and invoke the available tools. Common usage includes querying market data via get_market_data, placing and managing perpetual orders with execute_order and manage_orders, and running automated strategies through grid_start or start_strategy, among many other capabilities described in the Tools Reference.

Once running, you can connect Claude (or your MCP client) to the server by pointing your MCP configuration at the node-based server path and exporting your Aster API credentials. The server will expose the full suite of tools under the mcpServers section you configured (e.g., aster) and will handle requests such as market data queries, order execution, risk checks, VPVR analytics, and automated strategies.

Prerequisites:

• Node.js 20+
• pnpm (npm install -g pnpm)
• An Aster DEX account with API key/secret

Install and build:

git clone https://github.com/tyranosurasmax/asterdex-mcp-server.git
cd asterdex-mcp-server
pnpm install
pnpm run build

Configure credentials (example):

cp .env.example .env
# Edit .env with your Aster API key and secret (or set env vars accordingly)

Run the server locally (example):

node dist/mcp-server.js
# or use a process manager to keep it running

If you’re integrating with Claude or other MCP clients, ensure your mcp_config points to the built server path and includes the required environment variables for Aster API access as shown in the mcp_config example.

Tips and notes:

• Ensure Node.js 20+ is installed and pnpm is available for building the project.
• The server expects Aster API credentials; store them securely and do not commit them to source control.
• The provided mcp_config example uses placeholder paths; replace /path/to/asterdex-mcp-server/dist/mcp-server.js with the actual built path on your system.
• If you plan to run Claude integration, update the JSON config in Claude Desktop, Claude Code, or OpenCode with your actual API keys and the correct path to dist/mcp-server.js.
• When upgrading, re-run pnpm install and pnpm run build to ensure the MCP server is up to date with the latest code.
• Monitor logs for API connectivity issues or rate limits from Aster DEX; consider handling retries and backoffs in your MCP client configuration.
• For production deployments, use a process manager (e.g., pm2, systemd) and consider containerization if your environment requires isolation.