coindcx-mcp-server

A minimal MCP (Model Context Protocol) server written in Rust that exposes your CoinDCX futures wallet balance as a tool to Claude Desktop.

What is an MCP Server?

MCP (Model Context Protocol) is an open standard that lets AI models like Claude interact with external tools and data sources. Instead of Claude only knowing what's in its training data, an MCP server lets you expose real-time data and actions — like fetching your live account balance — directly into a Claude conversation.

Think of it as a plugin system for Claude: you write a server that defines "tools", and Claude can call those tools on your behalf during a conversation.

How It Works

Claude Desktop  ──►  MCP Protocol (stdin/stdout)  ──►  coindcx-mcp-server  ──►  CoinDCX API
                ◄──                                ◄──                      ◄──

1. Claude Desktop spawns your binary as a subprocess
2. Claude and the server communicate over stdin/stdout using the MCP protocol
3. When you ask Claude about your balance, it calls the get_futures_wallet_balance tool
4. The server makes an authenticated request to the CoinDCX API and returns the result
5. Claude reads the response and presents it to you in the conversation

What This Project Includes

That's it — intentionally simple. This is a working foundation you can extend with more tools (place orders, get positions, etc.).

Prerequisites

• Rust (stable)
• A CoinDCX account with API access enabled
• Claude Desktop

Clone and Run

1. Clone the repository

git clone https://github.com/your-username/coindcx-mcp-server.git
cd coindcx-mcp-server

2. Create your .env file

cp .env.example .env

Edit .env and fill in your CoinDCX API credentials:

COINDCX_API_KEY=your_api_key_here
COINDCX_API_SECRET=your_api_secret_here

You can generate API keys from your CoinDCX API settings.

3. Build the release binary

cargo build --release

The binary will be at target/release/coindcx-mcp-server.

4. Test it locally (optional)

cargo run --release

The server will start and wait for MCP messages on stdin. You won't see any output — that's expected. Kill it with Ctrl+C.

Claude Desktop Setup

Locate your config file

Option A — Recommended: use cwd to load .env automatically

This keeps your API keys out of the config file. The server reads them from .env at startup.

{
  "mcpServers": {
    "coindcx": {
      "command": "/absolute/path/to/coindcx-mcp-server/target/release/coindcx-mcp-server",
      "cwd": "/absolute/path/to/coindcx-mcp-server"
    }
  }
}

Replace /absolute/path/to/coindcx-mcp-server with the actual path on your machine. For example on macOS:

{
  "mcpServers": {
    "coindcx": {
      "command": "/Users/yourname/projects/coindcx-mcp-server/target/release/coindcx-mcp-server",
      "cwd": "/Users/yourname/projects/coindcx-mcp-server"
    }
  }
}

Option B — Use cargo run (no separate build step)

Convenient during development. Cargo will recompile if needed and the .env is picked up automatically.

{
  "mcpServers": {
    "coindcx": {
      "command": "/Users/yourname/.cargo/bin/cargo",
      "args": [
        "run",
        "--release",
        "--manifest-path",
        "/Users/yourname/projects/coindcx-mcp-server/Cargo.toml"
      ]
    }
  }
}

Note: If cargo isn't found, use its full path. Run which cargo in your termin

... View full README on GitHub