Developer integration guide

Integrate an MCP Server with Claude Desktop

Claude Desktop can call external tools through the Model Context Protocol. With OpenMM MCP, Claude gets structured crypto trading tools for tickers, order books, balances, grid strategy previews, and order execution when enabled.

Install / configuration example

{
  "mcpServers": {
    "openmm": {
      "command": "npx",
      "args": ["@qbtlabs/openmm-mcp"],
      "env": {
        "OPENMM_EXCHANGE": "kraken",
        "OPENMM_API_KEY": "your_read_only_key",
        "OPENMM_API_SECRET": "your_secret"
      }
    }
  }
}

Step-by-step setup

  1. 1. Install the server

    Run `npx @qbtlabs/openmm-mcp` once to verify the package resolves and the server starts.

  2. 2. Create exchange credentials

    Start with read-only API keys. Disable withdrawals and restrict IPs at the exchange level whenever possible.

  3. 3. Add Claude Desktop config

    Register OpenMM MCP as a stdio MCP server in Claude Desktop's MCP configuration file.

  4. 4. Test read-only tools

    Ask Claude for a ticker, order book snapshot, or account-balance summary before enabling any order permissions.

  5. 5. Enable trading carefully

    Only after dry-runs are correct, add order permissions with small limits and external monitoring.

Safety checklist

  • • Start with read-only API keys.
  • • Disable withdrawals on every exchange key.
  • • Use test/sandbox accounts or tiny balances for first live runs.
  • • Keep API keys in environment variables, never prompts or chat history.
  • • Log every tool call and execution result.

FAQ

Can Claude Desktop place real crypto orders?

Yes, if the MCP server is configured with exchange API keys that have order permissions. Start read-only, then add trading permissions only after dry-run testing.

Is OpenMM MCP required to use Claude for trading?

Claude needs a tool layer to access exchanges. OpenMM MCP provides that layer through the open Model Context Protocol.

Related docs and resources