← Back to Docs

MCP Setup Guide

Connect OpenMM to your favorite AI client

What is MCP?

The Model Context Protocol (MCP) is an open standard that allows AI agents to connect to external tools and data sources. OpenMM provides an MCP server that gives your agent access to trading tools across multiple exchanges.

Choose Your Client

Claude Desktop supports MCP servers via the claude_desktop_config.json file.

1. Locate your config file

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add the OpenMM server

claude_desktop_config.json
{
  "mcpServers": {
    "openmm": {
      "command": "npx",
      "args": ["-y", "@qbt-labs/openmm-mcp"],
      "env": {
        "MEXC_API_KEY": "your-api-key",
        "MEXC_SECRET": "your-secret"
      }
    }
  }
}

3. Restart Claude Desktop

After saving the config, restart Claude Desktop. You should see the OpenMM tools available in the tools panel.

Best Integration: OpenClaw provides the most seamless experience with OpenMM skills, running locally on your machine with full MCP support.

Option A: Install as a Skill (Easiest)

openclaw skills add qbt-labs/openmm

This automatically configures OpenMM and makes all tools available in your sessions.

Option B: Manual MCP Server Config

Add to your OpenClaw config file:

~/.openclaw/config.yaml
# Add to your ~/.openclaw/config.yaml

mcp_servers:
  openmm:
    command: npx
    args:
      - "-y"
      - "@qbt-labs/openmm-mcp"
    env:
      MEXC_API_KEY: your-api-key
      MEXC_SECRET: your-secret

2. Set your exchange API keys

Add to your shell profile (~/.zshrc or ~/.bashrc):

export MEXC_API_KEY="your-key" MEXC_SECRET="your-secret"

3. Restart the OpenClaw gateway

openclaw gateway restart

4. Verify it works

Ask your agent: "Get my MEXC balance" or "Show BTC/USDT price"

Run MCP Server Locally

Want full control? Clone OpenMM and run the MCP server on your own machine:

1. Clone and build

Terminal
git clone https://github.com/3rd-Eye-Labs/OpenMM.git
cd OpenMM
npm install
npm run build

2. Configure environment

Terminal
cp .env.example .env
# Edit .env with your API keys

3. Install globally

Terminal
npm install -g .
openmm --help

4. Use with any MCP client

Point your AI client to use the local openmm command instead of npx.

💡 Benefits of self-hosting: Full privacy, no external dependencies, custom modifications, faster startup time.

Exchange API Keys

To enable trading operations, you'll need to provide API keys for your exchanges. Market data tools work without authentication.

.env or shell profile
# Exchange API Keys (add to your shell profile or .env)

# MEXC
export MEXC_API_KEY="your-mexc-api-key"
export MEXC_SECRET="your-mexc-secret"

# Gate.io
export GATEIO_API_KEY="your-gateio-api-key"
export GATEIO_SECRET="your-gateio-secret"

# Bitget
export BITGET_API_KEY="your-bitget-api-key"
export BITGET_SECRET="your-bitget-secret"
export BITGET_PASSPHRASE="your-bitget-passphrase"

# Kraken
export KRAKEN_API_KEY="your-kraken-api-key"
export KRAKEN_SECRET="your-kraken-secret"

⚠️ Security Note: Never commit API keys to version control. Use environment variables or a secrets manager.

Verify Your Setup

Once configured, test that OpenMM is working by asking your agent:

"Get the BTC/USDT price on MEXC"
"Show the ETH/USDT orderbook on Gate.io"
"What are my balances on all exchanges?"

Troubleshooting

Tools not appearing?

  • • Make sure you've restarted your AI client after adding the config
  • • Check that Node.js 18+ is installed and in your PATH
  • • Verify the JSON syntax in your configuration file

Authentication errors?

  • • Verify your API keys are correct and active
  • • Check that API trading permissions are enabled on the exchange
  • • Ensure environment variables are properly exported

Still having issues?

Open an issue on GitHub or reach out on X/Twitter

Ready to Trade

Your agent now has access to 30+ trading tools across 4+ exchanges