Skip to main content

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 1xops.yaml, 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

1xops.yaml

One file holds everything a person or team sets. It holds non-secret values only; secrets stay in AWS SSO, az login or the Atlassian sign-in.

scope: team                       # org | team | local | personal
dir: .                            # project or tenant folder (team, local)
connectors:
  aws:
    AWS_BILLING_PROFILE: "billing-readonly"
    AWS_OPERATIONS_PROFILE: "ops-readonly"
    AWS_REGION: "ap-southeast-2"
  itsm: {}
  ./my-profile.json: {}           # your own profile
1xops config --file 1xops.yaml --yes    # apply it
eval "$(1xops env)"                    # team/org: load your values into the shell
  • Keys are the ${VAR} names each profile uses; 1xops profiles lists them.
  • At team and org scope the shared files keep ${VAR}, so profile names and tenant IDs never reach git. The host reads these from your shell environment, so run 1xops env.
  • At local and personal scope the values are written into your private host configuration.
  • Values must be quoted strings, and keys that look like secrets (TOKEN, SECRET, PASSWORD, API_KEY) are refused.
  • Keep a personal 1xops.yaml out 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 mcpServers object: --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.0

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

Source distribution (sdist)

Source distribution for 1xops 0.2.0
File Size Uploaded Provenance Actions
1xops-0.2.0.tar.gz 11.3 kB Without provenance Details for 1xops-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for 1xops 0.2.0
File Interpreter ABI Platform Actions
1xops-0.2.0-py3-none-any.whl Python 3 none any Details for 1xops-0.2.0-py3-none-any.whl

Total release size: 24.7 kB

Release files / 1xops-0.2.0.tar.gz

Download URL 1xops-0.2.0.tar.gz
Size 11.3 kB
Tags Source
SHA-256 checksum
How to use checksums
e9a07ff784ba51db7576e503dd217e066ed6fa01892ba005323f91fc70446ae4
BLAKE2b-256 checksum
How to use checksums
5908819eb8e3d823d34ee7a4609cf267150f0b16eccde838da4897064473beea
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / 1xops-0.2.0-py3-none-any.whl

Download URL 1xops-0.2.0-py3-none-any.whl
Size 13.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f69e6d717474da777f709845d82160a77e681c16b4f1120d6a2e9aa7394103d2
BLAKE2b-256 checksum
How to use checksums
fb98ea4662f77265f677497a08f57df56707e2c85c88a6cd26a3ce6b31b7f60f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Security for 1xops 0.2.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

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