scry-connect
MCP server for ROS 2 — exposes your robot's topics, nodes, services, parameters, actions, diagnostics, and ~99 other introspection tools to AI agents.
Pairs with the Scry app for natural-language robot debugging.
Install
pip install scry-connect
Requires Python 3.10+ and a sourced ROS 2 environment (Humble, Jazzy,
Kilted, Lyrical, or Rolling). The rclpy runtime is provided by your
ROS 2 install — no second install required.
Run
source /opt/ros/$ROS_DISTRO/setup.bash
scry-connect
Defaults to 0.0.0.0:5339, LAN-only (rejects callers from public IPs).
Open the Scry app on your phone and scan the printed pairing QR.
scry-connect --token # require a paired token for all calls
scry-connect --mtls # mutual TLS for production deployments
Other install paths
For Docker, sidecar deployments, or the one-line installer, see the install guide.
Links
Metadata
Release files for scry-connect 1.3.0
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 |
|---|---|---|---|---|
| scry_connect-1.3.0.tar.gz | 251.8 kB | With provenance | Details for scry_connect-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scry_connect-1.3.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for scry_connect-1.3.0-py2.py3-none-any.whl |
Total release size: 465.5 kB
Release files / scry_connect-1.3.0.tar.gz
| Download URL | scry_connect-1.3.0.tar.gz |
|---|---|
| Size | 251.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d3c81df34f58f97b8da9af91395a4c8de2914680ebdf139f0a4a4a8a50eb8c5
|
|
BLAKE2b-256 checksum How to use checksums |
d1dff6fbf931a47c5d723fac10447634132f64833ae0febd80b42b1b1260ac42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 18, 2026.
Transparency logRelease files / scry_connect-1.3.0-py2.py3-none-any.whl
| Download URL | scry_connect-1.3.0-py2.py3-none-any.whl |
|---|---|
| Size | 213.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
140877d15db4b995053b9a868b8efb68402026e5c0d1260762c2bc37f52fe860
|
|
BLAKE2b-256 checksum How to use checksums |
b4b2255b1fd3117200638d844d3b3661e08b5c51cf5de0ac9fb72daed2ea17b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 18, 2026.
Transparency logSecurity for scry-connect 1.3.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for scry_connect-1.3.0.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 Jun 18, 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.