Skip to main content

MirrorNeuron CLI

mn-cli provides the mn command for validating and running blueprints, inspecting runtime state, managing jobs, exporting artifacts, and starting local services installed by mn-deploy.

Quick Start

Install locally and run tests:

python3.11 -m venv .venv
. .venv/bin/activate
.venv/bin/python -m pip install -e .
.venv/bin/python -m pytest -q

Try the CLI:

mn --version
mn node list
mn blueprint run message_routing_trace

Override blueprint config for one run without changing config/overwrite.json:

mn blueprint run --folder ./vc_assistant \
  --set document_sources.folder_path=/path/to/documents \
  --set execution.debug=true

Repeat --set for multiple values. Values use JSON types when possible and otherwise remain strings.

Configuration

Configuration is loaded by mn_cli.config. .env files provide defaults, and real environment variables always override them. MN_ENV selects the environment-specific defaults file and defaults to dev when unset.

Precedence:

real environment variables
> .env.${MN_ENV}
> .env
> built-in safe defaults

Development:

export MN_ENV=dev
cp .env.example .env.dev
mn --version

Tests:

export MN_ENV=test
mn --version

Production does not require any .env file. Provide deployment-specific values through the real environment:

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 runtime status

Keep secrets, credentials, production hostnames, production database URLs, cloud credentials, and user-specific local paths out of source files. Use environment variables or uncommitted .env files instead.

Details

Notes

  • A running MirrorNeuron core is required for live runtime commands.
  • The default gRPC target comes from MN_GRPC_TARGET, then local deployment settings, then localhost:55051.
  • Use mn blueprint validate before mn blueprint run --folder when checking a local bundle.
  • mn blueprint run checks the complete effective model set before preparation; if no node can satisfy it, the command reports per-node capacity reasons and does not start any model installation.

Release files for mirrorneuron-cli 1.2.26

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mirrorneuron-cli 1.2.26
File Size Uploaded
mirrorneuron_cli-1.2.26.tar.gz 363.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for mirrorneuron-cli 1.2.26
File Interpreter ABI Platform
mirrorneuron_cli-1.2.26-py3-none-any.whl Python 3 none any Details

Total release size: 614.2 kB

Release files / mirrorneuron_cli-1.2.26.tar.gz

Download URL mirrorneuron_cli-1.2.26.tar.gz
Size 363.5 kB
Tags Source
SHA-256 checksum
How to use checksums
3f82ea8f25bac4bcc5cac1fe1e2e2f7d573eeea1b65a30f0453ce1439c739d4e
BLAKE2b-256 checksum
How to use checksums
9bb0aee8e04f64cba66dceb21ee6d9d467cf1f4dd785533eaee704b2744aafae
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 18, 2026.

Transparency log

Release files / mirrorneuron_cli-1.2.26-py3-none-any.whl

Download URL mirrorneuron_cli-1.2.26-py3-none-any.whl
Size 250.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9e5049a0464e1d980eaaf9a8f8d78794d27082bb03e1ea4d107937b698e4b54a
BLAKE2b-256 checksum
How to use checksums
fa56c9ad82f9610b30469ae8c5252840146e78100c43d33fe6919d97c0c6b6f1
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 18, 2026.

Transparency log

Release history Release notifications | RSS feed

1.2.32

2 release files

1.2.31

2 release files

1.2.30

2 release files

1.2.27

2 release files

This release

1.2.26 This release

2 release files

1.2.25

2 release files

1.2.23

2 release files

1.2.22

2 release files

1.2.18

2 release files

1.2.15

2 release files

1.2.8

2 release files

1.2.7

2 release files

1.2.6

2 release files

1.2.5

2 release files

1.1.9

2 release files

1.1.4

2 release files

1.1.3

2 release files

1.1.2

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page