A
AIops-tools/CICD-AIops
Governed AI-ops for self-managed GitLab and self-hosted Gitea.
更新 2026-10-30
在 GitHub 查看 ↗直链 · 无中转页
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 0 ★ · AIops-tools/CICD-AIops · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
AIops-tools/CICD-AIops;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# CICD AIops
以下摘录自该仓库的 README(片段)
> Audit availability: Real writes require a committed pending audit row and stop before contacting the platform if storage is unavailable. Reads and previews may continue with a warning; new audit rows store outcome summaries rather than full responses.
Governed AI-ops for self-managed GitLab and self-hosted Gitea.
cicd-aiops is for the team running its own CI/CD forge — a GitLab instance
or a Gitea server on your hardware, in your lab, behind your VPN — who want an
AI agent that can answer "why did the pipeline fail?", "which runner is
wedged?", "where did 40 GB of artifact storage go?" and "what work went
stale?" and then act (retry, cancel, pause, delete, protect) only through
an audited, budgeted, risk-tiered, undo-recorded governance harness. It is not
a SaaS integration: it speaks the GitLab REST API v4 and the Gitea API v1
directly against your server, with credentials encrypted at rest.
> Verification status: modelled from each project's public API docs and
> exercised against mocked HTTP responses; there is no recorded end-to-end run
> against a live server yet. cicd-aiops doctor is the fastest live check —
> see docs/VERIFICATION.md.
> Routing: Do NOT use this for Kubernetes deploy state — use k8s-aiops.
> This tool ends at the CI/CD server's API (pipelines, runners, artifacts,
> repo hygiene).
## What this tool does, and does not, decide
It delivers CI/CD operations — reads and writes — accurately and efficiently, and
records every one of them. It does not decide whether a write is allowed to
happen. That is the agent's judgement, or the permission of the token you connect
it with: give it a GitLab/Gitea access token without write scope and the writes
fail at the server — the place that actually owns the permission.
So there is no read-only switch, no policy file, no approval gate to configure.
The one thing the tool guarantees is that nothing is silent: every call, over
MCP and over the CLI alike, lands an audit row in ~/.cicd-aiops/audit.db,
and destructive writes still capture their before-state and record an inverse
where one exists.
> Each tool declares a risk_level, kept in agreement with its [READ]/[WRITE]
> documentation tag by a test, and carried into the audit row as a descriptive
> tier — so a reviewer can see at a glance that a row was a high-risk delete. It
> is a label, not a gate.
Running a smaller / local model? See
agent-guardrails.md — it lists
the guardrails this tool enforces for you (so you don't spend prompt budget
restating them) and gives a ready-made system prompt for what's left.
## Quick start
### As a Claude Code plugin
One install gives an agent both the skill and the MCP server:
/plugin marketplace add AIops-tools/marketplace
/plugin install cicd-aiops@aiops-tools
The MCP server is fetched with uv and pinned to the
package version this plugin declares, so an audit row can be traced back to the
code that wrote it. Credentials are still configured with cicd-aiops init — see below.
### As an OpenClaw plugin
The same bundle is published on ClawHub, where one
install delivers the skill and its MCP server together:
bash
openclaw plugins install clawhub:@zw008/cicd-aiops
openclaw skills info cicd-aiops # expect: Visible to model: yes
Governed AI-ops for self-managed GitLab and self-hosted Gitea.
cicd-aiops is for the team running its own CI/CD forge — a GitLab instance
or a Gitea server on your hardware, in your lab, behind your VPN — who want an
AI agent that can answer "why did the pipeline fail?", "which runner is
wedged?", "where did 40 GB of artifact storage go?" and "what work went
stale?" and then act (retry, cancel, pause, delete, protect) only through
an audited, budgeted, risk-tiered, undo-recorded governance harness. It is not
a SaaS integration: it speaks the GitLab REST API v4 and the Gitea API v1
directly against your server, with credentials encrypted at rest.
> Verification status: modelled from each project's public API docs and
> exercised against mocked HTTP responses; there is no recorded end-to-end run
> against a live server yet. cicd-aiops doctor is the fastest live check —
> see docs/VERIFICATION.md.
> Routing: Do NOT use this for Kubernetes deploy state — use k8s-aiops.
> This tool ends at the CI/CD server's API (pipelines, runners, artifacts,
> repo hygiene).
## What this tool does, and does not, decide
It delivers CI/CD operations — reads and writes — accurately and efficiently, and
records every one of them. It does not decide whether a write is allowed to
happen. That is the agent's judgement, or the permission of the token you connect
it with: give it a GitLab/Gitea access token without write scope and the writes
fail at the server — the place that actually owns the permission.
So there is no read-only switch, no policy file, no approval gate to configure.
The one thing the tool guarantees is that nothing is silent: every call, over
MCP and over the CLI alike, lands an audit row in ~/.cicd-aiops/audit.db,
and destructive writes still capture their before-state and record an inverse
where one exists.
> Each tool declares a risk_level, kept in agreement with its [READ]/[WRITE]
> documentation tag by a test, and carried into the audit row as a descriptive
> tier — so a reviewer can see at a glance that a row was a high-risk delete. It
> is a label, not a gate.
Running a smaller / local model? See
agent-guardrails.md — it lists
the guardrails this tool enforces for you (so you don't spend prompt budget
restating them) and gives a ready-made system prompt for what's left.
## Quick start
### As a Claude Code plugin
One install gives an agent both the skill and the MCP server:
/plugin marketplace add AIops-tools/marketplace
/plugin install cicd-aiops@aiops-tools
The MCP server is fetched with uv and pinned to the
package version this plugin declares, so an audit row can be traced back to the
code that wrote it. Credentials are still configured with cicd-aiops init — see below.
### As an OpenClaw plugin
The same bundle is published on ClawHub, where one
install delivers the skill and its MCP server together:
bash
openclaw plugins install clawhub:@zw008/cicd-aiops
openclaw skills info cicd-aiops # expect: Visible to model: yes
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/aiops-tools-cicd-aiops/)
- 来源
- awesome · https://github.com/AIops-tools/CICD-AIops
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。