Loading...
The Rootly MCP server allows users to manage incident response directly from their IDE by leveraging Rootly's API for incident management, on-call scheduling, and resolution.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
The Rootly MCP server allows users to manage incident response directly from their IDE by leveraging Rootly's API for incident management, on-call scheduling, and resolution.
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.
Performance is primarily limited by the Rootly API's response times and the network latency between the IDE and the MCP server. Smart pagination helps mitigate context window overflow.
Cost is primarily determined by Rootly API usage. Be mindful of the number of API calls made, especially when retrieving large datasets or performing frequent queries.
{
"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.
API Key
cloud
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.
The level of autonomy depends on the specific tool invoked and the permissions granted to the Rootly API key. Exercise caution when using tools that modify incident data.
Production Tip
Monitor the Rootly API usage and error rates to ensure the MCP server is functioning correctly and not exceeding API limits.
The required permissions depend on the tools being used. For full functionality, a Global API Key is recommended. Team API Keys or Personal API Keys may have limited visibility.
Use the provided JSON configuration snippets in your IDE's MCP settings, replacing `<YOUR_ROOTLY_API_TOKEN>` with your actual Rootly API token.
The MCP server will be unable to retrieve data or perform actions, and error messages will be displayed in the IDE.
Yes, but you will need to modify the `command` and `args` in the MCP configuration to point to your self-hosted instance.
Create a Team API Key or Personal API Key with limited permissions in Rootly.
No, the MCP server is configured for a single Rootly organization using the provided API key.
The MCP server is automatically updated when you open your editor. The package will be automatically downloaded and installed.