MQT Core - The Backbone of the Munich Quantum Toolkit (MQT)
MQT Core provides reusable C++20 and Python libraries for quantum computing: the MQT Compiler Collection, built on MLIR and LLVM, together with decision diagrams, QIR execution, QDMI device access, SDK and HPC integrations, and structured benchmarks. It forms the backbone of the Munich Quantum Toolkit (MQT).
MQT Core 4 is a major architectural release. Structured compiler representations replace the classic circuit APIs and connect quantum-classical programs to optimization, hardware mapping, and execution. For the release highlights, see the v4 overview. Existing users should start with the v3-to-v4 migration guide.
Start with your task
Install mqt.core in a Python 3.11 or newer virtual environment:
uv pip install mqt.core
For other installation options, follow the source-build instructions. Then choose a starting point:
| Task | Start here |
|---|---|
| Compile and execute a program | Factor 21 with Shor's algorithm; explore compilation and execution. |
| Connect or implement a device | Discover devices, integrate SDKs, or implement an interface. |
| Use decision diagrams | Represent states and operations in C++ or Python: DD quickstart. |
| Generate and evaluate benchmarks | Configure quantum programs and compare results with references. |
| Exchange quantum programs | Qiskit to QIR, OpenQASM, and jeff. |
| Embed or extend MQT Core | Use the C++ libraries or extend the MLIR compiler. |
Getting Started
Factor 21 with Shor's algorithm, using modular arithmetic, a reused query qubit, and measurement feedback. The callback compiles each circuit for the bundled DDSIM device and submits 64 shots through each payload format:
from mqt.core.bench import shor
from mqt.core.mlir import compile_program, submit_program
from mqt.core.qdmi import ProgramFormat, open_device
device = open_device("mqt.ddsim.default")
def run(benchmark: shor.Shor) -> dict[str, int]:
compiled = compile_program(benchmark.generate(), target=device, program_format=program_format)
job = submit_program(compiled, target=device, num_shots=64, custom1=17)
job.wait()
return job.get_counts()
for program_format in (ProgramFormat.QIR_ADAPTIVE_MODULE, ProgramFormat.QASM3):
result = shor.factor(21, run)
assert result.status == shor.FactorStatus.SUCCESS
assert result.factors == (3, 7)
print(f"{program_format.name}: {result.factors}")
QIR_ADAPTIVE_MODULE: (3, 7)
QASM3: (3, 7)
The factoring walkthrough explains the measured phase, continued fractions, and verified factor recovery.
Development
Source builds require a C++20 compiler and CMake 3.28 or newer. Building the compiler collection also requires LLVM/MLIR 23.1 or newer. Prebuilt Python wheels include the compiler and simulator. Graphviz is optional for exporting DD visualizations.
See the contribution guide for development setup and checks. For questions and suggestions, open a discussion or an issue.
Contributors and Supporters
MQT Core is developed by MQSC and the Chair for Design Automation at the Technical University of Munich. Among others, it is part of the Munich Quantum Software Stack (MQSS) ecosystem, which is being developed as part of the Munich Quantum Valley (MQV) initiative.
Thank you to all the contributors who have helped make MQT Core a reality!
The MQT will remain free, open-source, and permissively licensed — now and in the future. We are firmly committed to keeping it open and actively maintained for the quantum computing community.
To support this endeavor, please consider:
- Starring and sharing our repositories: https://github.com/munich-quantum-toolkit
- Contributing code, documentation, tests, or examples via issues and pull requests
- Citing the MQT in your publications (see Cite This)
- Citing our research in your publications (see References)
- Using the MQT in research and teaching, and sharing feedback and use cases
- Sponsoring us on GitHub: https://github.com/sponsors/munich-quantum-toolkit
Cite This
Please cite the work that best fits your use case.
MQT Core (the tool)
When citing the software itself or results produced with it, cite the MQT Core paper:
@article{burgholzer2025MQTCore,
title = {{{MQT Core}}: {{The}} Backbone of the {{Munich Quantum Toolkit (MQT)}}},
author = {Burgholzer, Lukas and Stade, Yannick and Peham, Tom and Wille, Robert},
year = 2025,
journal = {Journal of Open Source Software},
publisher = {The Open Journal},
volume = 10,
number = 108,
pages = 7478,
doi = {10.21105/joss.07478},
url = {https://doi.org/10.21105/joss.07478}
}
The MQT Compiler Collection
When citing the compilation framework built on MLIR, cite the MQT Compiler Collection paper:
@article{MQTCompilerCollection2026,
title = {The {{MQT Compiler Collection}}: {{A}} Blueprint for a Future-Proof Quantum-Classical Compilation Framework},
author = {Burgholzer, Lukas and Haag, Daniel and Stade, Yannick and Rovara, Damian and Hopf, Patrick and Wille, Robert},
year = {2026},
booktitle = {Design, Automation and Test in Europe},
doi = {10.23919/DATE69613.2026.11539504},
eprint = {2604.08674},
eprinttype = {arxiv},
}
The Munich Quantum Toolkit (the project)
When discussing the overall MQT project or its ecosystem, cite the MQT Handbook:
@inproceedings{mqt,
title = {The {{MQT}} Handbook: {{A}} Summary of Design Automation Tools and Software for Quantum Computing},
shorttitle = {{The MQT Handbook}},
author = {Wille, Robert and Berent, Lucas and Forster, Tobias and Kunasaikaran, Jagatheesan and Mato, Kevin and Peham, Tom and Quetschlich, Nils and Rovara, Damian and Sander, Aaron and Schmid, Ludwig and Schoenberger, Daniel and Stade, Yannick and Burgholzer, Lukas},
year = 2024,
booktitle = {IEEE International Conference on Quantum Software (QSW)},
doi = {10.1109/QSW62656.2024.00013},
eprint = {2405.17543},
eprinttype = {arxiv},
addendum = {A live version of this document is available at \url{https://mqt.readthedocs.io}}
}
Acknowledgements
The Munich Quantum Toolkit has been supported by the European Research Council (ERC) under the European Union's Horizon 2020 research and innovation program (grant agreement No. 101001318), the Bavarian State Ministry for Science and Arts through the Distinguished Professorship Program, as well as the Munich Quantum Valley, which is supported by the Bavarian state government with funds from the Hightech Agenda Bayern Plus.
Metadata
Release files for mqt-core 4.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mqt_core-4.1.1.tar.gz | 1.9 MB | Details |
Built distributions (wheels)
Total release size: 467.1 MB
Release files / mqt_core-4.1.1.tar.gz
| Download URL | mqt_core-4.1.1.tar.gz |
|---|---|
| Size | 1.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
358bb35242b9f0407ac311e8f5ccd5bdd0e67f9f58a0eb84595bb676fb915d0d
|
|
BLAKE2b-256 checksum How to use checksums |
a0b4e9c4d8ac82fa78dc0d8ba1f737d0bb7fa56af065b90c8b60bbf6b3549a41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp315-abi3t-win_arm64.whl
| Download URL | mqt_core-4.1.1-cp315-abi3t-win_arm64.whl |
|---|---|
| Size | 42.0 MB |
| Tags | CPython 3.15 Windows ARM64 abi3t |
|
SHA-256 checksum How to use checksums |
086fded62248353a21a3e4a6dc155fc017094f1c51374c7c52adac345433bd2d
|
|
BLAKE2b-256 checksum How to use checksums |
427529efb2b6dae5d9548d79fe49613172ca465ffe779ede04ca70dd575e44a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp315-abi3t-win_amd64.whl
| Download URL | mqt_core-4.1.1-cp315-abi3t-win_amd64.whl |
|---|---|
| Size | 43.4 MB |
| Tags | CPython 3.15 Windows x86-64 abi3t |
|
SHA-256 checksum How to use checksums |
34dd2569437a06d9f085a5f0893daed60793217aabbb3bf96cd54702814adf77
|
|
BLAKE2b-256 checksum How to use checksums |
4a4823a14834ec1146c78dd0e58e45c062a44a422ccb517cfa2017fd4d3ed4b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp315-abi3t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | mqt_core-4.1.1-cp315-abi3t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 55.2 MB |
| Tags | CPython 3.15 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 abi3t |
|
SHA-256 checksum How to use checksums |
23d8d81482742e99e9fa2eefdad14d88b73a815caa8b2f40ed35f8de39e6242b
|
|
BLAKE2b-256 checksum How to use checksums |
9df9c879f1f3891c09d49ed8747d8de6d3e57e2a54ba412fadbeb0f36164fe1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp315-abi3t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | mqt_core-4.1.1-cp315-abi3t-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 52.4 MB |
| Tags | CPython 3.15 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 abi3t |
|
SHA-256 checksum How to use checksums |
1a2a1455604865b02c21bc7b9f958761afe3854b8c57ce31daacbca40f01e340
|
|
BLAKE2b-256 checksum How to use checksums |
efa84742d0d9006e40552a572b028db03c857754553906c6238d4aacc09d6c70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp315-abi3t-macosx_13_0_arm64.whl
| Download URL | mqt_core-4.1.1-cp315-abi3t-macosx_13_0_arm64.whl |
|---|---|
| Size | 40.8 MB |
| Tags | CPython 3.15 abi3t macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
967fed209199c23ac0acbe13660c334a0f065dba8beb7b7b53752490f53c3a1e
|
|
BLAKE2b-256 checksum How to use checksums |
4126e39b9271f224c0033f6c5de6d6c6165c9f2e84f71a253f5b2b4d4decdac8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp311-abi3-win_arm64.whl
| Download URL | mqt_core-4.1.1-cp311-abi3-win_arm64.whl |
|---|---|
| Size | 40.6 MB |
| Tags | CPython 3.11 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
4d0977a7992b3681f103458f25213639f46d1a6e78e640b475617a656144de13
|
|
BLAKE2b-256 checksum How to use checksums |
9044d76541caad7c4d2f0d86d3283b012f2197b67f4c85f3d9bfd6e38fa51b41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp311-abi3-win_amd64.whl
| Download URL | mqt_core-4.1.1-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 42.5 MB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
13189c300c50d249fd56459aaa6345684195139758399281c67eb5b599d42b08
|
|
BLAKE2b-256 checksum How to use checksums |
071e696eda1ac8efe5c9d8ef3127262dd88e72358f5bde68f301f976c771ea0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp311-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | mqt_core-4.1.1-cp311-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 55.2 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
e7cef5cbc2cedd30618a6ab5a10f707279644a1734f888bb42c5a76231da2088
|
|
BLAKE2b-256 checksum How to use checksums |
738e9b2380db305faab84ad8f6115925d8bc2e02b2055ef116ea7be02e9f6677
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp311-abi3-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | mqt_core-4.1.1-cp311-abi3-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 52.4 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
7b3a229cc61c2be7023b63b2f95196210a5059ed0c3a42978b79b3b240d1e2e8
|
|
BLAKE2b-256 checksum How to use checksums |
d7dc40b75762a0d1c036809911f549d99d413051f45dd5e46cafef20d21ea44a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / mqt_core-4.1.1-cp311-abi3-macosx_13_0_arm64.whl
| Download URL | mqt_core-4.1.1-cp311-abi3-macosx_13_0_arm64.whl |
|---|---|
| Size | 40.8 MB |
| Tags | CPython 3.11 abi3 macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
356a3a3b43f50595ce63a32ff367daf681dc5503228e2dd7d9818c760eb26fb3
|
|
BLAKE2b-256 checksum How to use checksums |
1067a59b12eefc708e76e3726c3e3a69e441e541ce4bffe600803c82eb1f0807
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency log