# orderly-mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/OrderlyNetwork/orderly-mcp  
**GitHub Stars:** 10  
**npm Downloads (last month):** 2408  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/orderly-mcp

## Description
MCP Server for Orderly Network - Documentation and SDK patterns

## Tools
Capabilities this server exposes over MCP:

- **deposit** — Approve and deposit through the Vault contract
- **withdraw** — Sign the EIP-712 withdrawal and submit it
- **Events** — Account events with pagination (`/events_v2`) - trades, settlements, liquidations, transactions
- **Trades** — Trade data with filters (`/trades`)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "orderly-mcp": {
    "command": "npx",
    "args": ["-y","@orderly.network/mcp-server"]
  }
}
```

## Documentation

## What orderly-mcp does

orderly-mcp gives AI assistants a structured way to consult Orderly Network development material for omnichain perpetual futures applications. It covers architecture, concepts, REST and WebSocket APIs, SDK v2 hooks and symbols, supported-chain contract addresses, common implementation workflows, and React trading components.

The server is aimed at developers integrating Orderly rather than traders looking for a general market assistant. Its workflow guidance covers connecting a wallet and creating an Orderly key, placing an initial trade, depositing USDC or other tokens, configuring take-profit and stop-loss settings, and managing subaccounts. Indexer references include trading metrics, account events, volume statistics, trades, and ranking endpoints.

## How it works

The MCP interface exposes focused tools for documentation lookup and implementation guidance. `search_orderly_docs` accepts a topic or question and can surface SDK hooks, types, components, and functions. `get_contract_addresses` returns address information by chain, contract type, and mainnet or testnet network. `explain_workflow` provides step-by-step material for a named development task.

API-oriented tools separate core API references from indexer references. `get_api_info` handles REST, WebSocket, and authentication information, while `get_indexer_api_info` can search endpoint names or filter categories such as trading metrics and events. `get_component_guide` describes supported React UI patterns at minimal, standard, or advanced complexity. The server also includes an Orderly One API information tool for DEX creation, graduation, and management endpoints.

## Setup and configuration

The recommended installation uses the package CLI:

```bash
npx @orderly.network/mcp-server init --client cursor
```

The initializer creates the relevant client configuration and installs the package as a development dependency. Supported setup targets include Claude Code, Cursor, VS Code with Copilot, Codex, and OpenCode. Manual local configurations can run the package through `npx @orderly.network/mcp-server@latest`.

Local development requires Node.js 18 or newer and Yarn or npm. From a source checkout, install dependencies and build with `yarn install` followed by `yarn build`. The default process uses stdio. For remote access, `yarn start:http` serves MCP over HTTP on port 3000 unless `PORT` changes it; the health endpoint is `/health`. Docker can run the server in stateless HTTP mode. A hosted endpoint is available at `https://mcp.orderly.network`.

## Tools and capabilities

- Search Orderly documentation by topic, concept, or question.
- Find contract addresses for Ethereum, Arbitrum, Optimism, Base, Mantle, Solana, and Orderly L2.
- Retrieve REST, WebSocket, authentication, and indexer API references.
- Explore account events, trades, fees, volume, and ranking endpoints.
- Get implementation workflows for wallets, orders, deposits, risk settings, and subaccounts.
- Generate guidance for TradingPage, OrderBook, OrderEntry, Positions, and wallet connector components.

## Limitations and notes

The documented workflow and component tools provide explanations and code patterns for integrating Orderly SDK and APIs. Local HTTP deployments listen on port 3000 by default, while stdio is intended for local MCP clients. The hosted endpoint uses Streamable HTTP configuration rather than a local process.

_Full upstream README: https://allmcps.com/mcp/orderly-mcp/readme_