Lumoz setup
Install Lumoz skills and MCP tools in Codex or Claude Code without manually
cloning a repository. Requires uv (uvx) and the chosen client's CLI.
Install and configure either client:
uvx lumoz-setup codex
uvx lumoz-setup claude-code
Run one command for each client you use. Setup prompts for the full
client_id:client_secret API key with hidden input. No shell export is needed.
Run directly in a terminal; do not pipe the key into the command.
Codex setup adds the Lumoz marketplace, installs lumoz-skills@lumoz, and
registers the pinned MCP server with its API key in private config.toml.
Codex stores the key as plaintext. Rerunning setup replaces the full lumoz
MCP entry, including custom settings.
Claude Code setup adds the marketplace, installs lumoz-skills@lumoz and
lumoz-mcp@lumoz at user scope, then saves the key and absolute uvx path
through claude plugin configure --values-stdin. Claude Code 2.1.285+ is
required for that command. Existing installed plugins are kept and disabled
ones are enabled. An existing marketplace named lumoz keeps its source;
remove it first if it points to an outdated repository.
Restart the client, open /mcp, then ask:
Use Lumoz to list the apps and environments I can access. Do not modify anything.
Ask for lumoz-evals to use the skill. Registration does not verify API access;
a successful tool call does. The first MCP connection downloads its server
through uvx if needed. Local stdio tools do not configure cloud Chat sessions.
Uninstall
uvx lumoz-setup codex uninstall
uvx lumoz-setup claude-code uninstall
Uninstall removes the target client's Lumoz tools and skills, then removes the Lumoz marketplace if no remaining plugins need it. Other integrations remain. Codex removes the key with the MCP entry. Claude manages plugin settings and secret deletion; credentials stay if the plugin remains installed in another scope. Claude uninstall changes user scope only.
Restart active sessions to disconnect their running server. Uninstall does
not revoke API keys in Lumoz or erase package caches or credential copies
saved elsewhere. Codex MCP alone can also be removed with
codex mcp remove lumoz without uv or the installer.
Development and release
Runtime code lives in installer/src/lumoz_setup/; maintainer tooling lives
in scripts/. Runtime defaults and the license are packaged with the wheel;
no checkout files are read by the installed CLI.
To test local changes, run from the repository root:
uvx --from ./installer lumoz-setup --help
uvx --from ./installer lumoz-setup codex
See release instructions for package builds, versioning, and PyPI trusted-publisher configuration.
1 maintainer
Metadata
1 maintainer
Release files for lumoz-setup 0.1.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 |
|---|---|---|---|---|
| lumoz_setup-0.1.0.tar.gz | 9.5 kB | With provenance | Details for lumoz_setup-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lumoz_setup-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for lumoz_setup-0.1.0-py3-none-any.whl |
Total release size: 19.9 kB
Release files / lumoz_setup-0.1.0.tar.gz
| Download URL | lumoz_setup-0.1.0.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
582a9b4496b151d597c9401f690422d8d9098676ba0bb6e08640eb846290e848
|
|
BLAKE2b-256 checksum How to use checksums |
3b9853496b6c5977fe18cf4e919daf53ee546f92a018e9574d5f5a71a7dff74f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 22, 2026.
Transparency logRelease files / lumoz_setup-0.1.0-py3-none-any.whl
| Download URL | lumoz_setup-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f22f1bcd6a1203c0d6a02f6824679f2095edee7f991ee5d80f179ebc906a351
|
|
BLAKE2b-256 checksum How to use checksums |
a21e69c53530acad2b9412ee01e3d9443b6294ce10f6ac2bdd91f798565aaa2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 22, 2026.
Transparency logSecurity for lumoz-setup 0.1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for lumoz_setup-0.1.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 Oct 22, 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.
