Allows an AI client to manage cloud infrastructure, Kubernetes clusters, CI/CD pipelines, and DevOps tools using natural language.
別名 shittuay/DevOps-Agent, devops-agent, @devopsagent/mcp-server
- スター
- 0
- ツール
- —
- ダウンロード数(30日間)
- 612
- 最新バージョン
- 1.0.7
- 最終コミット
- 2026年11月14日
- ライセンス
- —
DevOps Agent MCPとは
DevOps AgentはMCPサーバーです。 Allows an AI client to manage cloud infrastructure, Kubernetes clusters, CI/CD pipelines, and DevOps tools using natural language.
プロジェクトのREADMEから生成された概要
DevOps Agent MCP server について
DevOps Agent provides an interface for managing cloud infrastructure and development operations through natural language. It connects to your existing AWS, Azure, and GCP accounts, as well as Kubernetes clusters and CI/CD systems like Jenkins, GitHub Actions, and GitLab. Users can interact with the system via a web application, a command-line interface, or by adding it as a custom MCP connector in Claude.ai.
The platform includes 749 tools across 18 modules, covering areas such as Terraform, Docker, Ansible, and monitoring tools like Datadog or Grafana. To prevent accidental damage, the system classifies tool calls by risk level and requires manual approval for dangerous operations like deletions or IAM changes. A sandbox mode is available for testing commands without affecting live environments.
Setup requires connecting cloud credentials and third-party integrations through the application settings. For local deployment, you need Python 3.11+, a PostgreSQL database, and an API key from Anthropic or Moonshot. The system ensures data privacy by storing encrypted credentials per user rather than using global environment variables.
できること
- 1Infrastructure ManagementAsk the agent to list or modify specific cloud resources like EC2 instances.
- 2Automated DevOps WorkflowsExecute complex, multi-step tasks such as auditing IAM permissions or troubleshooting Kubernetes pods.
- 3Safe Environment TestingSimulate infrastructure changes in a controlled setting to see results without touching real accounts.
- 4Incident ResponseManage on-call alerts and communication through integrated tools like PagerDuty.
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
DevOps Agent MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにDevOps Agent MCPをインストール
$ claude mcp add devops-agent -- npx -y @devopsagent/mcp-serverCursorにDevOps Agent MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"devops-agent": {
"command": "npx",
"args": [
"-y",
"@devopsagent/mcp-server"
]
}
}
}VS CodeにDevOps Agent MCPをインストール
.vscode/mcp.json
{
"servers": {
"devops-agent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@devopsagent/mcp-server"
]
}
}
}VS Code CLIにDevOps Agent MCPをインストール
$ code --add-mcp '{"name":"devops-agent","type":"stdio","command":"npx","args":["-y","@devopsagent/mcp-server"]}'Claude DesktopにDevOps Agent MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"devops-agent": {
"command": "npx",
"args": [
"-y",
"@devopsagent/mcp-server"
]
}
}
}CodexにDevOps Agent MCPをインストール
$ codex mcp add devops-agent -- npx -y @devopsagent/mcp-serverCodex config.tomlにDevOps Agent MCPをインストール
~/.codex/config.toml
[mcp_servers.devops-agent] command = "npx" args = ["-y", "@devopsagent/mcp-server"]
Gemini CLIにDevOps Agent MCPをインストール
$ gemini mcp add -s user devops-agent npx -- -y @devopsagent/mcp-serverGemini settings.jsonにDevOps Agent MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"devops-agent": {
"command": "npx",
"args": [
"-y",
"@devopsagent/mcp-server"
]
}
}
}設定
ANTHROPIC_API_KEYDATABASE_URLMOONSHOT_API_KEYSECRET_KEY
| 名前 | 説明 | 種類 |
|---|---|---|
| ANTHROPIC_API_KEY | — | |
| DATABASE_URL | — | |
| MOONSHOT_API_KEY | — | |
| SECRET_KEY | — |
自動チェック
実行日 2026年11月14日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。コードを読み、サーバーに必要最小限のアクセス権を与えてください。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能shittuay/devops-agent is public and reachablegithub.com/shittuay/devops-agent ↗合格
- パッケージがこのリポジトリをソースとして指定@devopsagent/mcp-server names shittuay/devops-agent as sourcenpmjs.com/package/@devopsagent/mcp-server ↗合格
- ビルドの来歴 (Sigstore 証明)No build attestation published for this release未チェック
- オープンソースライセンス (OSI)No license検出事項
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-12github.com/shittuay/devops-agent ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していないNo popular package one edit away from @devopsagent/mcp-server合格
- パッケージおよびその依存関係に重大な勧告なし1 resolved dependencies checked; no critical advisoryosv.dev ↗合格
- モデルへの隠れた指示がない0 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答HTTPS endpoint answered 401 (sign-in required)合格
README
GitHubで見るDevOps Agent
An AI DevOps assistant you talk to in plain English. It works on your own AWS, Azure and GCP accounts, Kubernetes clusters, CI/CD systems and on-call tools, with a safety check in front of every risky action.
- Live app: devopsagent.io
- Docs: devopsagent.io/docs (in the app) and the
docs/folder - Developer API: devopsagent.io/developers
What it does
- Chat with your infrastructure. Ask questions or give instructions ("list my EC2 instances", "scale the api deployment to 4 replicas", "why did last night's deploy fail?"). The agent picks from 749 tools across 18 modules and runs them against your own accounts.
- Workflows. 46 pre-built, step-by-step jobs (launch a web server, audit IAM, troubleshoot pods, self-host an LLM, re-run a failed pipeline, page on-call, and more) across 14 categories. Each opens a short form, then runs in chat.
- Safety. Every tool call is risk-classified. Deletes, terminations, IAM changes and other risky operations need approval before they run (see Approvals). Sandbox mode simulates everything without touching a real account.
- Your data stays yours. Cloud and integration credentials are stored per user, encrypted, and never shared with other users. The app never falls back to its own credentials.
| Area | Tools |
|---|---|
| AWS (EC2, VPC, IAM, RDS, Lambda, ECS, EKS, S3, CloudFormation, Route 53, and more) | 352 |
| Kubernetes | 76 |
| Git | 47 |
| GCP | 42 |
| Azure | 38 |
| CI/CD (Jenkins, GitHub Actions, GitLab) | 36 |
| Terraform | 26 |
| Docker | 22 |
| GitHub | 19 |
| PagerDuty and OpsGenie | 16 |
| Ansible | 13 |
| Prometheus, Datadog and Grafana | 12 |
| SonarQube | 12 |
| Nexus | 12 |
| Security audit / pentest (off by default) | 12 |
| Cost, compliance and change governance | 10 |
| Shell commands on the agent host | 2 |
Reachability probes (http_check, tcp_check) |
2 |
| Total | 749 |
Using the app
- Sign up at devopsagent.io and confirm your email.
- Connect a cloud account in Settings → Cloud Credentials. For AWS, the recommended option is an IAM role (one-click CloudFormation quick-create); access keys also work.
- Connect any third-party tools you use (GitHub, GitLab, Jenkins, PagerDuty, OpsGenie, Datadog, SonarQube, Nexus) in Settings → Integrations.
- Chat, or open Workflows and pick one.
Want to try it without a cloud account? Turn on Sandbox mode (Settings → Learning). Tool
results are simulated and labelled [Sandbox].
Plans: Free (20 credits a month), Starter ($29, 200 credits), Professional ($99, 1,000 credits) and Business ($299, 3,000 credits). Free and Starter use Kimi K3.1 Pro; Professional and Business use Claude. Extra credit packs are available on the Billing page.
Other ways in
- Claude.ai connector (MCP): add
https://devopsagent.io/mcpas a custom connector and sign in with your DevOps Agent account (and 2FA code, if you use 2FA). 704 tools are exposed this way. - Developer API:
/api-gateway/v1/*, authenticated with anX-API-Keyheader. See /developers. - Slack / Microsoft Teams: see the ChatOps page in the app.
Running it locally
Requirements: Python 3.11+, PostgreSQL (or let the tests use SQLite), and an Anthropic and/or Moonshot (Kimi) API key.
python3 -m venv venv && source venv/bin/activate
pip install -r requirements.txt
export SECRET_KEY=change-me
export ANTHROPIC_API_KEY=sk-ant-... # Claude tiers
export MOONSHOT_API_KEY=... # Kimi tiers
export DATABASE_URL=postgresql://user:pass@localhost:5432/devops_agent # required in production
python app.py # http://127.0.0.1:5000
New tables and columns are created automatically at startup. For a local Postgres and Redis, run
docker compose up db redis after setting POSTGRES_PASSWORD in .env (compose refuses to start
without it). The compose file's app service has no Dockerfile to build from, so run the app
itself with python app.py.
Cloud and integration credentials are not read from environment variables. Each user adds their own in Settings once the app is running.
Command-line mode
python main.py interactive # chat in the terminal
python main.py ask "list pods in the default namespace"
python main.py tools # list tools
The CLI has no signed-in user, so AWS, Azure and GCP tools refuse to run there (they only use
per-user credentials). Kubernetes works with your local kubeconfig when you set
K8S_USE_LOCAL_KUBECONFIG=true (on the hosted site it reaches the user's EKS clusters instead); local Git, Docker and Terraform work,
and integration tools work when you pass a token explicitly. See docs/USER_GUIDE.md.
Tests
pytest -q
Tests run against in-memory SQLite, so no database is needed. Two network-safety tests need public DNS and fail in fully offline sandboxes.
Project layout
app.py Flask app: pages, chat endpoints, startup
models.py SQLAlchemy models
src/agent/ Agent loop, safety classification, tool selection, guardrails
src/tools/ Tool modules (aws_tools.py, kubernetes_tools.py, ...)
services/ Business logic (credentials, workflows, approvals, billing, ...)
routes/ Blueprints for feature pages and APIs
api/v1/ Deprecated REST API (/api/v1); its handlers also serve /api-gateway/v1
templates/ Jinja2 pages
tests/ pytest suite
docs/ Guides and references
Contributors: read CLAUDE.md first. It records the security rules and invariants the code depends on (per-user isolation, SSRF guards, risk classification, guardrails), and CLAUDE_RUNBOOK.md records past incidents and fixes.
Removed features
These were removed in October 2026 and are no longer part of the app: Optimize, Monitoring (alert rules), Incidents (and playbooks), Analysis (root-cause analysis) and Predictive Scaling. Incident work now happens in chat, with the PagerDuty and OpsGenie tools and the Incident Response workflows.
Support
- In the app: the chat, or
/docs - Email: support@devopsagent.io
- Security issues: security@devopsagent.io (see /security)
DevOps Agent MCPのよくある質問
DevOps Agent MCPをClaude Codeに追加するには
ターミナルでclaude mcp add devops-agent -- npx -y @devopsagent/mcp-serverを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
DevOps Agent MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
How does the agent handle risky operations?
Every tool call is risk-classified, and risky operations like deletions or IAM changes require approval before they run.
Can I test the agent without a cloud account?
Yes, you can enable Sandbox mode in the settings to simulate tool results without touching a real account.
How is my data and credential security handled?
Cloud and integration credentials are encrypted and stored per user, ensuring they are never shared with other users.
How can I use this with Claude.ai?
You can add the DevOps Agent MCP URL as a custom connector in Claude.ai and sign in with your account.