MirrorNeuron Python SDK
mn-python-sdk provides the Python gRPC client and workflow-bundle helpers used
by the CLI, API, and Python-defined workflows.
Quick Start
Install locally and run tests:
python3.11 -m venv .venv
. .venv/bin/activate
.venv/bin/python -m pip install -e ".[dev]"
.venv/bin/python -m pytest -q
.venv/bin/python -m ruff check .
Minimal client example:
from mn_sdk import Client
client = Client(target="localhost:55051")
print(client.list_jobs(limit=5))
Details
Source Manifests
Blueprints may use apiVersion: mn.workflow.source/v1 for a compact,
CSS-like manifest.json that declares intent and overrides while SDK profiles
provide common defaults. Generate the executable runtime manifest with:
mn-manifest-converter expand manifest.json --output build/manifest.executable.json
mn-manifest-converter check manifest.json --against build/manifest.executable.json
The CLI/API expand source manifests automatically before validation and
submission. Existing mn.workflow/v1 executable manifests continue to work.
Configuration
Configuration is loaded by mn_sdk.config in this order:
real environment variables
> .env.${MN_ENV}
> .env
> built-in safe defaults
MN_ENV defaults to dev when unset. MN_ENV=development loads .env.dev;
MN_ENV=test loads .env.test; MN_ENV=prod or MN_ENV=production loads
.env.prod when present. Production does not require any .env file.
Development example:
export MN_ENV=dev
cp .env.example .env.dev
mn-cli ...
Test example:
export MN_ENV=test
mn-cli ...
Production example:
export MN_ENV=production
export MN_HOME=/var/lib/mirrorneuron
export MN_LOG_LEVEL=info
export MN_API_HOST=0.0.0.0
export MN_API_PORT=8080
mn-api ...
Do not commit real .env files. Use .env.example for placeholders only, and
put secrets in real environment variables or token files.
Notes
- A running MirrorNeuron core is required for live client calls.
- Constructor arguments take precedence over environment variables.
- Generated protocol modules are included with the package.
Release files for mirrorneuron-python-sdk 1.2.22
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mirrorneuron_python_sdk-1.2.22.tar.gz | 296.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mirrorneuron_python_sdk-1.2.22-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 557.0 kB
Release files / mirrorneuron_python_sdk-1.2.22.tar.gz
| Download URL | mirrorneuron_python_sdk-1.2.22.tar.gz |
|---|---|
| Size | 296.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff45a5ff24713063241c4551fbad91ab3f17e5358f3c5d28d7566967e5896d69
|
|
BLAKE2b-256 checksum How to use checksums |
75901e13902c090c53d8509102f045184e6c7081b25bcb895c25bc457d18d091
|
| 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 Jul 9, 2026.
Transparency logRelease files / mirrorneuron_python_sdk-1.2.22-py3-none-any.whl
| Download URL | mirrorneuron_python_sdk-1.2.22-py3-none-any.whl |
|---|---|
| Size | 260.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa2d9504df7f6fb20103aabb79b54b0faa7c04733476872b60121790f41aa486
|
|
BLAKE2b-256 checksum How to use checksums |
183d0e771051bab509d73cfe432ce753803b2cf39fd496e9c947ee72c52fe3a4
|
| 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 Jul 9, 2026.
Transparency log