Rootly

Manage Rootly incidents, alerts, on-call schedules and status pages from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Rootly connector does

The Rootly MCP server connects Claude to Rootly's incident management platform. Claude can search incidents, find similar past ones, check who is on call, and read shift metrics. It can also create incidents and alerts, change schedules and update status pages. Rootly excludes delete operations from the default tool surface and offers a read-only mode.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Rootly tools (255)

  • attach_alert
  • check_responder_availability
  • collect_incidents
  • create_alert
  • create_alert_event
  • create_alert_group
  • create_alert_route
  • create_alert_routing_rule
  • create_alert_urgency
  • create_alerts_source
  • create_catalog
  • create_catalog_entity
  • create_cause
  • create_custom_field
  • create_custom_form
  • create_dashboard
  • create_environment
  • create_escalation_level
  • create_escalation_level_paths
  • create_escalation_path
  • create_escalation_policy
  • create_form_field
  • create_form_field_option
  • create_form_set
  • create_functionality
  • create_heartbeat
  • create_incident
  • create_incident_action_item
  • create_incident_custom_field_selection
  • create_incident_event
  • create_incident_form_field_selection
  • create_incident_type
  • create_live_call_router
  • create_on_call_role
  • create_on_call_shadow
  • create_override_recommendation
  • create_override_shift
  • create_playbook
  • create_pulse
  • create_retrospective_process
  • create_schedule
  • create_schedule_rotation
  • create_schedule_rotation_active_day
  • create_schedule_rotation_user
  • create_service
  • create_severity
  • create_status_page
  • create_status_page_template
  • create_sub_status
  • create_team
  • create_user_email_address
  • create_user_notification_rule
  • create_user_phone_number
  • create_workflow
  • create_workflow_form_field_condition
  • create_workflow_group
  • create_workflow_run
  • create_workflow_task
  • find_related_incidents
  • get_alert
  • get_alert_by_short_id
  • get_alert_event
  • get_alert_group
  • get_alert_route
  • get_alert_routing_rule
  • get_alert_urgency
  • get_alerts_source
  • get_catalog
  • get_catalog_entity
  • get_cause
  • get_current_user
  • get_custom_field
  • get_custom_field_option
  • get_custom_form
  • get_dashboard
  • get_dashboard_panel
  • get_environment
  • get_escalation_level
  • get_escalation_path
  • get_escalation_policy
  • get_form_field
  • get_form_field_option
  • get_form_field_placement
  • get_form_field_placement_condition
  • get_form_set
  • get_form_set_condition
  • get_functionality
  • get_functionality_incidents_chart
  • get_functionality_uptime_chart
  • get_heartbeat
  • get_incident
  • get_incident_action_items
  • get_incident_custom_field_selection
  • get_incident_form_field_selection
  • get_incident_meeting_transcripts
  • get_incident_retrospective_step
  • get_incident_sub_status
  • get_incident_type
  • get_live_call_router
  • get_meeting_recording
  • get_on_call_role
  • get_on_call_shadow
  • get_oncall_handoff_summary
  • get_oncall_schedule_summary
  • get_oncall_shift_metrics
  • get_override_shift
  • get_playbook
  • get_playbook_task
  • get_pulse
  • get_retrospective_process
  • get_retrospective_process_group
  • get_retrospective_step
  • get_schedule
  • get_schedule_rotation
  • get_schedule_shifts
  • get_server_version
  • get_service
  • get_service_incidents_chart
  • get_service_uptime_chart
  • get_severity
  • get_shift_coverage_request
  • get_shift_incidents
  • get_status_page
  • get_status_page_template
  • get_sub_status
  • get_team
  • get_team_incidents_chart
  • get_user
  • get_user_email_addresses
  • get_user_phone_numbers
  • get_workflow
  • get_workflow_form_field_condition
  • get_workflow_group
  • get_workflow_task
  • list_alert_events
  • list_alert_groups
  • list_alert_routes
  • list_alert_routing_rules
  • list_alert_urgencies
  • list_alerts
  • list_alerts_sources
  • list_all_incident_action_items
  • list_all_meeting_recordings
  • list_audits
  • list_catalog_entities
  • list_catalogs
  • list_causes
  • list_custom_fields
  • list_custom_forms
  • list_dashboards
  • list_endpoints
  • list_environments
  • list_escalation_levels
  • list_escalation_levels_paths
  • list_escalation_paths
  • list_escalation_policies
  • list_form_field_options
  • list_form_fields
  • list_form_sets
  • list_functionalities
  • list_heartbeats
  • list_incident_action_items
  • list_incident_alerts
  • list_incident_custom_field_selections
  • list_incident_events
  • list_incident_form_field_selections
  • list_incident_roles
  • list_incident_types
  • list_incidents
  • list_live_call_routers
  • list_meeting_recordings
  • list_on_call_roles
  • list_on_call_shadows
  • list_override_shifts
  • list_playbooks
  • list_pulses
  • list_retrospective_processes
  • list_schedule_rotation_active_days
  • list_schedule_rotation_users
  • list_schedule_rotations
  • list_schedules
  • list_services
  • list_severities
  • list_shift_coverage_requests
  • list_shifts
  • list_status_page_templates
  • list_status_pages
  • list_sub_statuses
  • list_teams
  • list_user_notification_rules
  • list_users
  • list_workflow_form_field_conditions
  • list_workflow_groups
  • list_workflow_runs
  • list_workflow_tasks
  • list_workflows
  • patch_alert_route
  • search_incidents
  • suggest_solutions
  • update_alert
  • update_alert_event
  • update_alert_group
  • update_alert_route
  • update_alert_routing_rule
  • update_alert_urgency
  • update_alerts_source
  • update_catalog
  • update_catalog_entity
  • update_cause
  • update_custom_field
  • update_custom_field_option
  • update_custom_form
  • update_dashboard
  • update_dashboard_panel
  • update_environment
  • update_escalation_level
  • update_escalation_path
  • update_escalation_policy
  • update_form_field
  • update_form_field_option
  • update_form_field_placement
  • update_form_field_placement_condition
  • update_form_set
  • update_form_set_condition
  • update_functionality
  • update_heartbeat
  • update_incident
  • update_incident_action_item
  • update_incident_custom_field_selection
  • update_incident_form_field_selection
  • update_incident_retrospective_step
  • update_incident_sub_status
  • update_incident_type
  • update_live_call_router
  • update_on_call_role
  • update_on_call_shadow
  • update_override_shift
  • update_playbook
  • update_playbook_task
  • update_pulse
  • update_retrospective_process
  • update_retrospective_process_group
  • update_retrospective_step
  • update_schedule
  • update_schedule_rotation
  • update_service
  • update_severity
  • update_status_page
  • update_status_page_template
  • update_sub_status
  • update_team
  • update_workflow
  • update_workflow_form_field_condition
  • update_workflow_group
  • update_workflow_task

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The default surface writes. Without readonly=true, a connection can create incidents and alerts and change schedules and status pages.
  • Scopes do not narrow access. The advertised OAuth scopes are identity plus all; restriction comes from read-only mode, toolsets and the credential's role.
  • The full list is heavy. Rootly puts the full tool list at about 125k tokens of context, against about 10k for the core toolset.
  • Counts drift. The directory lists 255 tools; Rootly's docs say about 280, because tools are generated from the live API.
  • Per-tool side effects are not documented on the MCP page. Whether a given call pages someone depends on your Rootly alert routes and workflows.
  • We could not read tool schemas or annotations. The endpoint requires sign-in before tools/list.

Frequently asked questions

Why do the on-call handoff and shift metrics tools return incomplete data?

Because your credential probably sees only one team. Rootly says get_oncall_handoff_summary and get_oncall_shift_metrics need visibility across every team, and a Team API Key is scoped to a single team. Rootly recommends a Global API Key for full results from these organization-wide tools. With OAuth, the results follow the permissions of the Rootly user who signed in.

Can I connect the Rootly MCP server in read-only mode?

Yes. Add readonly=true to the hosted URL, or send the X-MCP-Readonly header, and Rootly hides write tools and refuses any request that would change data. Rootly adds that for a hard guarantee you should also use an API key whose role cannot write. Local and self-hosted installs use ROOTLY_MCP_ENABLE_WRITE_TOOLS set to false instead.

Why does the Rootly server connect but show no tools?

Most often the client needs a restart. Rootly says some MCP clients only load a new server after a full restart of the editor or assistant, and that invalid JSON in the configuration, such as a missing comma or bracket, silently stops the server loading. Check the configuration file, restart the client fully, and connect again.

Which Rootly MCP endpoint should I use?

Rootly recommends Code Mode at mcp.rootly.com/mcp-codemode, which exposes a few meta-tools instead of about 280 individual ones. The classic endpoint at mcp.rootly.com/mcp, which Anthropic's directory lists, loads every tool unless you add a toolsets parameter. The older SSE endpoint is deprecated and Rootly says it will be removed after 20 November 2026.

Sources

Use it in an agent

Put Rootly to work.

Connect Rootly once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.