devops-utils 0.2.0

Description

A set of utility tools for DevOps, built around a dependency-free core that is exposed through several optional surfaces: a CLI, a Qt UI, a TUI, an MCP server, and agent tools.

Requires Python 3.12+.

Install

# core + CLI
pip install devops-utils

# with optional surfaces
pip install "devops-utils[mcp]"   # MCP server
pip install "devops-utils[tui]"   # Textual TUI
pip install "devops-utils[qt]"    # PySide6 desktop UI
pip install "devops-utils[azure]" # Azure DevOps work-item tools
pip install "devops-utils[all]"   # everything

For development this project uses uv:

uv sync --all-extras --dev

Usage

# Mask Secret values in a Kubernetes manifest, print to stdout
devops-utils sanitize manifest.yml -o -

# Write the sanitized manifest to a file
devops-utils sanitize manifest.yml -o manifest.sanitized.yml

Run the MCP server (requires the mcp extra):

devops-utils-mcp

Azure DevOps work items

A small, LLM-friendly interface to Azure DevOps work items, working against both Services (cloud) and Server (on-prem). Requires the azure extra.

Credentials are never read from the machine — supply a bearer token (or PAT) out-of-band via environment variables:

export AZURE_DEVOPS_ORG_URL="https://dev.azure.com/your-org"   # or on-prem: https://server/tfs/DefaultCollection
export AZURE_DEVOPS_TOKEN="<bearer-token-or-pat>"
export AZURE_DEVOPS_AUTH_SCHEME="bearer"   # or "pat" for a raw Personal Access Token
export AZURE_DEVOPS_API_VERSION="7.1"      # lower for older on-prem servers

devops-utils azdo repos --project MyProject
devops-utils azdo list --project MyProject --state Active --type Bug
devops-utils azdo search --project MyProject "login timeout"
devops-utils azdo create --project MyProject --type Task --title "Fix flaky test"
devops-utils azdo update 42 --state Closed --assigned-to dev@example.com
devops-utils azdo comment 42 "Investigating."
devops-utils azdo tag 42 backend urgent
devops-utils azdo link 42 --kind commit --project MyProject --repo MyRepo --value <sha>
devops-utils azdo attach 42 ./trace.log

The same operations are exposed as MCP tools (azdo_*) and framework-agnostic agent callables in devops_utils.agent.tools, all reading the env vars above.

Set up an agent

devops-utils setup installs the bundled skills, wires the devops-utils-mcp server into an agent's MCP config, and writes an Azure DevOps env scaffold. Defaults target Claude Code at user scope (~/.claude).

# Everything, for the current user (skills + MCP server + env scaffold)
devops-utils setup all

# Scope to the current repo (./.claude, ./.mcp.json)
devops-utils setup all --project

# Individual steps, or an arbitrary directory
devops-utils setup skills --dest ./agent-skills
devops-utils setup mcp --dest .
devops-utils setup env

Use --force to overwrite existing files; setup mcp merges into any existing config without clobbering other servers.

Use with mattpocock/skills

Skills like mattpocock/skills (triage, wayfinder, to-tickets, …) read a repo-local config file, docs/agents/issue-tracker.md, to learn how to talk to the issue tracker — GitHub's gh CLI by default. To point them at Azure DevOps work items via devops-utils instead, run in the target repo:

devops-utils setup tracker --project-name MyProject --done-state Closed

This writes docs/agents/issue-tracker.md and docs/agents/triage-labels.md mapping every tracker operation (create, comment, labels→tags, close, claim, blocking links, PR references) to devops-utils azdo / the azdo_* MCP tools. --done-state is the state meaning "closed" in your process template (Closed, Done, Resolved, …).

Author

Cláudio Ferreira Carneiro - carneirofc @ claudiofcarneiro@gmail.com

Licence

devops-utils is licensed under the MIT License. See LICENSE.