Devops Practices

Name: Devops Practices
Author: ai-4-devops

by ai-4-devopsversion 1.4.0i★ –iRuns on your computer

Registry nameio.github.ai-4-devops/devops-practices

Install

Overview

Description from the maker (original English)

Productivity framework for DevOps engineers using AI assistance (Claude Code) while working on PoCs

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "devops-practices": {
      "command": "uvx",
      "args": [
        "devops-practices-mcp",
        "-m",
        "devops_practices_mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add devops-practices -- uvx devops-practices-mcp -m devops_practices_mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "devops-practices": {
      "command": "uvx",
      "args": [
        "devops-practices-mcp",
        "-m",
        "devops_practices_mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "devops-practices": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "devops-practices-mcp",
        "-m",
        "devops_practices_mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ai-4-devops, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 1394 servers in this category
Published to the registry more recently than 6% of the other 1394 servers in this category
Basic checks equal to or better than 100% of the other 1394 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Devops Practices safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.4.0) reached the registry 9 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

DevOps Practices - MCP Server

mcp-name: io.github.ai-4-devops/devops-practices

Purpose: Productivity framework for DevOps engineers using AI assistance (Claude Code) while working on PoCs.

Type: Model Context Protocol (MCP) Server for Claude Code

Version: 1.4.0

Status: 🎉 Officially Published in the MCP Registry (Published: February 18, 2026)

Published Versions:

📦 PyPI: v1.4.0 → Git tag v1.4.0 (34ca572)
🌐 MCP Registry: v1.4.0 → Git tag v1.4.0 (34ca572)
🚀 Latest Development: main branch (may include unreleased features)

Who is this for? DevOps engineers using Claude Code (VS Code plugin) for PoC development.

What it does: Provides structure (TRACKER, ISSUES, docs, SoPs) so you can focus on building without worrying about documentation overhead.

What it's NOT: Not a DevOps tutorial - it's a productivity framework for AI-assisted development.

Why This MCP Server?

Solves the CLAUDE.md Bloat Problem

Tired of maintaining massive CLAUDE.md files (1000+ lines) across multiple projects? This MCP centralizes reusable DevOps instructions for engineers working on multiple PoCs, eliminating repeated instructions across projects and folders.

The Problem:

❌ Large CLAUDE.md files eat up context window
❌ Same practices duplicated across every project
❌ Reinventing TRACKER.md, ISSUES.md, docs, SoPs for every PoC
❌ Inconsistent standards across projects
❌ Context wasted on instructions instead of actual work

The Solution:

✅ Pre-built structure - Templates for TRACKER, ISSUES, docs, SoPs
✅ Focus on work - Not on "how should I document this?"
✅ Consistency - Same standards across all your PoCs
✅ Team alignment - Same patterns enable seamless collaboration and easy handovers across sessions, systems, and team members
✅ Faster startup - Copy template, start working
✅ Context saved - No bloated CLAUDE.md files

What you get (structure, not knowledge):

📋 TRACKER.md template - Start tracking immediately, don't design tracking
🐛 ISSUES.md system - Start logging issues, don't setup Jira
📚 Documentation standards - Start writing docs, don't debate structure
📖 Runbook templates - Start documenting ops, don't create SoP formats
🔄 Session continuity - Start handoffs, don't design handoff protocols

When searching "devops" in the MCP Registry (as of February 2026), this is the only result. While other MCPs focus on:

🔧 Development tools (code generation, testing, debugging)
📊 Data analysis (databases, APIs, analytics)
🎨 Content creation (writing, design, media)

This MCP provides:

🏗️ Configuration structure - How to organize configs per environment, generate new env configs from completed ones, create and validate SoPs
📚 Documentation patterns - TRACKER, ISSUES, docs, runbook templates ready to copy
🔄 Operations templates - Session handoff, runbook formats, documentation standards
🎯 Structured guidance - GG-SS organized practices for quick discovery

What makes it different:

Prescriptive, not generative - Provides proven practices, not generated code
Infrastructure-first - Built for ops teams, not developers
Reusable patterns - Templates and standards across all your projects
AI-native design - Organized for Claude to query and apply contextually
R&D optimized - Accelerates proof-of-concept development and experimentation

Perfect for: DevOps engineers using Claude Code (VS Code plugin) to build PoCs and conduct R&D with AI assistance.

How It Works

No server management required:

✅ Auto-start: Spawns when Claude Code/Desktop starts
✅ Background: Runs silently while you work
✅ On-demand: Claude queries practices as needed
✅ Auto-stop: Shuts down when Claude closes
✅ Fallback: Access practices via GitHub/local if MCP unavailable (see Troubleshooting)

Configuration Options:

You can configure the MCP server globally (all projects) or per-project:

Option 1: Global Configuration (~/.claude.json)

"mcpServers": { "devops-practices": { "command": "python3", "args": ["-u", "~/.mcp-servers/devops-practices/mcp-server.py"], "env": {"PYTHONUNBUFFERED": "1"} } } }

Option 2: Project-Level Configuration (.mcp.json in project root)

"mcpServers": { "devops-practices": { "command": "python3", "args": ["-u", "~/.mcp-servers/devops-practices/mcp-server.py"], "env": {"PYTHONUNBUFFERED": "1"} } } }

Setup Steps:

Install the MCP server (see Installation section below)
Add configuration to ~/.claude.json (global) or .mcp.json (per-project)
Restart Claude Code/Desktop
MCP server runs automatically - no manual startup needed

Note: The -u flag and PYTHONUNBUFFERED ensure real-time logging for debugging.

What This Provides

This MCP server provides shared DevOps practices that are common across infrastructure projects:

Available Practices (11)

Organized using GG-SS prefix pattern (Group-Sequence) for better discoverability:

Naming Pattern: GG-SS-practice-name

GG = Group ID (01-04) - Functional category
SS = Sequence ID (01-03) - Order within group
Example: 03-02-air-gapped-workflow = Group 03, Sequence 02

Group Legend:

01 = Workflow & Processes (how to work effectively)
02 = Version Control & Project Management (git, issues)
03 = Infrastructure & Configuration (K8s, deployments, config)
04 = Documentation Standards (docs, READMEs, runbooks)

Group 01: Workflow & Processes

01-01-session-continuity - State tracking, handoff protocols, CURRENT-STATE.md
01-02-task-tracking - TRACKER.md, CURRENT-STATE.md, PENDING-CHANGES.md
01-03-efficiency-guidelines - When to script vs copy-paste, batching commands

Group 02: Version Control & Project Management

02-01-git-practices - Using git mv, commit conventions, backup protocols, GitLab Flow
02-02-issue-tracking 🆕 - In-repository Jira-like issue tracking system (Advanced)

Group 03: Infrastructure & Configuration

03-01-configuration-management ⭐ - Config organization, placeholders, environment isolation
03-02-air-gapped-workflow - Working across laptop, CloudShell, bastion, and EKS
03-03-standard-workflow - Common operational patterns and workflows

Group 04: Documentation Standards

04-01-documentation-standards - HOW/WHAT/WHY structure, naming conventions
04-02-readme-maintenance ⭐ - Directory documentation standards and best practices
04-03-runbook-documentation ⭐ - Mandatory session log standards and requirements

Available Templates (7)

TRACKER.md - Task tracking template (milestones)
CURRENT-STATE.md - Session handoff template
CLAUDE.md - Simplified project instructions template
RUNBOOK.md ⭐ - Session log template with all required sections
ISSUE.md 🆕 - Individual issue template (Advanced)
ISSUES.md 🆕 - Issue index template with stats dashboard (Advanced)
issues/README.md 🆕 - How to use the issue system (Advanced)

Architecture

devops-practices-mcp/

├── README.md # This file ├── mcp-server.py # MCP server implementation ├── requirements.txt # Python dependencies ├── .github/workflows/ci.yml # GitHub Actions pipeline ├── health-check.sh # Health validation script ├── practices/ # Shared practice documents (11 files, GG-SS organized) │ ├── 01-01-session-continuity.md │ ├── 01-02-task-tracking.md │ ├── 01-03-efficiency-guidelines.md │ ├── 02-01-git-practices.md │ ├── 02-02-issue-tracking.md # 🆕 Advanced: In-repo issue tracking │ ├── 03-01-configuration-management.md │ ├── 03-02-air-gapped-workflow.md │ ├── 03-03-standard-workflow.md │ ├── 04-01-documentation-standards.md │ ├── 04-02-readme-maintenance.md │ └── 04-03-runbook-documentation.md ├── templates/ # File templates (7 files) │ ├── TRACKER-template.md │ ├── CURRENT-STATE-template.md │ ├── CLAUDE-template.md │ ├── RUNBOOK-template.md │ ├── ISSUE-TEMPLATE.md # 🆕 Individual issue template │ ├── ISSUES.md # 🆕 Issue index with dashboard │ └── issues-README.md # 🆕 Issue system guide ├── tools/ # Automation tools 🆕 │ └── issue-manager.sh # CLI for managing issues └── config/ # MCP configuration └── mcp-config.json # Server configuration

MCP Tools

The MCP server provides 5 tools for Claude to query practices and templates:

Tool	Description	Example
`list_practices`	List all available practices	Returns list of 10 practices
`get_practice`	Get practice content by name	`get_practice("01-02-task-tracking")`
`list_templates`	List all available templates	Returns list of 4 templates
`get_template`	Get template content by name	`get_template("TRACKER-template")`
`render_template`	Render template with variable substitution	`render_template("TRACKER-template", {"PROJECT_NAME": "my-project"})`

Template Variable Substitution

Templates support ${VARIABLE} placeholders that are automatically substituted:

Auto-provided variables:

${DATE} - Current date (YYYY-MM-DD format)
${TIMESTAMP} - UTC timestamp (YYYYMMDDTHHMMz format)
${USER} - Current system user
${YEAR} - Current year

Custom variables: Pass any additional variables when rendering:

render_template("RUNBOOK-template", {

"SESSION_NUMBER": "1", "TITLE": "Kafka Deployment", "CLUSTER_NAME": "example-eks-uat", "OBJECTIVE_DESCRIPTION": "Deploy Kafka cluster to UAT" })

All ${...} placeholders in the template are replaced with provided values.

CI/CD Pipeline

This repository includes a GitHub Actions pipeline (.github/workflows/ci.yml) that automatically validates changes:

Pipeline Jobs

On every merge request and commit to main/develop:

health-check - Runs the comprehensive health check script
python-validation - Validates Python syntax and dependencies
practice-validation - Ensures all practice files exist
template-validation - Ensures templates contain variable placeholders
link-checker - Checks documentation cross-references

Benefits

✅ Prevents breaking changes from reaching main branch
✅ Catches missing files or syntax errors automatically
✅ Ensures consistent quality standards
✅ No manual validation needed

Pipeline Status

Check pipeline status in GitHub:

Green checkmark ✅ - All checks passed, safe to merge
Red X ❌ - C

Only the beginning is shown; read the rest in the repo

Devops Practices

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

DevOps Practices - MCP Server

Why This MCP Server?

How It Works

What This Provides

Available Practices (11)

Group 01: Workflow & Processes

Group 02: Version Control & Project Management

Group 03: Infrastructure & Configuration

Group 04: Documentation Standards

Available Templates (7)

Architecture

MCP Tools

Template Variable Substitution

CI/CD Pipeline

Pipeline Jobs

Benefits

Pipeline Status