Setup Guide

Vault-based setup — your credentials never leave your machine.

Security Model

• All credentials stored in an AES-256-GCM encrypted vault on your machine
• Vault password is typed once in the terminal, never stored anywhere
• MCP clients connect via a local IPC socket — no API keys in config files
• Policy enforcement happens at the socket before any key is touched

Setup in 4 Steps

Install

Install the OpenMM package globally

npm install -g @qbtlabs/openmm-mcp

Create Vault

Run the one-time setup wizard to create your encrypted vault, generate a wallet, and add exchange credentials

openmm-init

Start Server

Start the unified MCP server — run this before launching any AI client

openmm serve

Configure Client

Write the MCP config for your AI client (Claude, Cursor, Windsurf, etc.)

openmm-mcp --setup

Client Config Reference

openmm-mcp --setup writes this automatically. Shown here for reference.

~/.claude.json

{
  "mcpServers": {
    "openmm": {
      "type": "stdio",
      "command": "node",
      "args": [
        "<openmm-mcp-path>/dist/index.js"
      ],
      "env": {
        "MCP_TRANSPORT": "stdio",
        "OPENMM_SOCKET": "/tmp/openmm.sock",
        "PAYMENT_SERVER": "https://mcp.openmm.io",
        "X402_TESTNET": "true"
      }
    }
  }
}

Note: openmm-mcp --setup detects your node and package paths automatically and writes the correct absolute paths.

No API keys, no wallet keys in config — just the socket path and payment server. Credentials stay in the vault.

Managing Credentials

Exchange credentials live inside your encrypted vault. Use the CLI to manage them:

List configured exchanges

openmm-exchange list

Add exchange credentials

openmm-exchange add mexc

Remove exchange

openmm-exchange remove gateio

See CLI Reference for all commands including wallet management, policy limits, and vault operations.

Next Steps

Quick Start

2-minute guide

MCP Setup

Client-specific guides

Browse Skills

Skill packages