qlib-sync

中文说明

Website: randyy179.github.io/qlib-sync

One command to install and keep current a local Qlib China A-share dataset, and an MCP server so AI assistants can read it.

pip install qlib-sync
qlib-sync cn update

Or without installing anything first: uvx --python 3.12 qlib-sync cn update. (--python 3.12 because pyqlib publishes wheels up to Python 3.12; uv fetches that Python for you if needed. With pip, use Python 3.10 to 3.12.)

That installs the daily community release from chenditc/investment_data into ~/.qlib/qlib_data/cn_data, the location Qlib reads by default. Run the same command again any time; when the data is already current it finishes in about a second.

Why not just wget and tar?

Qlib's README points A-share users to the community release with a wget and tar one-liner. That works until it doesn't:

• An interrupted or truncated download extracts into a half-written dataset, or fails after the old one has already been overwritten.
• Upstream republishes releases. In November 2026 a data error was found and corrected (investment_data#163) and releases were republished under the same date. A date check alone never sees the fix.
• Every check downloads 550 MB, even when nothing changed.

The investment_data README itself describes a careful manual process: download the release manifest, check the archive with its validate_archive.py, then extract. qlib-sync runs the same checks automatically on every update and adds what a manual process cannot: it skips the download when nothing changed, extracts beside the live data and swaps it in with rollback (rather than extracting on top of the existing folder), and picks up republished releases.

qlib-sync treats the dataset like a production system:

The checks catch broken, truncated, or tampered packages. They cannot catch wrong values inside a correctly published release (lik

... View full README on GitHub