IncidentFlowIncidentFlowDocs
Developer Reference

Tools

The full IncidentFlow MCP tool catalog — 48 read-only and memory-write tools, grouped by domain.

IncidentFlow MCP exposes 48 tools: 44 operational tools across six domains plus 4 meta tools for discovery and diagnostics. Every tool is read‑only except knowledge_upsert, which writes to workspace memory.

All tools return the same response envelope, are scoped to the authenticated workspace, and never mutate clusters, deployments, or integrations.

Conventions

  • Accessread (observability only) or write (workspace memory only).
  • response_mode — many tools accept summary (default) or full to control payload size.
  • Allow‑lists — Grafana dashboards and Kubernetes namespaces are limited to what the workspace has approved.
  • Discovery — call incidentflow_capabilities for the authoritative, machine‑readable inventory with per‑tool safety metadata.

Kubernetes (17)

Read‑only cluster diagnostics through the IncidentFlow Kubernetes Agent.

ToolDescriptionAccess
k8s_connection_healthCheck whether the agent is online, the cluster is reachable, and core read‑only permissions work.read
k8s_agent_statusAgent registry status, version, heartbeat, and selected cluster identity.read
k8s_rbac_checkReport the read‑only Kubernetes permissions available to the agent.read
k8s_cluster_overviewSRE overview: pod health, unhealthy pods, deployment counts, warning events, top restarts, plus a health assessment.read
k8s_namespace_overviewRead‑only overview scoped to one allowed namespace (pods, events, deployments, services, restarts).read
k8s_list_namespacesList namespaces visible to the agent.read
k8s_list_podsPod health and readiness in a namespace — phase, container readiness, restarts, age.read
k8s_show_unhealthy_podsFind pods that are not ready, crash‑looping, pending, failed, or high‑restart, with reasons.read
k8s_get_podQuick health status for one pod — readiness, restart count, node, phase.read
k8s_describe_podStructured pod investigation report — the primary tool for why a pod is unhealthy.read
k8s_debug_podFull automated pod investigation: state, recent logs, related events, owner deployment.read
k8s_get_pod_logsStream recent, filtered/redacted container log lines (kubectl logs equivalent).read
k8s_list_deploymentsList deployments in an allowed namespace with rollout and availability metadata.read
k8s_get_rollout_statusDeployment rollout readiness, availability, and progress.read
k8s_list_servicesList services in an allowed namespace — type, ports, selectors.read
k8s_list_eventsNamespace events, warnings first and deduplicated with occurrence counts.read
k8s_analyze_workloadInspect a workload rollout, related pods, unhealthy status, and redacted recent logs.read

Argo CD (8)

Read‑only GitOps deployment context from the connected Argo CD integration.

ToolDescriptionAccess
argocd_connection_healthConnection health, authentication, RBAC, version, and application counts.read
argocd_list_applicationsList visible applications with filters (project, namespace, destination, health, sync).read
argocd_get_applicationNormalized application details — project, destination, sources, health, sync, recent history.read
argocd_get_application_resourcesResource‑tree metadata (manifests and Secret data intentionally omitted).read
argocd_get_sync_historyRecent sync/deployment history — revision, time, source, initiator.read
argocd_get_last_operationLatest operation state — phase, timing, message, sync revision, resource results.read
argocd_find_recent_deploymentsRecent deployment events across visible applications, with optional filters.read
argocd_analyze_applicationCompact health and sync analysis from status, last operation, history, and resource tree.read

Grafana / Prometheus (8)

Guarded, read‑only metrics from allow‑listed dashboards and datasources.

ToolDescriptionAccess
grafana_connection_healthRead‑only Grafana connection health: normalized status, datasource count, and warnings.read
grafana_list_dashboardsDiscover dashboards approved for the current workspace.read
grafana_get_dashboardDashboard metadata, panels, and datasource references for a known UID.read
grafana_extract_panel_queriesExtract the PromQL expressions embedded in an allow‑listed dashboard.read
grafana_metrics_queryPoint‑in‑time PromQL result through server‑side guardrails.read
grafana_metrics_query_rangePromQL time series over a bounded window through server‑side guardrails.read
analyze_dashboard_healthHealth summary for an allow‑listed dashboard over a time window (per‑panel series + anomaly flags).read
grafana_get_panel_viewRender one allow‑listed timeseries panel (Apps SDK view).read

Slack / Incidents (6)

Read‑only incident context, alert parsing, and correlation.

ToolDescriptionAccess
incident_summaryStructured incident summary — title, severity, status, affected services, timeline, recommendations.read
incident_thread_summarySRE‑focused human‑context summary of a Slack incident thread (no command execution).read
correlate_alertsGroup alerts by shared service, label affinity, and time proximity.read
external_status_checkPublic status for external providers (e.g. GitHub, AWS) — current status, incidents, history.read
slack_alerts_listRecent alerts from a configured Slack channel, parsed into structured incident context.read
slack_alert_thread_getParse a Slack alert thread — replies, commands, links, hypotheses, decisions.read

Knowledge (5)

Public documentation search, integration setup guidance, and private workspace memory.

ToolDescriptionAccess
integration_guideStructured, documentation‑backed setup/verify/troubleshoot guidance for an integration (Kubernetes, Slack, Grafana, Argo CD). Secret‑free command templates only.read
public_knowledge_searchSearch official IncidentFlow documentation and product knowledge.read
private_knowledge_searchSearch authenticated workspace knowledge — incidents, RCAs, postmortems, runbooks, service context.read
knowledge_getRetrieve one workspace document deterministically by id, point id, or exact title.read
knowledge_upsertCreate or update one workspace knowledge document (runbook, incident, RCA, postmortem, note).write

Meta (4)

Discovery and diagnostics. Excluded from the 44 operational count.

ToolDescriptionAccess
incidentflow_capabilitiesCanonical capability inventory grouped by category, with per‑tool safety metadata.read
mcp_versionServer version, release tag, build commit, image provenance, environment, and tool counts.read
incidentflow_auth_statusAuthenticated user, active workspace, role, and runtime environment.read
incidentflow_integrations_statusWhich integrations are connected for the active workspace.read

Schema strictness

Each tool publishes a JSON Schema for its response data. Owned, fully‑typed tools are strict (additionalProperties: false); tools that pass through upstream integration payloads are permissive (upstream fields tolerated). The strict tools today are k8s_agent_status, k8s_rbac_check, incident_thread_summary, knowledge_upsert, and mcp_version. Retrieve any schema from GET /schemas/{schema_id}.

On this page