Local IFC tools for IFCViewX. Everything stays on your machine.
Local Studio guide
·
Docs
Install and run
pip install ifcviewx
ifcviewx # open Local Studio
ifcviewx model.ifc # open a model
Local Studio serves IFCViewX at 127.0.0.1:8765. It can convert IFC models to
.ifcx with IfcOpenShell, run native Python, and check models from the command
line. It also provides an MCP bridge for supported AI clients and can keep an
assistant API key in a local vault instead of the browser.
Use --convert when you want to create an optimized .ifcx copy. The check
command runs model and IDS checks without opening the viewer, while mcp
starts the bridge for an AI client.
ifcviewx model.ifc --convert
ifcviewx check model.ifc --ids spec.ids
ifcviewx mcp
The service accepts local connections only. Model edits run on a copy and wait
for approval in the viewer, so the original file is not changed silently. Use
--readonly to block writes or --no-python to disable Python completely.
License
Apache License 2.0, see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for ifcviewx 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ifcviewx-0.1.4.tar.gz | 2.6 MB | With provenance | Details for ifcviewx-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ifcviewx-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for ifcviewx-0.1.4-py3-none-any.whl |
Total release size: 5.3 MB
Release files / ifcviewx-0.1.4.tar.gz
| Download URL | ifcviewx-0.1.4.tar.gz |
|---|---|
| Size | 2.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd061f575ee6680492a2d3a6f3fb3e233d54a020208f5db3d5f32d77aa72e6e9
|
|
BLAKE2b-256 checksum How to use checksums |
7b4e3c6d6ac027a716409a78f468a0d643212d77623a742e71526c83c23c71e7
|
| 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 3, 2026.
Transparency logRelease files / ifcviewx-0.1.4-py3-none-any.whl
| Download URL | ifcviewx-0.1.4-py3-none-any.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
58c43419d667c0b1865c0baec509357051ebe556c13fbb4eb0edd3d0365b9b46
|
|
BLAKE2b-256 checksum How to use checksums |
87e1d3ab909a88c892a4ad3397b0f063c8a5296215dfeeb2c94caf1266b95b56
|
| 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 3, 2026.
Transparency logSecurity for ifcviewx 0.1.4
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ifcviewx-0.1.4.tar.gz
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 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
