0xAuto OKX MCP Server

Created By
Buidl-Landa year ago
Overview

What is 0xAuto OKX MCP Server?

0xAuto OKX MCP Server is a server that provides a tool interface layer for the OKX V5 API and OKX DEX API, enabling AI agents to access functionalities of both centralized and decentralized exchanges seamlessly.

How to use 0xAuto OKX MCP Server?

To use the server, install the necessary dependencies, set up your environment variables with your OKX API credentials, and run the server using Node.js. The server will start and listen for requests on the specified port.

Key features of 0xAuto OKX MCP Server?

  • Simplified access to OKX exchange functionalities through standardized MCP tool interfaces.
  • Centralized Exchange (CEX) features including account management, market data retrieval, and trading operations.
  • Decentralized Exchange (DEX) features such as token exchanges, multi-chain transactions, and on-chain balance queries.
  • Standardized JSON responses and error handling for easier integration.

Use cases of 0xAuto OKX MCP Server?

  1. Automating trading strategies on OKX CEX.
  2. Building AI agents that interact with OKX DEX for token swaps.
  3. Developing applications that require real-time market data from OKX.

FAQ from 0xAuto OKX MCP Server?

  • What are the system requirements?

Node.js (v16 or higher) and pnpm are required to run the server.

  • How do I set up my API credentials?

Create a .env file and fill in your OKX API key, secret key, and passphrase as instructed in the installation steps.

  • Can I use this server for both CEX and DEX functionalities?

Yes! The server supports both centralized and decentralized exchange functionalities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Buidl-Land
Star
0
Language
JavaScript
License
-
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago