Devops Practices

Name: Devops Practices
Author: ai-4-devops

作者：ai-4-devops版本 1.4.0i★ –i在你的电脑上运行

注册名称io.github.ai-4-devops/devops-practices

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 ai-4-devops 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 1394 个服务器的 0%
发布到注册中心的时间比此分类中其他 1394 个服务器的 6% 更新
基础检查结果等于或优于此分类中其他 1394 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Devops Practices 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.4.0）于9个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新

安装

Desktop Commander

作者：wonderwhy-er

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

在你的电脑上运行★ 10,225MIT16天前更新

安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分；其余内容请在仓库中阅读