Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Step-by-step guide to configure exchange API credentials for OpenMM.
Step-by-step guide to configure exchange API credentials for OpenMM.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Interactive guide for configuring exchange API credentials in OpenMM.
Use this skill when: Setting up OpenMM for the first time Adding a new exchange Troubleshooting connection issues
ExchangeMin OrderCredentials RequiredMEXC1 USDTAPI key + SecretGate.io1 USDTAPI key + SecretBitget1 USDTAPI key + Secret + PassphraseKraken5 EUR/USDAPI key + Secret
Guide user to the exchange's API management page: MEXC: https://www.mexc.com/ucenter/api Gate.io: https://www.gate.io/myaccount/apikeys Kraken: https://www.kraken.com/u/security/api Bitget: https://www.bitget.com/account/newapi
Required permissions for each exchange: MEXC: Enable Spot Trading Enable Reading Disable Withdrawals (safety) IP whitelist recommended Gate.io: Spot Trade Spot Read No Withdraw permission IP whitelist recommended Kraken: Query Funds Query Open Orders & Trades Create & Modify Orders No Withdraw permission Bitget: Trade Read Only No Transfer permission Note the Passphrase โ it is set when creating the API key
OpenMM uses environment variables for credentials. Add them to your .env file or export in your shell: # MEXC export MEXC_API_KEY="your_mexc_api_key" export MEXC_SECRET="your_mexc_secret_key" # Gate.io export GATEIO_API_KEY="your_gateio_api_key" export GATEIO_SECRET="your_gateio_secret_key" # Bitget (requires passphrase) export BITGET_API_KEY="your_bitget_api_key" export BITGET_SECRET="your_bitget_secret_key" export BITGET_PASSPHRASE="your_bitget_passphrase" # Kraken export KRAKEN_API_KEY="your_kraken_api_key" export KRAKEN_SECRET="your_kraken_secret_key" Or create a .env file in the project root: MEXC_API_KEY=your_mexc_api_key MEXC_SECRET=your_mexc_secret_key GATEIO_API_KEY=your_gateio_api_key GATEIO_SECRET=your_gateio_secret_key BITGET_API_KEY=your_bitget_api_key BITGET_SECRET=your_bitget_secret_key BITGET_PASSPHRASE=your_bitget_passphrase KRAKEN_API_KEY=your_kraken_api_key KRAKEN_SECRET=your_kraken_secret_key
Test that credentials work by checking balances: # MEXC openmm balance --exchange mexc # Gate.io openmm balance --exchange gateio # Bitget openmm balance --exchange bitget # Kraken openmm balance --exchange kraken
Confirm market data access: openmm ticker --exchange mexc --symbol BTC/USDT openmm orderbook --exchange kraken --symbol ADA/EUR --limit 5
To use OpenMM as an MCP server, add to your MCP client config: { "mcpServers": { "openmm": { "command": "npx", "args": ["@qbtlabs/openmm-mcp"], "env": { "MEXC_API_KEY": "your_key", "MEXC_SECRET": "your_secret", "KRAKEN_API_KEY": "your_key", "KRAKEN_SECRET": "your_secret" } } } } Only include env vars for exchanges you want to use.
Verify environment variables are set: echo $MEXC_API_KEY Check .env file is in the correct directory Ensure variable names match exactly (e.g. MEXC_SECRET not MEXC_SECRET_KEY)
Verify all three vars: BITGET_API_KEY, BITGET_SECRET, BITGET_PASSPHRASE The passphrase is set when creating the API key on Bitget
Verify KRAKEN_API_KEY and KRAKEN_SECRET Check key permissions on Kraken API settings page
System clock may be out of sync Run: sudo ntpdate time.google.com
Reduce request frequency Check exchange's rate limit docs
Never enable withdrawals โ trading doesn't need it Use IP whitelisting โ restrict to your server's IP Never commit .env files โ add .env to .gitignore Rotate keys periodically โ every 90 days recommended Use separate keys for testing โ don't mix testnet/mainnet
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.