Orderly Network MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port the server will start on when running in HTTP mode. Default is 3000. | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_orderly_docsC | Search Orderly Network documentation for specific topics, concepts, or questions |
| get_contract_addressesB | Get smart contract addresses for Orderly on specific chains |
| explain_workflowC | Get step-by-step explanation of common Orderly development workflows |
| get_api_infoC | Get information about Orderly REST API endpoints or WebSocket streams |
| get_indexer_api_infoB | Get information about Orderly Indexer API for trading metrics, account events, trades, and volume statistics (rankings endpoints available via endpoint search) |
| get_component_guideC | Get guidance on building React UI components using Orderly SDK |
| get_orderly_one_api_infoB | Get information about Orderly One API for DEX creation, graduation, and management |
| get_strategy_vault_api_infoC | Get information about Orderly Strategy Vault API for yield optimization, strategy providers, and liquidity providers |
| get_public_info_api_infoA | Get information about the Orderly Public Info API — a zero-auth single endpoint (POST /v1/public/query) for market, account, and platform data via a |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Orderly Network Overview | High-level protocol architecture and key concepts |
| SDK Hooks Reference | Complete reference of all v2 SDK hooks |
| Component Building Guides | Guides for building UI components with Orderly SDK |
| Contract Addresses | Smart contract addresses across all supported chains |
| Common Workflows | Step-by-step workflows for common development tasks |
| REST API Reference | Complete REST API documentation |
| WebSocket API Reference | Real-time WebSocket streams documentation |
| Indexer API Reference | Indexer API for trading metrics, account events, trades, and volume statistics (rankings endpoints available via endpoint search) |
| Public Info API Reference | Zero-auth single-endpoint query API (POST /v1/public/query) for market, account, and platform data via a `type` field |
TDQS
Scored across 9 tools
Most tools target clearly distinct areas: contract addresses, workflows, React components, and several named APIs. However, search_orderly_docs overlaps with the specialized informational tools, and the multiple get_*_api_info tools can be hard to distinguish without knowing which API hosts the needed endpoint.
All tool names use consistent snake_case and follow a predictable verb_noun pattern (get_*, search_*, explain_*). The repeated get_*_api_info suffix is stable and readable rather than chaotic.
Nine tools is well scoped for a documentation and guidance server covering multiple Orderly APIs and workflows. Each tool appears to earn its place without excessive fragmentation.
The surface covers contract addresses, docs search, workflows, REST/WebSocket info, Indexer, Public Info, Orderly One, Strategy Vault, and React component guidance. Minor gaps remain, such as a general SDK/hooks reference or troubleshooting tool, but core developer needs are addressed.