cirdan
This server exposes a broad agentic operations surface: it maps and explores infrastructure, answers graph/dependency questions, inspects incidents/logs/state, executes audited actions, and generates evidence-backed views and reports.
Map and fingerprint environments: detect runtimes, clouds, IaC, and telemetry; run full static + live discovery and regenerate artifacts.
Explore the infrastructure graph: query what depends on what, fetch nodes/neighbors, find shortest paths, list services/dependencies/dependents/public entrypoints/runtime workloads.
Gather operational evidence: tail logs, get live component state, and cluster recent error/warning events.
Work with incidents: list incidents (with optional detection pass), and get evidence-backed markdown explanations.
Act safely: list available actions for a component, execute action IDs, and verify their outcomes — all recorded and audited.
Enrich knowledge: manually add nodes/edges with evidence, annotate existing nodes, and see enrichment targets left by scanners.
Generate outputs: create agentic UI views (HTML/MD/JSON) and regenerate INFRA_REPORT.md.
Audit everything: retrieve recent audit entries showing what was observed, generated, executed, and verified.
Integrates with Docker to fingerprint, graph, and monitor containers and services, enabling incident detection and operational actions through the agent.
Integrates with Kubernetes to fingerprint, graph, and monitor clusters, workloads, and resources, enabling incident detection and operational actions through the agent.
Integrates with Terraform to analyze infrastructure-as-code declarations and detect drift against live infrastructure, enabling drift detection and operational actions.
Cirdan
Cirdan is an on-call software repair agent. A production alert fires — Grafana,
Alertmanager, or Slack. Cirdan resolves the affected service and its repo from the
explicit services: registry in cirdan.yaml, reproduces the failure in an isolated
runner (Docker Compose or Kubernetes), has a coding agent fix the code — your own
logged-in Claude Code / Codex CLI, or an API provider — re-verifies the fix against
the pinned reproduction probe and the repo's test suite, and opens a verified pull
request. When policy allows, it merges, deploys, and verifies production recovery,
stopping at manual_required with full evidence when recovery fails.
alert ─▶ resolve service + repo (the services: registry) ─▶ reproduce in an isolated runner
─▶ coding agent fixes the code ─▶ verify (pinned repro probe + sandboxed test suite)
─▶ verified PR (@cirdan review loop; CI checks watched) ─▶ optional merge + deploy
─▶ verify recovery in productionThe job it does: when an alert fires at 3am for a code-shaped failure, a verified fix PR (or a completed deploy plus recovery confirmation) is waiting instead of a page.
Cirdan is deliberately not an infrastructure mapper, a topology explorer, an observability dashboard, a generic agent launcher, or a ChatOps bot. It repairs the services you register — nothing is discovered, and nothing is repaired implicitly.
Quickstart
pipx install "cirdanops[all]" # or uv / pip / npm / brew / curl / docker — see Install
cirdan setup # opens the local, loopback-only setup UIcirdan setup walks one short path and shows a readiness banner that flips to
"Ready to repair" only when this install can actually fix something:
Choose a pathway — Use the CLI (the tools already logged in on this machine) or Use the API (managed credentials + a GitHub App). See Two ways to run.
Connect an alert source — a Grafana webhook (+ HMAC), native Alertmanager intake, or Slack.
Select repair repositories — in Source Code Connection, Cirdan lists the repos your
ghlogin can push to; pick which ones it may repair. Only selected repositories are ever repaired.Prove routing — the Alert routing step synthesizes a sample alert (or takes a real payload you paste) and must show it resolving to a selected repository and routing to a code-repair pipeline.
Start the daemon and post a demo alert:
cirdand serve --http
curl -X POST localhost:8090/v1/ingest/grafana -d @examples/demo/alert.firing.jsonThe runnable demo in examples/demo/ wires this end to end. The
same checklist is available headlessly — cirdan status --checks prints the identical
table and exits 1 until the install is ready. Useful setup flags:
cirdan setup --terminal— the text step flow instead of the UIcirdan setup --all— run every step without prompting (scripts / CI)cirdan setup --system— machine-level scope in~/.cirdaninstead of a repo
Related MCP server: NEAT MCP Server
Install
From PyPI (recommended):
uv tool install "cirdanops[all]"
# or
pipx install "cirdanops[all]"
pip install "cirdanops[all]"Without Python — npm / Homebrew / curl:
npx -y @cirdanops/cli serve-mcp # run the MCP server, zero install
npm install -g @cirdanops/cli # or put the `cirdan` command on your PATH
brew install adanb13/tap/cirdan # macOS / Linux (Homebrew)
curl -LsSf https://raw.githubusercontent.com/adanb13/cirdan/main/packaging/install.sh | sh
# Windows: irm https://raw.githubusercontent.com/adanb13/cirdan/main/packaging/install.ps1 | iexThese ship a self-contained binary — no Python 3.11+ required. Supported: macOS (arm64), Linux x64/arm64 (glibc), Windows x64. On Intel Macs, Alpine/musl, or other platforms, use the PyPI install above.
Then set it up in one command (see Quickstart):
cirdan setup # inside a repo
# or, machine-level scope in ~/.cirdan:
cirdan setup --systemBoth open the same guided setup: choose a pathway, connect an alert source + GitHub, select repair repositories, prove routing, and start the always-on daemon.
Targeted installs: cirdanops[mcp], cirdanops[api], cirdanops[slack],
cirdanops[agent], cirdanops[github-app], cirdanops[secrets], or combinations
like cirdanops[api,mcp]. The sandbox runners need no extras — they use the
docker/kubectl CLIs already on your PATH.
Prerequisites by platform (Python 3.11+ and uv or pipx):
# macOS
brew install python@3.12 uv
# Windows
winget install astral-sh.uv
# Ubuntu / Debian
sudo apt install python3.12 python3-pip pipx
# or get uv:
curl -LsSf https://astral.sh/uv/install.sh | shDocker (no Python needed):
# run the always-on repair daemon: alert receiver + isolated repair runner,
# using the host's Docker for sandboxes
docker run -d \
-v "$PWD":/workspace:ro \
-v /var/run/docker.sock:/var/run/docker.sock \
-p 127.0.0.1:8090:8090 \
ghcr.io/adanb13/cirdan(or docker compose up with the provided docker-compose.yml)
From source (latest unreleased):
pip install "cirdanops[all] @ git+https://github.com/adanb13/cirdan.git"Two commands are installed:
Command | What it is |
| Human/agent CLI |
| Long-running Always ON daemon |
Local development (from a clone)
Contributors work from a clone with an editable virtualenv, so changes to the
working tree take effect immediately — no reinstall between edits. make install
creates .venv and installs the package (distribution name cirdanops) editable with
the [all,dev] extras — every runtime feature plus the test toolchain:
git clone https://github.com/adanb13/cirdan.git
cd cirdan
make install # ≈ python3 -m venv .venv && .venv/bin/pip install -e ".[all,dev]"
make test # .venv/bin/python -m pytest tests/ -qRequires Python 3.11+. The manual two-line equivalent works on a standard Python;
make install additionally handles the pip-less-venv case (it falls back to
python3 -m venv --without-pip and bootstraps pip into the venv).
The editable install puts both console scripts in .venv/bin, running working-tree
code with no rebuild:
.venv/bin/cirdan setup # or: .venv/bin/python -m cirdan.cli.main setup
.venv/bin/cirdand serve --http
.venv/bin/python -m pytest tests/test_slack_events.py -q # a single test moduleCommon Make targets (make help lists them all):
target | what it does |
| create |
| run the full pytest suite |
| build the sdist + wheel into |
| reset a project's onboarding so |
| build and drive the runnable stack in |
On a headless box with no OS keyring, storing credentials during
cirdan setupneeds a master key in the environment first:export CIRDAN_MASTER_KEY=$(.venv/bin/python -c 'import os,base64;print(base64.b64encode(os.urandom(32)).decode())').
Two ways to run: Use the CLI / Use the API
The first setup screen picks a deployment posture (deployment_mode: in
cirdan.yaml), which gates everything after it:
Use the CLI (cli, the default) — Cirdan runs with the tools already logged in on
this machine. GitHub writes go through your gh auth login; the coding agent is a
detected, logged-in Claude Code or Codex CLI, spawned headless inside the isolated
repair workspace; the sandbox runner is your local Docker (or kubectl). The happy path
needs no stored keys and no GitHub App — an env-var API key and a GitHub App
remain available behind explicitly labeled "Advanced" toggles.
Use the API (api) — headless and managed, for shared/enterprise deployments.
Provider API keys are stored encrypted (cirdan secret; AES-256-GCM), GitHub writes
go through a GitHub App (guided manifest onboarding) with short-lived per-repo
installation tokens, and the enterprise security profile is derived automatically:
inherited gh auth and host-spawned CLI agents are refused at config load.
Both pathways end at the same readiness contract — the setup UI banner and
cirdan status --checks render the same table: repair repositories selected (each with a
resolvable repo) · an alert source connected · a routing proof (a sample or live
alert demonstrably resolved to a selected repository and routed to a code pipeline) ·
remediation.mode ∈ {develop, deliver} · a live-probed coding agent · a verified
GitHub write path including access to each selected repo · git on PATH · a
working sandbox runner · the daemon running. Every red row shows the exact fix
command or the setup step that resolves it.
Legacy configs load forever: deployment_mode: single-user reads as cli,
business as api, and the file text migrates on the next setup save.
Configuration
cirdan setup writes cirdan.yaml for you; everything is also hand-editable — see
cirdan.yaml.example. The heart of the file is the
services: registry: the explicit list of services Cirdan may repair, how alerts
resolve to them, and where their code lives.
services:
- name: checkout-api # canonical id (lowercase, node-id-safe)
repo: acme/checkout # "org/name" — the PR / repair target
aliases: [checkout, checkout-svc] # extra alert-label names for this service
match_labels: {team: payments} # optional exact label matchers (first match wins)
deploy: # how it runs in prod + how the runner rebuilds it
kind: compose # compose | k8s | helm
compose_service: checkout-api # defaults to the entry name
compose_files: [docker-compose.yml]
deploy_workflow: deploy.yml # per-service GitHub Actions deploy (optional)
telemetry_service: checkout # Loki/PromQL service label; defaults to name
- name: payments-api
repo: acme/payments
source_root: ~/src/payments # local checkout (cli pathway only)
deploy:
kind: k8s
namespace: prod
workload: payments-api # kubernetes_kind defaults to DeploymentAlerts resolve to a service by an explicit cirdan_node label, then match_labels,
then a ladder of common labels (service, service_name, app, job,
deployment, statefulset, pod, container, the host of instance,
annotations.service, alertname) matched against names + aliases. There is no
implicit default: an alert that matches nothing opens a triage incident and never
auto-repairs "the only registered repo".
Routing policy. Every alert source flows through one first-match-wins policy:
routing_policy:
rules:
- when: {service: checkout-api, severity: [high, critical]}
pipeline: full_remediation # may merge/deploy — only under mode: deliver + the auto_* gates
- when: {source: slack}
pipeline: triage_onlyWith no matching rule, an alert that resolves to a registered service with a
resolvable repo defaults to reproduce_and_pr_only at qualifying severity
(responder.severities, default high/critical); everything else fails safe to
triage_only. Pipelines, by decreasing depth: full_remediation ·
reproduce_and_pr_only · lightweight_pr_only · triage_only.
Safety gates (under source_hosts.github and remediation):
gate | default | what it does |
|
| a PR opens only when the failure was reproduced (baseline probe failed) AND the fix verified (post-fix probe passed) |
|
| additionally require a passing sandboxed repo-test run before any PR |
|
| enable GitHub-native auto-merge on Cirdan PRs — branch protection and reviewers still gate the real merge; Cirdan never force-merges |
|
| master switch for delivery: deploy the merged fix and re-verify in production |
|
| block deploy dispatch until the merge commit's CI checks are green (block-only: it can stop a deploy, never start one) |
|
| ceiling on what any pipeline may do; |
A failed deploy or failed production verification stops the delivery at
manual_required, with the failure evidence notified and audited — Cirdan stops
at manual intervention (automatic rollback is deliberately deferred).
Commands
cirdan setup # guided setup: loopback UI (default) or --terminal
cirdan install --project # scripted variant: hook agents, register MCP, arm responder, start daemon
cirdan incidents # detection pass + list incidents
cirdan explain <incident-id> # evidence-backed explanation
cirdan respond <incident-id> # write the incident brief + invoke the responder once under a mode
cirdan remediate <incident-id> # durable fix: isolated workspace → reproduce → fix → verify → PR
cirdan deliver <incident-id> # manually drive an in-flight delivery (merge → deploy → prod-verify)
cirdan watch # foreground event + incident stream
cirdan status [--checks] # daemon status; --checks runs the full readiness checklist
cirdan stop # stop the daemon for this scope
cirdan secret set|get|list|delete # encrypted credential store (provider keys, App key)
cirdan slack-app # emit the importable Slack app manifest for the configured intake
cirdan preview-intake # dry-parse a sample payload; --source/--service runs the routing proof
cirdan serve-mcp # MCP server (stdio; --transport streamable-http)Always ON
cirdand serve # ingest alerts, detect incidents, repair, deliver — forever
cirdand serve --http # + the HTTP API (alert ingestion endpoints)
cirdand serve --http --mcp # + MCP mounted at /mcpThe daemon runs supervised loops — access refresh, alert ingestion + incident
detection, delivery, PR-checks watching, @cirdan comment handling, and the Slack
inbox (plus the Socket Mode client and webhook wakers, as configured). A crashing
loop logs and restarts; it never takes the daemon down.
One instance per scope: a second cirdand serve (or cirdan watch) against the same
scope is refused with the running pid. cirdan status / cirdan stop (also available
on cirdand) inspect and shut it down.
Agent integration
Cirdan is also a tool surface for your coding agents: the same engine behind the CLI
is exposed over MCP with exactly six read/evidence tools — list_incidents,
explain_incident, get_recent_errors, get_logs, get_state, and get_audit.
get_logs and get_state take a registered service name (or alias) from
services: and resolve the live container/pod themselves. Everything returned is
redacted.
cirdan install --project # full guided setup (recommended)
cirdan setup # re-run the guided setup anytime
cirdan install --platform claude # .claude/skills/cirdan/SKILL.md + CLAUDE.md + .mcp.json
cirdan install --platform codex # AGENTS.md + .codex/cirdan.md
cirdan install --platform cursor # .cursor/rules/cirdan.mdc + .cursor/mcp.json
cirdan install --platform gemini # GEMINI.md
cirdan install --platform vscode # .github/copilot-instructions.md + .vscode/mcp.json
cirdan install --platform windsurf # .windsurf/rules/cirdan.md (MCP: global config)
cirdan install --platform roo # .roo/rules/cirdan.md + .roo/mcp.json
cirdan install --platform cline # .clinerules/cirdan.md (MCP: editor UI)
cirdan install --platform opencode # AGENTS.md + opencode.json
cirdan install --platform goose # .goosehints (MCP: global config)
cirdan install --platform generic # .agents/skills/cirdan/SKILL.md + AGENTS.mdcirdan install --project is a guided setup that leaves Cirdan running the repair
loop, not just documented:
detects the agents on your machine (claude/codex/cursor/gemini/vscode/windsurf/opencode/goose config or CLIs) and writes instruction files for exactly those (plus generic
AGENTS.md)registers the MCP server in
.mcp.jsonarms the incident responder so daemon alerts route to your agent
starts the always-on daemon (detached;
cirdand status/cirdand stop)
Steps 3–4 are prompted (default yes) or driven by flags for scripts:
--responder/--no-responder, --daemon/--no-daemon, --all-platforms. Re-run any of
it later with cirdan setup, which shows each step's current state and only proposes
what's missing. Installs are idempotent and never touch content outside Cirdan's own
marker block.
Supported agents. First-class auto-registration (native instruction file + MCP where the agent supports a writable config) covers Claude Code, Codex, Cursor, Gemini, VS Code (+ GitHub Copilot), Windsurf, Roo Code, Cline, opencode, and Goose. Any other agent works through the generic AGENTS.md + .agents/skills/cirdan/SKILL.md. Auto-detection finds claude/codex/cursor/gemini/vscode/windsurf/opencode/goose; pass --platform roo or --platform cline explicitly (they're VS Code extensions with no CLI to detect, and Cline keeps MCP config in editor storage, so add that one through its UI).
For any MCP client not listed, register Cirdan by hand — no Python required:
// npx form — zero install
{ "command": "npx", "args": ["-y", "@cirdanops/cli", "serve-mcp"] }
// or, if `cirdan` is already on PATH (pip / npm -g / brew / curl install):
{ "command": "cirdan", "args": ["serve-mcp"] }HTTP API
With the [api] extra, cirdand serve --http exposes /health, /incidents,
/incidents/{id}, /incidents/{id}/explain, /audit, the alert intake under
/v1/ingest/{grafana|alertmanager|…} (plus /v1/ingest/slack/events and a
signature-verified /v1/ingest/github webhook waker), /v1/slack/interactions, a
minimal OTLP/HTTP JSON receiver at /v1/logs, and the setup UI + API under /setup.
Add --mcp to mount the MCP server at /mcp. State-changing routes are guarded —
see SECURITY.md.
Upgrading
Nothing happens automatically — PyPI is pull-only, so an installed version keeps working as-is until you upgrade. New installs always get the latest release. Upgrading is one command, matching however you installed:
Installed via | Upgrade command |
|
|
|
|
|
|
npm ( |
|
Homebrew |
|
curl installer | re-run the install script (it fetches the latest) |
Docker |
|
Two operational notes: existing cirdan-out/ artifacts and the SQLite store are compatible across releases so far (a schema-version key + migration will land before 1.0). And the CLI prints a single dim line on stderr when a newer release exists (checked at most once a day, interactive terminals only) — silence it with CIRDAN_NO_UPDATE_CHECK=1.
Upgrading from the mapping releases (≤ 0.9)
Cirdan committed to a single product: the repair workflow. The infrastructure-mapping surface — the graph/exploration commands, runtime profiles, and their artifacts — was removed. Removed commands and what replaces them:
Removed command | What replaces it |
| the explicit |
|
|
|
|
Old configs keep loading: adapters:, enrich:, and profile: keys are accepted and
ignored (profile warns once — Cirdan always runs the repair workflow), and
deployment_mode: single-user/business normalize to cli/api. The [map] and
[terraform] extras are gone from packaging. Old artifacts (infra.graph.json,
INFRA_REPORT.md, infra.html, fingerprint.json, …) simply stop being written —
Cirdan never deletes your files.
Security
Cirdan mirrors the access of the process it runs in and never escalates; everything it writes is redacted and audited. The two postures draw different trust boundaries: "Use the CLI" runs your own logged-in tools with your own permissions, while "Use the API" enforces the enterprise profile (GitHub App + stored keys, no host CLIs). Details — including network behavior and why PRs can only ever target the configured repo — in SECURITY.md.
License
Apache-2.0
Available Tools
27 toolsannotate_nodeA
Attach evidence or attributes to an existing node without changing its confidence.
Inputs: node_ref (required), evidence, attrs. Returns: result
execute_actionA
Execute an action id from list_available_actions. Recorded, redacted, audited.
Inputs: action_id (required). Returns: result
explain_incidentC
Evidence-backed markdown explanation of an incident.
Inputs: incident_id (required). Returns: result
fingerprint_systemB
Detect runtimes, clouds, IaC, and telemetry with confidence and evidence.
Inputs: no named parameters. Returns: result
generate_reportA
Regenerate INFRA_REPORT.md and return its contents.
Inputs: no named parameters. Returns: result
generate_viewB
Generate an Agentic UI view ('show me …') and save html/md/json artifacts.
Inputs: request (required). Returns: result
get_access_contextA
What the current agent/session can access (capability mirror, not permissions).
Inputs: no named parameters. Returns: result
get_auditC
Recent audit entries: what Cirdan observed, generated, executed, verified.
Inputs: limit. Returns: result
get_enrichment_targetsC
What the deterministic scanners left unconnected: docs to read, isolated nodes, unlinked IaC, uncertain claims. Contribute findings via upsert_edge.
Inputs: no named parameters. Returns: result
get_logsC
Tail logs for a component through the owning live adapter.
Inputs: node_ref (required), lines. Returns: result
get_neighborsC
Neighborhood subgraph around a node.
Inputs: node_ref (required), depth. Returns: result
get_nodeA
Fetch one node (by id or fuzzy name) with evidence, attributes, and edges.
Inputs: node_ref (required). Returns: result
get_recent_errorsC
Recent error/warning events, clustered by message template.
Inputs: window_minutes, service. Returns: result
get_stateD
Live state of a component through the owning adapter.
Inputs: node_ref (required). Returns: result
list_available_actionsC
Actions currently possible against a component with this session's access.
Inputs: node_ref (required). Returns: result
list_dependenciesC
What a component depends on (transitive).
Inputs: node_ref (required). Returns: result
list_dependentsB
What depends on a component (transitive blast radius).
Inputs: node_ref (required). Returns: result
list_incidentsB
Open (and optionally resolved) incidents. Runs a detection pass by default.
Inputs: include_resolved, detect_first. Returns: result
list_public_entrypointsD
Everything reachable from outside, with the reasons.
Inputs: no named parameters. Returns: result
list_runtime_workloadsA
Current workloads (services, containers, pods, units) with live state.
Inputs: no named parameters. Returns: result
list_servicesB
All logical services with state and origin.
Inputs: no named parameters. Returns: result
map_infrastructureC
Run full discovery (static + live) and regenerate all cirdan-out artifacts.
Inputs: live. Returns: result
query_infra_graphC
Ask the graph a question, e.g. 'what depends on postgres?' or 'what broke?'.
Inputs: question (required). Returns: result
shortest_pathC
Shortest path between two components.
Inputs: source (required), target (required). Returns: result
upsert_edgeC
Contribute a relationship between existing nodes (ids or names). Evidence required.
Inputs: source (required), target (required), relation (required), evidence (required), +2 more. Returns: result
upsert_nodeB
Contribute a node the scanners missed. Evidence quotes required; recorded as INFERRED.
Inputs: node_id (required), type (required), name (required), evidence (required), +2 more. Returns: result
verify_actionB
Verify the outcome of a previously executed action (act-… record id).
Inputs: record_id (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 27 tools
Each tool targets a distinct operation or query: annotation, actions, incidents, fingerprinting, reports, views, graph queries, state, dependencies, entrypoints, runtime, services, etc. There is no functional overlap, and descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern (e.g., annotate_node, get_state, list_services). No mixing of case or style, making the set predictable for an agent.
With 27 tools, the count exceeds the recommended range for a coherent set. While each tool serves a specific purpose, the overall surface is heavy and may overwhelm an agent, suggesting some consolidation is possible.
The tool set covers the full lifecycle of graph management (get, list, upsert, query) and domain-specific tasks (incidents, actions, dependencies). Minor gaps include the absence of delete operations for nodes/edges and limited incident modification tools.
Maintenance
Related MCP Connectors
Deterministic IT asset registry operated by AI agents over MCP. Agents propose, humans approve.
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
Watches reliability, change safety, security and cloud cost across your code and clouds.
1Read-only server insight: why a Linux server or K8s cluster is slow, failing or changed.
Related MCP Servers
- AlicenseAqualityAmaintenanceagent-bom is an open security scanner and self-hosted control plane for AI, MCP, and cloud infrastructure. The default scan profile in MCP server mode exposes 8 MCP tools. Additional profiles provide inventory, findings, compliance, graph, and runtime workflows. See the published Glama release for its packaged version.81,158 PyPI38Apache 2.0

NEAT MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceProvides AI agents with a live architecture model of a codebase, enabling queries for root cause analysis, blast radius, and dependency traversal through MCP tools.34Apache 2.0- AlicenseNot gradedqualityDmaintenanceMCP server that provides guarded, audited, read-only access to ops tooling (alerts, metrics, logs, deploys, runbooks) and a triage agent that diagnoses incidents end-to-end with CI-verified root cause analysis.MIT
- AlicenseNot gradedqualityDmaintenanceA continuous, out-of-band trust and reliability layer for the MCP ecosystem. It fingerprints MCP server tool definitions, detects and classifies drift (e.g., rug pulls) via a severity taxonomy, maintains a hash-chained evidence ledger, and gates CI with SARIF—while also acting as an MCP server itself so agents can check a server's safety before binding.Apache 2.0