MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents
OpenMM MCP Server (io.github.QBT-Labs/openmm-mcp)
This MCP server provides an integration layer for OpenMM by exposing tools for market data, account operations, trading, and strategy functionality to AI agents. It is packaged as an MCP server and is intended to be used by MCP clients within AI-agent workflows.
🛠️ Key Features
MCP server for OpenMM
Exposes market data tools
Provides account tools
Supports trading tools
Offers strategy tools
🚀 Use Cases
AI agents that require market data access
Agent-driven trading workflows
Agent actions that depend on account operations
Strategy execution and coordination for automated decision-making
⚡ Developer Benefits
Standardized MCP server interface for MCP clients
Tool access organized for AI-agent consumption
Open-source project focused on AI-agents and MCP interoperability
⚠️ Limitations
Only information provided is the server purpose; specific tool behaviors, inputs/outputs, and supported chains are not described here.
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
bash
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
bash
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:
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: