How do I install Openmm?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Openmm need an API key?

No required environment variable is listed on this record.

What transport does Openmm use?

Openmm runs locally over stdio.

When was Openmm last checked?

Last checked 2026-11-09. AI-native crypto trading MCP server — market data, orders, grid strategies & DeFi

Openmm MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @qbtlabs/[email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add io.github.adacapo21-openmm-mcp -- npx -y @qbtlabs/openmm-mcp@1.0.5

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.adacapo21-openmm-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "@qbtlabs/[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.0.5
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

@qbtlabs/openmm-mcp

📚 Documentation · 🤖 AI Skills Portal · 🔌 API Reference

MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents via any MCP client.

Two Ways to Use

Option	Best For	API Keys	Payments
Local (npm)	Full control, your own keys	Encrypted vault	Free
Hosted (mcp.openmm.io)	No setup, pay-per-use	Not needed for public data	x402 USDC

Local Setup

Prerequisites: Node.js 20 or later.

1. Install and configure

npm install -g @qbtlabs/openmm-mcp
openmm-mcp --setup

The setup wizard writes the correct MCP config for your client (Claude Desktop, Claude Code, Cursor, Windsurf). No credentials are stored in config files — only the socket path.

2. Initialize encrypted vault

openmm-init

This creates an encrypted vault at ~/.openmm/vault.enc containing your wallet key and exchange API credentials. You'll set a password, generate (or import) a wallet, and optionally add exchange keys.

3. Start the server

openmm serve

Type your vault password once. The unified socket starts at /tmp/openmm.sock — all MCP clients connect here. No credentials exist in any config file.

Manual configuration

If you prefer to edit config files directly instead of using --setup:

Client	Config file
Claude Desktop	`~/Library/Application Support/Claude/claude_desktop_config.json`
Claude Code	`~/.claude.json`
Cursor	`.cursor/mcp.json`
Windsurf	`~/.codeium/windsurf/mcp_config.json`

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

Replace /path/to/openmm-mcp with the actual install path. For Claude Desktop, use the full path to node (e.g. from which node) to avoid nvm/PATH issues.

Tip: Run openmm-mcp --setup instead — it writes the correct absolute paths automatically.

No API keys. No private keys. No passwords. Just the socket path.

Without vault (quick start)

You can skip the vault and pass API keys directly in the env block:

{
  "mcpServers": {
    "openmm": {
      "command": "npx",
      "args": ["@qbtlabs/openmm-mcp"],
      "env": {
        "MEXC_API_KEY": "your_key",
        "MEXC_SECRET": "your_secret"
      }
    }
  }
}

The vault strengthens every scenario — nothing sensitive exists in any config file, process environment, or client memory.

Client compatibility

Client	Without vault	With vault
Claude Desktop	API keys in env	Only `OPENMM_SOCKET`
Claude Code	API keys in env	Only `OPENMM_SOCKET`
Cursor	API keys in env	Only `OPENMM_SOCKET`
Windsurf	API keys in env	Only `OPENMM_SOCKET`

All clients connect to the same running openmm serve — one vault, one socket, any client.

Hosted Server with x402 Payments

Connect to mcp.openmm.io — no local installation needed for public data. Pay per tool call with USDC on Base.

How it works

AI Agent (Claude / Cursor / Windsurf)
│  MCP stdio — no keys in config
▼
MCP Client Process
(reads OPENMM_SOCKET — credentials never here)
│  Unix socket /tmp/openmm.sock (mode 0600)
▼
openmm serve — unified vault process
┌──────────────────────────────────┐
│  ~/.openmm/vault.enc             │
│  AES-256-GCM + PBKDF2           │  ← wallet key + exchange keys, one vault
│            │                     │
│  Policy Engine                   │  ← maxPerTx, maxPerDay, allowedChains
│  (checked before key is touched) │
│            │                     │
│  signAndWipe()                   │  ← key used inline, wiped from memory
└──────────────────────────────────┘
│  EIP-3009 signature only
▼
mcp.openmm.io → x402 verification → Base L2 settlement

Security properties

Property	How
Keys encrypted at rest	AES-256-GCM + PBKDF2 in `~/.openmm/vault.enc`
Keys never in client memory	MCP process only holds socket path
Keys never in config files	No API keys, no private keys anywhere in config
Process isolation	Signing happens in `openmm serve`, not in the AI agent process
Policy enforcement	Spending limits checked before private key is accessed
Memory safety	`signAndWipe()` — key used once, goes out of scope immediately

Payment flow

Agent calls a tool
Server returns 402 Payment Required with price
openmm serve signs EIP-3009 authorization (gasless — no ETH needed)
Server submits payment on-chain and returns data

Tool Pricing

Category	Tools	Price (USDC)
Free	`list_exchanges`	$0.00
Read	`get_ticker`, `get_orderbook`, `get_trades`, `get_ohlcv`, `get_balance`, `list_orders`, `get_cardano_price`, `discover_pools`, `get_strategy_status`	$0.001
Write	`create_order`, `cancel_order`, `cancel_all_orders`, `start_grid_strategy`, `stop_strategy`	$0.01

Available Tools (15)

Tool	Description	Parameters
Market Data
`list_exchanges`	List supported exchanges	—
`get_ticker`	Real-time price, bid/ask, spread, volume	`exchange`, `symbol`
`get_orderbook`	Order book depth (bids/asks)	`exchange`, `symbol`, `limit?`
`get_trades`	Recent trades with buy/sell summary	`exchange`, `symbol`, `limit?`
`get_ohlcv`	OHLCV candlestick data	`exchange`, `symbol`, `timeframe?`, `limit?`
Account
`get_balance`	Account balances (all or filtered)	`exchange`, `asset?`
`list_orders`	Open orders (all or by symbol)	`exchange`, `symbol?`
Trading
`create_order`	Place limit or market order	`exchange`, `symbol`, `type`, `side`, `amount`, `price?`
`cancel_order`	Cancel order by ID	`exchange`, `symbol`, `orderId`
`cancel_all_orders`	Cancel all orders for a pair	`exchange`, `symbol`
Cardano DEX
`get_cardano_price`	Aggregated token price from DEXes	`symbol`
`discover_pools`

CLI Reference

Setup & Server

Command	Description
`openmm-init`	Create vault, generate/import wallet, add exchanges
`openmm-init --import <key>`	Create vault with an existing private key
`openmm serve`	Unlock vault, start unified socket
`openmm-status`	Show vault, socket, wallet, and exchange status (no password)

Exchange Credentials

Command	Description
`openmm-exchange list`	List configured exchanges
`openmm-exchange add <id>`	Add exchange credentials
`openmm-exchange remove <id>`	Remove exchange credentials

Supported exchanges: mexc, gateio, bitget, kraken, binance, coinbase, okx

Wallet

Command	Description
`openmm-wallet info`	Show wallet address and chain
`openmm-wallet set`	Set wallet credentials
`openmm-wallet export`	Display private key (requires confirmation)

Spending Policy

Command	Description
`openmm-policy show`	Show current policy
`openmm-policy set max-per-tx <amount>`	Max USDC per transaction
`openmm-policy set max-per-day <amount>`	Max USDC per day
`openmm-policy set allowed-chains <chains>`	Comma-separated chain IDs
`openmm-policy reset`	Clear all policy limits

Advanced

Command	Description
`openmm-vault info`	Show vault metadata
`openmm-vault change-password`	Change vault password
`openmm-vault export`	Export all credentials (dangerous)
`openmm-vault destroy`	Delete the vault

Example Usage

Check BTC price:

"Get me the BTC/USDT ticker on MEXC"

Place an order:

"Buy 0.1 ETH at $2400 on Kraken"

Start grid strategy:

"Start a grid strategy on MEXC for INDY/USDT between $0.10 and $0.15 with 10 levels and $500 total"

Check Cardano token:

"What's the current price of SNEK on Cardano DEXes?"

Security

Vault: AES-256-GCM encrypted at ~/.openmm/vault.enc
Password: Interactive terminal only — never in any config file, env var, or CLI flag
Socket: /tmp/openmm.sock mode 0600 — the socket is the authentication boundary
Policy: Spending limits enforced at the socket before the private key is touched
Isolation: Private key never enters any MCP client process memory — signing happens in the openmm serve process via IPC

Development

git clone https://github.com/QBT-Labs/openMM-MCP.git
cd openMM-MCP
npm install
npm run typecheck
npm run lint
npm test
npm run build

Resources

OpenMM SDK — Underlying trading SDK
x402 Package — Payment integration
MCP Specification — Model Context Protocol docs
Base Network — L2 for USDC payments

License

MIT

Hosted deployment

A hosted deployment is available on Fronteir AI.