Loading...
{
"mcpServers": {
"rootly": {
"command": "uv",
"args": [
"tool",
"run",
"--from",
"rootly-mcp-server",
"rootly-mcp-server"
],
"env": {
"ROOTLY_API_TOKEN": "<YOUR_ROOTLY_API_TOKEN>"
}
}
}
}find_related_incidentsFinds historically similar incidents using TF-IDF similarity analysis.
Read-only operation; retrieves incident data for analysis.
suggest_solutionsRecommends actionable solutions by mining past incident resolutions.
Read-only operation; analyzes past resolutions to provide suggestions.
get_oncall_shift_metricsRetrieves on-call shift metrics for a specified time period, grouped by user, team, or schedule.
Read-only operation; fetches metrics without modifying data.
get_oncall_handoff_summaryProvides a summary of the current and next on-call personnel, along with incidents during their shifts.
Read-only operation; gathers on-call information and incident summaries.
get_shift_incidentsLists incidents during a specified time period, with filtering options for severity, status, and tags.
Read-only operation; retrieves incident lists based on specified filters.
check_oncall_health_riskDetects workload health risk in scheduled responders.
Read-only operation; analyzes on-call health data.
The Rootly MCP server offers convenient incident management from within an IDE. It is relatively safe for read-only operations. However, write operations should be performed with caution, ensuring the API key has appropriate, limited permissions to prevent unintended consequences.