dcc-mcp-openscreen
Standalone DCC-MCP adapter for OpenScreen.
The adapter exposes only typed, bounded CLI operations. Set DCC_MCP_OPENSCREEN_PATH when the executable is not on PATH. It does not automate the desktop UI; DCC window selection and unsupported UI actions remain owned by dcc-cua / ui-control.
Run
python -m pip install -e .
dcc-mcp-openscreen
Tools: openscreen__sources, openscreen__record, and openscreen__export.
License
MIT
Release files for dcc-mcp-openscreen 0.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 | |
|---|---|---|---|
| dcc_mcp_openscreen-0.1.1.tar.gz | 7.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dcc_mcp_openscreen-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.3 kB
Release files / dcc_mcp_openscreen-0.1.1.tar.gz
| Download URL | dcc_mcp_openscreen-0.1.1.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b022458471972ae26fcc0e8e645fccc8b9ec7ba7248a6069a11e88d46e84cfa9
|
|
BLAKE2b-256 checksum How to use checksums |
86436bc4d635b124af040e9ccc0978c03895027f92a045e406332da753461097
|
| 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 27, 2026.
Transparency logRelease files / dcc_mcp_openscreen-0.1.1-py3-none-any.whl
| Download URL | dcc_mcp_openscreen-0.1.1-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3e756014a35579fb9776b4819c9d0ff5b6a5354f16b61d0b0e81f8dc0b083c4
|
|
BLAKE2b-256 checksum How to use checksums |
06b45daa7b649f2b0fe8078ac05935efad2ad2f2f38ae5a5ff2e22941250700c
|
| 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 27, 2026.
Transparency log
