MCP.so
ログイン

0xAuto OKX MCP Server

@Buidl-Land

0xAuto OKX MCP Server について

概要はまだありません

基本情報

カテゴリ

その他

ランタイム

node

トランスポート

stdio

公開者

Buidl-Land

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is 0xAuto OKX MCP Server?

0xAuto OKX MCP Server is an MCP‑compliant tool interface layer for the OKX V5 API and OKX DEX API. It provides AI agents with simplified, authenticated access to OKX exchange (CEX) and decentralized exchange (DEX) functionalities, hiding complex API signing logic behind standard MCP tools.

How to use 0xAuto OKX MCP Server?

Install dependencies with pnpm install, copy .env.example to .env, and fill in your OKX API credentials (OKX_API_KEY, OKX_SECRET_KEY, OKX_PASSPHRASE). Set SIMULATED_TRADING=0 (live) or 1 (demo). Start the server with pnpm start (or pnpm dev). MCP clients connect via /mcp, /sse, or /messages endpoints. Use the listed MCP tools (e.g., okx_get_balance, okx_place_order, okx_swap) to interact with CEX and DEX features.

Key features of 0xAuto OKX MCP Server

  • Hides OKX API authentication and signature complexity
  • Covers CEX account, market, trading, and funding operations
  • Provides DEX aggregator access for multi‑chain swaps
  • Standardized JSON responses and error handling
  • Supports MCP session management and streaming
  • Simulated trading mode for testing

Use cases of 0xAuto OKX MCP Server

  • AI agents placing orders and checking balances on OKX CEX
  • Automated portfolio management and position tracking
  • Fetching real‑time market data and K‑lines for analysis
  • Executing intra‑chain and cross‑chain token swaps via OKX DEX
  • Funding operations: deposit addresses, withdrawal history, withdrawals

FAQ from 0xAuto OKX MCP Server

What dependencies are required?

Node.js v16 or higher and pnpm are required. The server runs as a standard Node.js application.

How do I configure OKX API credentials?

Set OKX_API_KEY, OKX_SECRET_KEY, OKX_PASSPHRASE in the .env file. Ensure your API key has read and trade permissions. Optional: configure SIMULATED_TRADING for demo mode.

Which OKX data does the server access?

It accesses the OKX V5 API (CEX) and the OKX DEX API (web3.okx.com). It does not store user data locally; all data is fetched live from OKX endpoints.

Does the server support live and demo trading?

Yes. Set SIMULATED_TRADING=0 for live trading or 1 for a demo/simulated environment. This is configured in the .env file.

What transports and authentication are used?

The server communicates over HTTP (port 3000 by default) using standard MCP endpoints. OKX authentication is handled internally via API key, secret, and passphrase; no additional auth layer is exposed to the MCP client.

コメント

「その他」の他のコンテンツ