AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
MCP unreviewed MIT Self-run

Dojops

mcp-dojops-dojops · by dojops

⚡ AI Automation Engine

No reviews yet
0 installs
15 views
0.0% view→install

Install

$ agentstack add mcp-dojops-dojops

Open-source listing, not yet scanned by AgentStack. Follow the source repository for install instructions.

Security review

⚠ Flagged

1 finding(s); flagged for manual review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures
  • high Pipes remote content directly into a shell (remote code execution).

What it can access

  • Network access Used
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Reliability & compatibility

Not yet reviewed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude DesktopCursorWindsurf

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Dojops? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

DojOps

AI-powered automation engine for infrastructure, CI/CD, and security. Describe what you need. DojOps generates it, validates it, and writes it safely.

Quick start  ·  Capabilities  ·  Docs  ·  Skill hub  ·  Website  ·  Contributing


Why DojOps?

Writing Terraform, Kubernetes, and CI/CD configs by hand is slow. Using an LLM to generate them is fast but risky: no schema enforcement, no execution controls, no audit trail. Compliance teams can't sign off on configs they can't verify.

DojOps sits between you and your LLM provider. It constrains output to Zod schemas, validates configs with external tools (terraform validate, hadolint, kubectl dry-run), writes files through a sandbox with approval gates, and logs every action to a tamper-proof audit chain.

You → DojOps CLI → Agent Router → Specialist Agent → LLM Provider
                         ↓                ↓
                   Skill Engine     Schema Validation
                         ↓                ↓
                   Policy Engine → Sandbox → File Write → Audit Log

At a glance

| | | | ------------------------ | ------------------------------------------------------------------------------------------------------------------ | | 32 specialist agents | Terraform, Kubernetes, CI/CD, security, Docker, cloud, SRE, incident response, and more | | 38 built-in skills | .dops v2 manifests for GitHub Actions, Terraform, K8s, Helm, Docker, Nginx, Falco, Vault, Istio, EKS, and others | | 7 LLM providers | OpenAI, Anthropic, Ollama (local), DeepSeek, Mistral, Google Gemini, GitHub Copilot | | 10 security scanners | Trivy, Gitleaks, Checkov, Semgrep, Hadolint, ShellCheck, npm/pip audit, SBOM, license scan | | 12 packages | Modular monorepo - CLI, API, runtime, planner, executor, scanner, core, SDK, and more | | 23 REST endpoints | Full HTTP API with web dashboard, metrics, and token tracking | | 0 telemetry | Nothing leaves your machine except requests to your chosen LLM provider |


Quick start

# Install
npm i -g @dojops/cli

# Configure your LLM provider
dojops config

# Generate your first config
dojops "Create a Kubernetes deployment for nginx with 3 replicas"

Other install methods

# Homebrew (macOS / Linux)
brew tap dojops/tap && brew install dojops

# Shell script
curl -fsSL https://raw.githubusercontent.com/dojops/dojops/main/install.sh | sh

# Docker
docker run --rm -it ghcr.io/dojops/dojops "Create a Terraform config for S3"

See the installation guide for provider setup and configuration.


How it works

# Describe what you need - the right skill and agent are selected automatically
dojops "Create a Terraform config for S3 with versioning"

# Break complex goals into dependency-aware task graphs
dojops plan "Set up CI/CD for a Node.js app with Docker deployment"

# Execute the plan with approval workflow
dojops apply plan-abc123

# Autonomous mode - plan, execute, verify, self-repair
dojops auto "Add Kubernetes HPA and PDB to my deployment"

# Scan for vulnerabilities before shipping
dojops scan

# Interactive chat session with agent routing
dojops chat

# Web dashboard + REST API
dojops serve

Your prompt gets routed to the right specialist agent. The LLM output is locked to a Zod schema, validated by external tools, then written to disk through the sandbox. If something fails mid-plan, dojops apply --resume picks up where it left off.


Key capabilities

32 specialist agents - automatic routing based on your prompt

Every prompt is analyzed and routed to the best-fit agent. You don't pick agents manually - the router does it based on keyword matching and confidence scoring.

| Agent | Domain | What it handles | | ------------------------ | -------------- | ---------------------------------------------------------------- | | ops-cortex | orchestration | Meta-agent that coordinates across domains | | terraform-specialist | infrastructure | Terraform configs, modules, state management | | kubernetes-specialist | containers | K8s manifests, deployments, services, RBAC | | cicd-specialist | CI/CD | GitHub Actions, GitLab CI, Jenkins pipelines | | security-auditor | security | Vulnerability assessment, compliance checks | | docker-specialist | containers | Dockerfiles, Compose, multi-stage builds | | cloud-architect | cloud | AWS, GCP, Azure architecture decisions | | gitops-specialist | gitops | ArgoCD, Flux, GitOps workflows | | sre-specialist | reliability | SLOs, error budgets, reliability patterns | | incident-response | incidents | Runbook generation, root cause analysis | | cost-optimizer | cost | Cloud spend analysis, right-sizing | | chaos-engineer | resilience | Chaos experiments, failure injection | | platform-engineer | platform | Internal developer platforms, golden paths | | container-security | security | Image scanning, runtime policies, admission control | | secret-management | secrets | Vault, sealed secrets, rotation policies | | api-security-specialist | API security | OWASP API Top 10, rate limiting, auth patterns | | policy-engine-specialist | policy | OPA, Gatekeeper, policy-as-code | | + 15 more | | Network, database, compliance, observability, shell, Python, ... |

Create custom agents with dojops agents create or drop a YAML file in .dojops/agents/.

38 built-in skills - validated config generation for real DevOps tools

Each skill is a .dops v2 manifest with output guidance, best practices, and optional Context7 documentation. The runtime compiles a prompt from the skill definition and your input, sends it to the LLM, and validates the output.

| Skill | Format | What it generates | | -------------- | ---------- | -------------------------------------------------------- | | github-actions | YAML | CI/CD workflows, validated by actionlint | | terraform | JSON | HCL configs, validated by terraform validate | | kubernetes | YAML | Deployments, services, RBAC, validated by kubeconform | | helm | YAML | Charts, values files, templates | | ansible | YAML | Playbooks, roles, inventories | | docker-compose | YAML | Multi-service compose files | | dockerfile | Dockerfile | Multi-stage builds, validated by hadolint | | nginx | conf | Server blocks, reverse proxy, TLS | | prometheus | YAML | Alert rules, recording rules, targets | | grafana | JSON | Dashboard definitions | | cloudformation | JSON | AWS CloudFormation stacks | | argocd | YAML | Applications, ApplicationSets, projects | | vault | JSON | Policies, secret engines, auth methods | | istio | YAML | VirtualServices, DestinationRules, AuthorizationPolicies | | falco | YAML | Runtime security rules, macros, exceptions | | eks | YAML | EKS cluster configs, node groups, add-ons | | cert-manager | YAML | ClusterIssuers, Certificates, ACME config | | opa-gatekeeper | YAML | ConstraintTemplates, Constraints, Rego policies | | flux | YAML | GitRepository, Kustomization, HelmRelease | | trivy-operator | YAML | VulnerabilityReports, ConfigAuditReports | | shell | sh/bash | Shell scripts, validated by ShellCheck | | python | py | Python automation scripts | | powershell | ps1 | PowerShell scripts for Windows automation | | packer | JSON | Machine image definitions, validated by packer validate | | + 10 more | | Pulumi, Kustomize, Crossplane, Terragrunt, Makefile, ... |

Write your own skills as .dops v2 manifests and share them on the DojOps Hub. Skills are auto-installed from the Hub when a prompt matches.

7 LLM providers - tiered model routing across all of them

DojOps works with any of these providers. You pick one, or let the tiered router select the right model based on task complexity.

| Provider | Fast tier | Standard tier | Premium tier | | -------------- | ---------------- | ----------------- | ----------------- | | OpenAI | gpt-4o-mini | gpt-4o | o1 | | Anthropic | claude-haiku-4-5 | claude-sonnet-4-6 | claude-opus-4-6 | | Ollama (local) | llama3.2:3b | llama3.1:8b | llama3.1:70b | | DeepSeek | deepseek-chat | deepseek-chat | deepseek-reasoner | | Mistral | mistral-small | mistral-medium | mistral-large | | Google Gemini | gemini-2.0-flash | gemini-2.5-pro | gemini-2.5-pro | | GitHub Copilot | gpt-4o-mini | gpt-4o | o1 |

Simple prompts (makefile, basic configs) get the fast tier. Complex prompts (multi-service architectures, security hardening) get the premium tier. Agent routing always uses the fast tier to keep costs low.

Override with DOJOPS_MODEL=your-model or dojops config --model gpt-4o.

10 security scanners + auto-remediation - catch issues before they ship

Run dojops scan to check your project. Scanners run in parallel and results are aggregated into a single report.

| Scanner | What it checks | | ------------- | ------------------------------------------------ | | Trivy | Container images, filesystems, IaC misconfigs | | Gitleaks | Secrets, API keys, tokens in source code | | Checkov | Terraform, CloudFormation, K8s policy violations | | Semgrep | Custom SAST rules, code patterns | | Hadolint | Dockerfile best practices | | ShellCheck | Shell script correctness and portability | | npm audit | Node.js dependency vulnerabilities | | pip audit | Python dependency vulnerabilities | | Trivy SBOM | Software bill of materials generation | | Trivy License | License compliance scanning |

Use dojops scan --auto-fix to generate a remediation plan with confidence-scored fix suggestions. Pass --yes to apply safe fixes automatically.

Task planning and execution - decompose goals into dependency graphs

dojops plan breaks a complex goal into a directed acyclic graph of tasks. Each task is assigned to a specialist agent and a skill. Dependencies are tracked so tasks run in the right order, with parallel execution where possible.

$ dojops plan "Set up CI/CD with Docker deployment"

  Tasks (6):
    analyze-existing-ci          [cicd-specialist]
    create-docker-build-action   [docker-specialist]  (after: analyze-existing-ci)
    create-cd-workflow           [cicd-specialist]     (after: create-docker-build-action)
    update-ci-workflow           [cicd-specialist]     (after: create-docker-build-action)
    create-docker-compose        [docker-specialist]
    update-dockerfile            [docker-specialist]

  Plan saved as plan-9219de4f
  To execute: dojops apply plan-9219de4f

dojops apply runs each task through the sandbox: generate → verify → approve → write → audit. If a task fails, fix the issue and run dojops apply --resume to continue from where it stopped.

Autonomous mode - plan, execute, verify, and self-repair

dojops auto reads your project, plans changes, writes configs, runs verification, and self-repairs on failure in an iterative tool-use loop.

# Foreground - watch the agent work
dojops auto "Add Kubernetes HPA and PDB to my deployment"

# Background - check results later
dojops auto --background "Create a complete CI pipeline"
dojops auto runs abc123  # check status

The agent loop runs until the plan succeeds or reaches the retry limit. Each iteration: generate → validate → if errors → re-prompt with error context → retry.

REST API and web dashboard - 23 endpoints over HTTP

dojops serve starts an Express server with API key authentication, CORS, and optional TLS.

| Method | Path | What it does | | ------ | --------------- | -------------------------------------------------------- | | GET | /api/health | Auth status + provider check | | POST | /api/generate | Agent-routed LLM generation | | POST | /api/plan | Goal decomposition + optional execution | | POST | /api/debug-ci | CI log diagnosis | | POST | /api/diff | Infrastructure diff analysis with risk scoring | | POST | /api/scan | Run security scanners | | POST | /api/chat | Chat message with agent routing | | POST | /api/review | DevSecOps code review pipeline | | POST | /api/auto | Autonomous agent (background: HTTP 202) | | GET | /api/agents | List all specialist agents | | GET | /api/metrics | Dashboard metrics (overview, security, audit, tokens) | | GET | /api/history | Execution history with audit verification | | | + 11 more | Sessions, chat CRUD, metrics breakdowns, auto run status |

The web dashboard at http://localhost:3000 shows agent usage, scan findings, execution history, and token consumption. Protect it with DOJOPS_API_KEY or dojops serve credentials.

Security and audit - sandbox, policy engine, hash-chained logs

Every file write goes through the policy engine:

| Layer | What it enforces | | ---------------- | ------------------------------------------------------------ | | Write scope | Only paths matching skill's scope.write globs are writable | | File size limits | Rejects outputs exceeding configured limits | | Approval gates | Interactive confirmation before destructive writes | | Backup on update | .bak file created before overwriting existing configs | | Timeout | Operations killed after configured timeout | | Env restrictions | Only allowed environment variables are acces

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.