Rootly MCP server

Read from the package source without running it. The installed server may list more.

• acknowledge_alert

  Marks a specific alert as acknowledged, indicating that it has been reviewed and noted by the user.

• add_form_field_optionwrite action

  Creates a new option for a form field, allowing you to define selectable values with optional styling and positioning.

• attach_alerts_to_incident

  Attach one or more alerts to an incident. This operation links existing alerts to an incident record for consolidated monitoring and tracking.

• create_alertwrite action
• create_alert_eventwrite action

  Creates a new note event attached to an alert. This allows adding contextual notes or updates to track alert activity and history.

• create_alert_groupwrite action

  Creates a new alert group to automatically organize and correlate incoming alerts based on specified criteria. Alert groups help reduce noise by bundling related alerts together within a configurable time window.

• create_alert_sourcewrite action
• create_alert_urgencywrite action

  Creates a new alert urgency level that can be assigned to alerts. Alert urgencies help categorize and prioritize alerts based on their importance.

• create_catalogwrite action

  Creates a new catalog with the specified name, description, and display settings. The catalog will be added to your catalog collection and can be organized with an icon and position.

• create_catalog_entitywrite action

  Creates a new catalog entity with the specified metadata. The entity will be added to the catalog and can be positioned within list displays.

• create_catalog_entity_propertywrite action

  Creates a new property for a catalog entity, associating a catalog field with a typed value. This establishes a key-value relationship within the catalog entity's property structure.

• create_catalog_fieldwrite action

  Creates a new field within a catalog to define custom attributes for catalog items. Fields can store text values or references to items in other catalogs, and can be configured to accept single or multiple values.

• create_causewrite action

  Creates a new cause with the provided name, description, and optional positioning. The cause type is fixed as 'causes'.

• create_custom_formwrite action

  Creates a new custom form that can be triggered via a Slack command. The form can include custom fields by referencing the form slug in field associations.

• create_dashboardwrite action

  Creates a new dashboard with customizable settings for data visualization and sharing. Configure the dashboard's appearance, refresh behavior, and data aggregation period.

• create_dashboard_panelwrite action

  Creates a new panel on a dashboard with specified visualization type, position, and data configuration. Panels are positioned using grid coordinates and can display various chart types or tables.

• create_environmentwrite action

  Creates a new environment with optional notification and messaging integrations. The environment serves as a deployment or organizational context that can be associated with Slack channels, email notifications, and visual styling.

• create_escalation_levelwrite action

  Creates a new escalation level within an escalation policy to define notification targets and timing for alert escalation. Each level specifies who gets notified and when, with configurable paging strategies.

• create_escalation_level_pathwrite action

  Creates a new escalation level within an escalation path, defining notification targets and timing for the next tier of alert recipients.

• create_escalation_policywrite action

  Creates a new escalation policy that automatically escalates alerts to additional responders after a specified number of cycles without acknowledgment. The policy can be triggered by alerts from associated groups or services.

• delete_alert_eventwrite action

  Permanently deletes a specific alert event by its unique identifier. This action cannot be undone.

• delete_alert_groupwrite action

  Permanently delete a specific alert group by its unique identifier. This action cannot be undone.

• delete_alert_sourcewrite action

  Permanently delete a specific alert source by its unique identifier. This action cannot be undone.

• delete_alert_urgencywrite action

  Delete a specific alert urgency by its unique identifier. This operation permanently removes the alert urgency configuration from the system.

• delete_authorizationwrite action

  Permanently delete a specific authorization by its unique identifier. This action cannot be undone.

• delete_catalogwrite action

  Permanently delete a catalog and all its associated data. This action cannot be undone.

• delete_catalog_entitywrite action

  Permanently delete a specific Catalog Entity by its unique identifier. This action cannot be undone.

• delete_catalog_entity_propertywrite action

  Permanently delete a specific Catalog Entity Property by its unique identifier. This operation removes the property and all associated data.

• delete_catalog_fieldwrite action

  Permanently delete a catalog field by its unique identifier. This action cannot be undone.

• delete_causewrite action

  Permanently delete a cause by its unique identifier. This action cannot be undone.

• delete_custom_formwrite action

  Permanently delete a custom form by its unique identifier. This action cannot be undone.

• delete_dashboardwrite action

  Permanently delete a dashboard by its unique identifier. This action cannot be undone.

• delete_dashboard_panelwrite action

  Permanently delete a specific dashboard panel by its unique identifier. This action cannot be undone.

• delete_environmentwrite action

  Permanently delete a specific environment by its unique identifier. This action cannot be undone.

• delete_escalation_levelwrite action

  Permanently delete an escalation level by its unique identifier. This action cannot be undone.

• delete_escalation_pathwrite action

  Permanently delete a specific escalation path by its unique identifier. This action cannot be undone.

• delete_escalation_policywrite action

  Permanently delete an escalation policy by its unique identifier. This action cannot be undone and will remove the policy from the system.

• delete_form_field_optionwrite action

  Delete a specific form field option by its unique identifier. This operation permanently removes the option from the form field.

• duplicate_dashboardwrite action

  Creates a copy of an existing dashboard with all its configuration, layout, and widgets. The duplicated dashboard will be a complete independent instance.

• duplicate_dashboard_panelwrite action

  Creates a duplicate copy of an existing dashboard panel, preserving its configuration and settings. The duplicated panel is added to the same dashboard as the original.

• get_alert

  Retrieves a specific alert by its unique identifier. Use this operation to fetch detailed information about a single alert.

• get_alert_event

  Retrieves a specific alert event by its unique identifier. Use this to fetch detailed information about a single alert event.

• get_alert_group

  Retrieves a specific alert group by its unique identifier. Use this operation to fetch detailed information about a single alert group.

• get_alert_source

  Retrieves a specific alert source by its unique identifier. Use this to fetch detailed configuration and settings for a particular alert source.

• get_alert_urgency

  Retrieves a specific alert urgency configuration by its unique identifier. Use this to fetch details about how urgent a particular alert level is classified.

• get_authorization

  Retrieves a specific authorization by its unique identifier. Use this to fetch details about an existing authorization.

• get_catalog

  Retrieves a specific catalog by its unique identifier. Use this operation to fetch detailed information about a catalog.

• get_catalog_entity

  Retrieves a specific Catalog Entity by its unique identifier, with optional inclusion of related catalog and properties data.

• get_catalog_entity_property

  Retrieves a specific Catalog Entity Property by its unique identifier. Optionally include related Catalog Entity or Catalog Field data in the response.

• get_catalog_field

  Retrieves a specific Catalog Field by its unique identifier. Optionally include related catalog information in the response.

• get_cause

  Retrieves a specific cause by its unique identifier. Use this operation to fetch detailed information about a single cause.

• get_custom_form

  Retrieves a specific custom form by its unique identifier. Use this operation to fetch the complete details and configuration of a custom form.

• get_dashboard

  Retrieves a specific dashboard by its unique identifier. Optionally include related resources such as panels in the response.

• get_dashboard_panel

  Retrieves a specific dashboard panel by its unique identifier, with optional filtering by date range and time-based aggregation.

• get_environment

  Retrieves a specific environment by its unique identifier. Use this operation to fetch detailed information about a single environment.

• get_escalation_level

  Retrieves a specific escalation level by its unique identifier. Use this to fetch details about a particular escalation level configuration.

• get_escalation_path

  Retrieves a specific escalation path by its unique identifier. Optionally include related escalation policy levels in the response.

• get_escalation_policy

  Retrieves a specific escalation policy by its unique identifier. Optionally include related resources such as escalation levels, paths, groups, or services.

• get_form_field_option

  Retrieves a specific form field option by its unique identifier. Use this to fetch details about a single option available for a form field.

• list_alert_events

  Retrieve a paginated list of events associated with a specific alert, with optional filtering by event kind and action type.

• list_alert_groups

  Retrieve a list of all alert groups. Use the include parameter to expand related resources in the response.

• list_alert_sources

  Retrieve a paginated list of alert sources with optional filtering by status and source type, and customizable sorting.

• list_alert_urgencies

  Retrieve a paginated list of alert urgency levels. Use this to understand the available urgency classifications for alerts in your system.

• list_alerts

  Retrieve a paginated list of alerts with optional filtering by status and field inclusion. Use this to monitor and review all alerts in the system.

• list_audits

  Retrieve a paginated list of audit logs with optional filtering by user, API key, source, or item type, and configurable sorting.

• list_catalog_entities

  Retrieve a paginated list of entities within a specific catalog, with optional filtering to include related catalog and property information.

• list_catalog_entity_properties

  Retrieve a paginated list of properties for a specific catalog entity, with optional filtering, sorting, and related entity inclusion.

• list_catalog_fields

  Retrieve a paginated list of fields within a specific catalog. Optionally filter by field kind, include related catalog data, and sort results by creation date, update date, or field position.

• list_catalogs

  Retrieve a paginated list of catalogs with optional inclusion of related data and sorting capabilities.

• list_causes

  Retrieve a paginated list of all causes. Use pagination parameters to control the number of results and navigate through pages.

• list_custom_forms

  Retrieve a paginated list of custom forms with optional filtering and sorting capabilities.

• list_dashboard_panels

  Retrieve a paginated list of panels configured within a specific dashboard. Use this to display dashboard contents or manage panel organization.

• list_dashboards

  Retrieve a paginated list of dashboards. Optionally include related panel data for each dashboard.

• list_environments

  Retrieve a paginated list of environments with optional filtering and sorting capabilities.

• list_escalation_levels

  Retrieve all escalation levels configured for a specific escalation policy. Escalation levels define the sequence of on-call responders and timing for incident escalation.

• list_escalation_levels_for_escalation_path

  Retrieve all escalation levels defined within a specific escalation path. Escalation levels determine the sequence and conditions for notifying responders when an incident requires escalation.

• list_escalation_paths

  Retrieve all escalation paths defined within a specific escalation policy. Optionally include related escalation policy level details.

• list_escalation_policies

  Retrieve a paginated list of escalation policies. Optionally include related resources such as escalation levels, paths, groups, or services to enrich the response.

• list_form_field_options

  Retrieve a paginated list of options available for a specific form field. Use filtering and pagination parameters to narrow results and control response size.

• list_incident_alerts

  Retrieve a paginated list of alerts associated with a specific incident. Supports filtering by source, groups, labels, and time ranges to narrow results.

• resolve_alert

  Resolves a specific alert and optionally its associated incidents. Use this operation to mark an alert as resolved with an optional explanation of how it was addressed.

• set_dashboard_as_default

  Sets the specified dashboard as the default dashboard for the current user. The default dashboard is displayed when the user first accesses the dashboard interface.

• update_alertwrite action

  Update an existing alert with new metadata, classifications, or associations. Modify alert properties such as noise status, summary, description, urgency, and linked resources.

• update_alert_eventwrite action

  Update a specific alert event by adding or modifying a note. Requires the alert event ID, resource type identifier, and note content.

• update_alert_groupwrite action

  Update an existing alert group's configuration, including grouping rules, time window, description, and notification targets.

• update_alert_sourcewrite action
• update_alert_urgencywrite action

  Update the properties of a specific alert urgency level, including its description and display position.

• update_catalogwrite action

  Update an existing catalog's metadata including its description, visual icon, and display position. Modify any combination of catalog properties by providing the catalog ID and updated values.

• update_catalog_entitywrite action

  Update an existing Catalog Entity by its unique identifier. Modify the entity's description and display position within catalog lists.

• update_catalog_entity_propertywrite action

  Update a specific catalog entity property by its identifier. Modify the property's key type and associated value to reflect changes in how catalog entities are characterized.

• update_catalog_fieldwrite action

  Update a specific catalog field by its ID. Modify field properties such as slug, kind, associated catalog reference, and display position.

• update_causewrite action

  Update an existing cause by its ID, allowing modification of its description and position in the list.

• update_custom_formwrite action

  Update an existing custom form configuration by its ID. Modify form metadata, slug, description, enabled status, or associated Slack command trigger.

• update_dashboardwrite action

  Update an existing dashboard's configuration, including its metadata, visibility settings, display preferences, and data refresh behavior.

• update_dashboard_panelwrite action

  Update a dashboard panel's configuration, including its display type, data sources, layout position, and visibility settings.

• update_environmentwrite action

  Update an existing environment's configuration, including its description, visual appearance, notification settings, and associated Slack integrations.

• update_escalation_levelwrite action

  Update an existing escalation level within an escalation policy. Modify notification timing, position in the escalation sequence, and paging strategy to control how and when alerts are routed to notification targets.

• update_escalation_pathwrite action
• update_escalation_policywrite action

  Update an existing escalation policy to modify its escalation behavior, associated resources, and scheduling rules. Changes apply to future alert escalations using this policy.

• update_form_field_optionwrite action

  Update a specific form field option by its ID, allowing modification of its display value, color, default status, and position within the form field.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 48,255 servers

Tools

100

the typical server has 7

Tools that change things

56%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 92% of 28,688 servers

Downloads a week

157

more than 71% of 12,191 servers with a package

Rootly: common questions

Is Rootly MCP server safe?

Mostly: it is graded B (80/100). Read the Rootly safety report

How do I install Rootly?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Rootly need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Rootly maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.5.

What can I use instead of Rootly?

Servers from other publishers that do the same job: OneUptime MCP server.

How does Rootly compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,255 servers); tools 100 (the typical server has 7); tools that change things 56% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.