Best for
- DevOps teams
- SRE engineers
- Incident response teams
- On-call managers
- Platform engineers
- Development teams needing incident management
R
Rootly
Community
Rootly MCP Server: Incident management, on-call scheduling, and intelligent analysis
GitHub source repository ↗
64FMRS · C
Rootly MCP Server is a powerful tool that provides comprehensive incident management, on-call scheduling, and intelligent analysis capabilities. It supports multiple MCP clients and offers a rich set of tools for managing various DevOps operations. With dynamic tool generation and intelligent analysis features, it helps teams respond to and manage incidents more effectively.
Rootly MCP Server provides incident management, on-call scheduling, and intelligent analysis powered by Rootly API for Cursor, Windsurf, Claude, and other MCP clients.
Tools
list_incidents
List all incidents
get_incident
Get detailed information about a specific incident
create_incident
Create a new incident
update_incident
Update an existing incident
search_incidents
Search for incidents based on criteria
find_related_incidents
Find historically similar incidents using similarity analysis
suggest_solutions
Recommend solutions based on past successful resolutions
create_incident_action_item
Create an incident action item
list_incident_action_items
List action items for an incident
update_incident_form_field_selection
Update incident form field selections
list_teams
List all teams
get_current_user
Get current user information
list_services
List all services
list_severities
List all severity levels
get_alert
Get detailed information about a specific alert
list_alerts
List all alerts
get_alert_by_short_id
Get an alert by its short ID
list_escalation_policies
List all escalation policies
get_escalation_policy
Get detailed information about a specific escalation policy
list_on_call_roles
List all on-call roles
list_schedules
List all schedules
get_schedule_shifts
Get schedule shifts
get_oncall_handoff_summary
Get on-call handoff summary
get_shift_incidents
Get incidents during a shift
list_endpoints
List all endpoints
check_oncall_health_risk
Check on-call health risk
check_responder_availability
Check responder availability
collect_incidents
Collect incident data
create_override_recommendation
Create override recommendation
get_server_version
Get server version information
list_workflow_runs
create_incident_form_field_selection
create_workflow_task
get_alert_event
get_alert_group
get_alert_routing_rule
get_alert_source
get_alert_urgency
get_catalog
get_catalog_entity
get_cause
get_custom_form
get_environment
get_escalation_level
get_escalation_path
get_form_field
get_form_field_option
get_functionality
get_functionality_incidents_chart
get_functionality_uptime_chart
get_incident_action_items
get_incident_type
get_on_call_role
get_on_call_shadow
get_override_shift
get_schedule
get_schedule_rotation
get_service
get_service_incidents_chart
get_service_uptime_chart
get_severity
get_status_page
get_status_page_template
get_team
get_team_incidents_chart
get_user
get_workflow
get_workflow_form_field_condition
get_workflow_group
get_workflow_task
list_alert_events
list_alert_groups
list_alert_routing_rules
list_alert_sources
list_alert_urgencies
list_all_incident_action_items
list_catalog_entities
list_catalogs
list_causes
list_custom_forms
list_environments
list_escalation_levels
list_escalation_levels_paths
list_escalation_paths
list_form_field_options
list_form_fields
list_functionalities
list_incident_alerts
list_incident_form_field_selections
list_incident_types
list_on_call_shadows
list_override_shifts
list_schedule_rotation_active_days
list_schedule_rotation_users
list_schedule_rotations
list_shifts
list_status_page_templates
list_status_pages
list_users
list_workflow_form_field_conditions
Setup
- Use hosted service: No local installation required, use URL: https://mcp.rootly.com/mcp
- Local installation:
- Install Python 3.12 or higher
- Install uv package manager
- Set ROOTLY_API_TOKEN environment variable
- Run with uvx command: uvx --from rootly-mcp-server rootly-mcp-server
claude_desktop_config.json
{
"hosted": {
"url": "https://mcp.rootly.com/mcp",
"auth": "OAuth2 or API Token"
},
"local": {
"command": "uvx",
"args": [
"--from",
"rootly-mcp-server",
"rootly-mcp-server"
],
"env": {
"ROOTLY_API_TOKEN": "Your Rootly API token"
}
}
}
Fit and risk
Not for
- Organizations requiring fully local deployment
- Teams not using Rootly for incident management
- Simple applications without need for real-time alerting and incident management
Required permissions
- Requires Rootly API access
- May need OAuth2 authentication or API token
- May need write permissions for creating and updating incidents based on configuration
Risks and side effects
- API token leakage risk
- Dependency on Rootly service
- Network connectivity issues may affect functionality
- Large data requests may cause performance issues
Troubleshooting
- Check if API token is correctly set
- Verify network connection to Rootly service
- Confirm MCP client configuration is correct
- Check Rootly service status
- Review logs for detailed error information
Use cases
Incident response and management
On-call scheduling and coverage
Alert management and monitoring
Incident analysis and trending
Post-incident analysis and reviews
Service health monitoring
Team collaboration and communication
Supported clients
Claude DesktopFull support
Claude CodeFull support
CursorFull support
WindsurfFull support
Gemini CLIFull support
CodexFull support