MCP DevOps Toolbox
Provides read-only Git repository inspection using fixed, argument-separated Git commands to safely view repository information.
Validates Kubernetes YAML manifests for document shape and basic correctness without invoking Kubernetes CLIs or admission policies.
Summarizes Terraform plan output from an existing terraform show -json file, providing a high-level view of plan changes.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP DevOps ToolboxValidate the Kubernetes manifest at examples/pod.yaml"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP DevOps Toolbox
A small MCP-style JSON-lines server for safe, local DevOps inspection. It has no cloud or external API dependency. Maintained by Prashant Rajguru (email).
flowchart LR
C[MCP-style client] -->|strict JSON line| S[Tool router]
S --> P[Path allowlist]
P --> G[Read-only Git]
P --> K[Kubernetes YAML validator]
P --> T[Terraform plan summary]
P --> L[Sanitized log analysis]Quickstart
Requires Node 22.12+ and Git.
npm ci
npm run check
TOOLBOX_ROOT="$PWD" npm startRequest and sample response:
{"id":1,"tool":"validate_kubernetes","arguments":{"manifest":"examples/pod.yaml"}}
{"id":1,"result":[{"document":1,"valid":true,"errors":[]}]}Tools accept strict schemas and only canonical paths beneath TOOLBOX_ROOT. Git commands are fixed,
argument-separated and read-only. Terraform input is an already-generated terraform show -json
file. Log output is bounded and common credentials are redacted.
Related MCP server: Security & GRC MCP Server
Security
Run as an unprivileged user against a narrow dedicated root. Symlink resolution prevents directory escape. This process does not invoke shells or Kubernetes/Terraform CLIs. Redaction is defensive, not a data-loss-prevention boundary; do not feed it secrets or expose stdin/stdout to untrusted networks.
Status and limitations
Portfolio/reference status, not a complete MCP protocol SDK implementation. Kubernetes validation checks document shape, not OpenAPI schemas or admission policy. Log classification is heuristic. Terraform summaries trust valid JSON and do not evaluate policy or provider behavior.
License
MIT © 2026 Prashant Rajguru.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
Deep security scans of repos you own from your editor: dependency CVEs, SAST, git-history secrets.
Scan configs, files, or text for leaked secrets and obvious misconfigurations. Nothing stored.
Fail-closed policy guardrails for AI agents running kubectl, terraform, helm, and argocd.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides secure filesystem operations, HTTP fetching with SSRF protection, JSON validation, artifact logging, and optional Redis key-value storage through both stdio and HTTP transports. Features production-ready security controls including sandbox enforcement, allowlist validation, and comprehensive input validation.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables local security scanning and compliance gap analysis for code and text, detecting secrets, PII, and OWASP vulnerabilities, and assessing readiness across major frameworks like NCA, ISO 27001, NIST CSF, and SOC 2.-
- AlicenseNot gradedqualityAmaintenanceA secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.MIT
- AlicenseAqualityBmaintenanceLocal MCP server for AI agents and vibe coding safety: deterministic risk checks (payments, auth, database, secrets, infrastructure), sessions, checkpoints, policy inspection, and fix prompts. Runs over stdio against a local git repository; no language model judges risk.81Apache 2.0