1xops
Command line for 1xops by OceanSoft.io: checks prerequisites, installs the 1xops plugin, and writes settings and read-only cloud connectors for an organisation, a team (or tenant folder), a project, or one person.
uvx 1xops doctor # prerequisites and read-only sign-in (account IDs masked)
uvx 1xops install --yes # add the marketplaces and install the plugin
uvx 1xops setup # guided: asks a few questions, writes .env.1xops, shows the diff
uvx 1xops profiles # built-in connector profiles: aws, azure, itsm
uvx 1xops config --scope team --connectors aws itsm # shows a diff
uvx 1xops config --scope team --connectors aws itsm --yes # writes it
| Scope | Writes | Who it is for |
|---|---|---|
org |
managed-settings.json, managed-mcp.json in --out, for IT to deploy |
Everyone in the organisation |
team |
.claude/settings.json, .mcp.json in --dir (a project or tenant folder) |
Everyone on the project, via git |
local |
.claude/settings.local.json in --dir; connectors via the host CLI |
You, in this project |
personal |
~/.claude/settings.json; connectors via the host CLI |
You, in every project |
.env.1xops
One plain KEY=value file holds everything a person or team sets: non-secret values only. Secrets stay in AWS SSO, az login or the Atlassian sign-in.
ONEXOPS_SCOPE=team # org | team | local | personal
ONEXOPS_DIR=. # project or tenant folder (team, local)
ONEXOPS_CONNECTORS=aws,itsm # built-in profiles, or paths to your own .json profiles
AWS_OPERATIONS_PROFILE=ops-readonly
AWS_REGION=ap-southeast-2
1xops config --file .env.1xops --yes # apply it
eval "$(1xops env)" # team/org: load your values into the shell
- Every other
KEYis the${KEY}a profile uses;1xops profileslists them. - At
teamandorgscope the shared files keep${VAR}, so profile names and tenant IDs never reach git. The host reads these from your shell environment, so run1xops env. - At
localandpersonalscope the values are written into your private host configuration. - Keys that look like secrets (
TOKEN,SECRET,PASSWORD,API_KEY) and unknownONEXOPS_settings are refused. - Keep a personal
.env.1xopsout of git.
Rules
- Nothing changes without
--yes. - Existing values are never overwritten; only missing entries are added.
- Built-in profiles pin every server version and use
${VAR}references for profiles, tokens and URLs, so no secret is written to a file. - Your own profile is a JSON file with an
mcpServersobject:--connectors ./my-profile.json.
Licence: Apache-2.0. © 2026 Nhat-Thanh Nguyen (nnthanh101@gmail.com), OceanSoft.io. Licence, trademarks and third-party components: NOTICE.
Metadata
Release files for 1xops 0.2.6
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 |
|---|---|---|---|---|
| 1xops-0.2.6.tar.gz | 20.2 kB | With provenance | Details for 1xops-0.2.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| 1xops-0.2.6-py3-none-any.whl | Python 3 | none | any | Details for 1xops-0.2.6-py3-none-any.whl |
Total release size: 38.8 kB
Release files / 1xops-0.2.6.tar.gz
| Download URL | 1xops-0.2.6.tar.gz |
|---|---|
| Size | 20.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d30f4a4d3ba7ae96cdec4e969375cb52be65716280fea7f476c46c4c73fac3d8
|
|
BLAKE2b-256 checksum How to use checksums |
72363a48772fe7071e67e7eee7cbca5648595984aa42bb386637488e55c2fc2d
|
| 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 Nov 17, 2026.
Transparency logRelease files / 1xops-0.2.6-py3-none-any.whl
| Download URL | 1xops-0.2.6-py3-none-any.whl |
|---|---|
| Size | 18.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c8039b9f44327b4f7f19c798609915226cd22f25fc7da52d9d1e4790fbc2324
|
|
BLAKE2b-256 checksum How to use checksums |
08681d8d8219c107f4a823c46bae0c52d9696295be4dbe37ceb06f21fe2acd08
|
| 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 Nov 17, 2026.
Transparency logSecurity for 1xops 0.2.6
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 1xops-0.2.6.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 Nov 17, 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.