grafana/mcp-grafana

Feature Request: Add update_incident tool (resolve, assign, update status/severity)

Open

#748 aberto em 14 de abr. de 2026

Ver no GitHub
 (4 comments) (1 reaction) (0 assignees)Go (368 forks)auto 404
good first issuehelp wanted

Métricas do repositório

Stars
 (3.078 stars)
Métricas de merge de PR
 (Mesclagem média 2d 3h) (37 fundiu PRs em 30d)

Description

Summary

The current incident toolset only supports create_incident, get_incident, list_incidents, and add_activity_to_incident. There is no way to update an existing incident — specifically to resolve it or assign it to a user/team — through the MCP server.

Motivation

In an on-call/triage workflow, the most common actions after creating an incident are:

  1. Assigning it to the engineer on-call or a specific team
  2. Resolving it once the issue is fixed

Without these, an AI agent using the Grafana MCP can open incidents but cannot close the loop — forcing the engineer to switch to the Grafana Incident UI for basic lifecycle management.

Proposed Solution

Add an update_incident tool (gated behind enableWriteTools like create_incident) that wraps the existing Grafana Incident API update endpoint.

type UpdateIncidentParams struct {
    IncidentID string `json:"incidentId" jsonschema:"description=The ID of the incident to update"`
    Status     string `json:"status,omitempty" jsonschema:"description=New status: 'active' or 'resolved'"`
    Severity   string `json:"severity,omitempty" jsonschema:"description=New severity level"`
    AssignedTo string `json:"assignedTo,omitempty" jsonschema:"description=User or team to assign the incident to"`
    Title      string `json:"title,omitempty" jsonschema:"description=Updated incident title"`
}

Use Cases

  • AI on-call agent resolves a Grafana incident after confirming the fix is deployed
  • AI agent assigns an incident to the on-call engineer automatically after triage
  • Updating severity after root cause is identified (e.g. downgrade from critical to minor)

Current Workaround

Using add_activity_to_incident to log a note like "Resolved — assigned to @engineer" is the only option today, but this doesn't actually change the incident state.

Related

  • tools/incident.go — where the new tool would live alongside CreateIncident and AddActivityToIncident
  • The enableWriteTools gate should apply here as well

Guia do colaborador