Run existing xtquant-based trading strategy code against miniQMT with minimal code changes.
Bridge a web control panel to one or more QMT terminals for market data and trade requests.
Manage multiple QMT terminals from one place by mapping trading accounts to separate bridge endpoints.
| 95ge/cfquant | aevella/sky-pc-mcp-companion | alicankiraz1/gemma-4-31b-mtp-vllm-server | |
|---|---|---|---|
| Stars | 26 | 26 | 26 |
| Language | Python | Python | Python |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 3/5 | 3/5 | 4/5 |
| Audience | developer | vibe coder | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires a Windows machine running QMT, plus copying specific files into the QMT Python strategy directory.
cfquant is a bridge tool for QMT, a stock trading platform used in China. It connects a web control panel, external Python programs, and QMT trading strategy scripts, forwarding market data subscriptions, trade requests, account lookups, and callback events between them. Its main purpose is to let the lighter miniQMT version behave like the full QMT xtquant interface, so existing trading code written against xtquant can keep working with only small import changes. To set it up, you download the source, unzip it to a folder, and run a start script on Windows, which launches a local server and opens a web control panel in the browser. From there you use a binding page to link your QMT accounts to the bridge. Separately, you copy a handful of specific files and folders into your QMT Python strategy directory and load two of them inside QMT itself, one for regular use and one described as a low latency trading entry point. External Python programs that want to use cfquant as a drop in replacement for xtquant install it locally, since it is not yet published to a package index, either with an editable pip install from the source folder or by copying its two core folders directly into a Python environment. Code that previously imported from xtquant can then import the same functions from cfquant instead, or alias the whole import so existing code barely changes. A configure function, or equivalent environment variables, lets you point the bridge at a different host, port, or token if you are not using the defaults. The project supports multiple QMT terminals at once by giving each one its own bridge identifier, with accounts mapped to bridges through the web console. It also has a basic update mechanism that pulls new code from GitHub or a zip file while keeping a couple of backups so a bad update can be rolled back. The README does not mention what license the project is released under.
A local bridge that lets miniQMT trading scripts work like the full QMT trading interface, connecting a web console, Python code, and QMT strategies.
Mainly Python. The stack also includes Python, QMT, xtquant.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.