About Wallex MCP Server
Wallex MCP Server connects MCP clients to Wallex Exchange for market data, wallet balances, and order handling. It uses FastMCP and a REST API client.
Key features
- 01Retrieve market data
- 02Check wallet balances
- 03Place orders
Use cases
- 01Review Wallex market data
- 02Check an account balance
- 03Handle exchange orders
MCP support
It exposes tools and resources through an MCP server, including `place_order`, `get_balance`, and `market_data`.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEWallex MCP Server
development
fastmcp dev wallex_mcp/server.py
production
mcpo --port 8001 --api-key "wallex-local" -- fastmcp run wallex_mcp/server.py
structure
wallex-mcp/
├── wallex_mcp/
│ ├── __init__.py
│ ├── server.py # FastMCP instantiation & run()
│ ├── config.py # Env var loader
│ ├── client.py # HTTPX wrapper
│ ├── schemas.py # Pydantic models
│ ├── tools/
│ │ ├── get_balance.py # @mcp.tool()
│ │ ├── place_order.py
│ │ └── cancel_order.py
│ └── resources/
│ ├── market_data.py # @mcp.resource("wallex://market/{symbol}")
│ ├── order_status.py # @mcp.resource("wallex://orders/{id}")
│ └── instruments.py
├── requirements.txt
├── Dockerfile
└── README.md # Project overview + Quickstart
Workflow
flowchart LR
subgraph MCP Server
A[FastMCP Instance] --> B[Tool: place_order]
A --> C[Resource: get_balance]
A --> D[Resource: market_data]
end
B --> E[wallex_mcp.client] --> F[Wallex REST API]
C --> E
D --> E
F --> G[JSON Response] --> H[wallex_mcp.schemas] --> B/C/D return
B/C/D return --> A --> I[LLM]
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.