Mission Pinball Framework (MPF)
...Let's build a pinball machine!
What is Mission Pinball Framework?
Mission Pinball Framework (MPF) is open source, cross-platform software for powering real pinball machines. MPF is a community-developed project released under the MIT license. It's supported by volunteers in their spare time.
Visit the MPF project homepage at https://missionpinball.org. Additional related projects exist as part of the MPF ecosystem, including the "MPF Monitor" which is a graphical application that lets you simulate pinball hardware, and "MPF-MC" which is a media controller which provides graphics and sounds for pinball machines.
Documentation
- User Docs (installation, tutorials, & reference): https://missionpinball.org
Support
MPF is an open source community project which has no official support. Some MPF users participate in the MPF-Users Google group or GitHub Discussion. Links here.
Individual pinball hardware companies may provide additional support for users of their hardware, often via their own Slack, Discord, or other chat groups. If you get stuck, you can ask for help in the MPF-users group, or you reach out to your hardware provider.
Maintenance, Pull Requests, & Bug Fixes
As a community project, we welcome pull requests and bug fixes. However, we do not have the resources to provide support for MPF. If you are interested in becoming a maintainer, please contact us at brian@missionpinball.org.
Bugs or other issues related to MPF itself can be posted to the MPF Discussions page on GitHub.
Contributing
Individual pinball hardware makers are responsible for their own platform interface maintenance and contributions.
MPF is a passion project created and maintained by volunteers. If you're a Python coder, documentation writer, or pinball maker, feel free to make a change and submit a pull request. For more information about contributing see the Contributing Code and Contributing Documentation pages.
License
MPF and related projects are released under the MIT License. Refer to the LICENSE file for details. Docs are released under Creative Commons CC BY 4.0.
3 maintainers
Metadata
3 maintainers
Release files for mpf 0.57.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mpf-0.57.6.tar.gz | 3.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mpf-0.57.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.9 MB
Release files / mpf-0.57.6.tar.gz
| Download URL | mpf-0.57.6.tar.gz |
|---|---|
| Size | 3.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa3f5ea974202995669b3ecdb0c8cf3fd6f20dda8795cbfcd95879c2d71de7dd
|
|
BLAKE2b-256 checksum How to use checksums |
a5dfbd200b44afa2b764d20920d2bc1c1e4b55eeaed474fd71ea3f4328ceec53
|
| 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 Sep 28, 2026.
Transparency logRelease files / mpf-0.57.6-py3-none-any.whl
| Download URL | mpf-0.57.6-py3-none-any.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
edfedcd5928e7bdfae414fe55be7a7acce7de67b3dff7b600126a0d9df71cee5
|
|
BLAKE2b-256 checksum How to use checksums |
976e9700dfb96ed450421b37b567fe53f4781feadca92d833ab9faeac18e2173
|
| 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 Sep 28, 2026.
Transparency log
