Integration

Rootly integration

Rootly is an incident management platform for engineering teams: it declares, runs and closes out incidents, and carries the on-call rota that pages people to them. Declare an incident and move it through triage, mitigation, resolution and cancellation, attach severities, incident types, causes, services, functionalities, environments and teams to it, log timeline events, assign responder roles, manage subscribers, and read or edit its retrospective. Read and act on alerts (acknowledge, snooze, escalate, resolve, attach to an incident) and manage the alert sources they arrive from. Run the service catalog: services, functionalities, environments and teams, each with bulk upsert and bulk delete, plus incident and uptime charts. Own the on-call schedule: schedules, rotations, override shifts, shifts and who is on call right now, with escalation policies, paths and levels. Drive automation workflows and their runs, publish status pages with components and announcements, ping heartbeats, and read the audit log. Every list route takes Rootly's own filter set plus JSON:API paging. Authentication is an organization API key sent as a bearer token.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Rootly.Built from the 165 Rootly tools below, on the connection you add once.

What you can do with Rootly

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Action item, 5 operations

  • create_incident_action_itemCreate incident action itemPOSTCreates an incident action item.
  • delete_incident_action_itemDelete incident action itemDELETEDelete an incident action item.
  • get_incident_action_itemGet incident action itemGETRetrieves an incident action item.
  • list_action_itemsList action itemsGETList all action items for an organization.
  • list_incident_action_itemsList incident action itemsGETList incident action items.

Alert, 5 operations

  • attach_alerts_to_incidentAttach alerts to incidentPOSTAttach alerts to an incident.
  • create_alertCreate alertPOSTCreates an alert.
  • get_alertGet alertGETRetrieves an alert.
  • list_alertsList alertsGETList alerts.
  • list_incident_alertsList incident alertsGETList Incident alerts.

Alert source, 4 operations

  • create_alert_sourceCreate alert sourcePOSTCreates an alert source.
  • delete_alert_sourceDelete alert sourceDELETEDelete an alert source.
  • get_alert_sourceGet alert sourceGETRetrieves an alert source.
  • list_alert_sourcesList alert sourcesGETList alert sources.

Bulk delete, 4 operations

  • bulk_delete_environmentsBulk delete environmentsPOSTBulk delete Environments.
  • bulk_delete_functionalitiesBulk delete functionalitiesPOSTBulk delete Functionalities.
  • bulk_delete_servicesBulk delete servicesPOSTBulk delete Services.
  • bulk_delete_teamsBulk delete teamsPOSTBulk delete Teams.

Bulk upsert, 4 operations

  • bulk_upsert_environmentsBulk upsert environmentsPOSTBulk upsert Environments.
  • bulk_upsert_functionalitiesBulk upsert functionalitiesPOSTBulk upsert Functionalities.
  • bulk_upsert_servicesBulk upsert servicesPOSTBulk upsert Services.
  • bulk_upsert_teamsBulk upsert teamsPOSTBulk upsert Teams.

Cause, 4 operations

  • create_causeCreate causePOSTCreates a cause.
  • delete_causeDelete causeDELETEDelete a cause.
  • get_causeGet causeGETRetrieves a cause.
  • list_causesList causesGETList causes.

Environment, 4 operations

  • create_environmentCreate environmentPOSTCreates an environment.
  • delete_environmentDelete environmentDELETEDelete an environment.
  • get_environmentGet environmentGETRetrieves an environment.
  • list_environmentsList environmentsGETList environments.

Escalation path, 4 operations

  • create_escalation_pathCreate escalation pathPOSTCreates an escalation path.
  • delete_escalation_pathDelete escalation pathDELETEDelete an escalation path.
  • get_escalation_pathGet escalation pathGETRetrieves an escalation path.
  • list_escalation_pathsList escalation pathsGETList escalation paths.

Escalation policie, 4 operations

  • create_escalation_policyCreate escalation policyPOSTCreates an escalation policy.
  • delete_escalation_policyDelete escalation policyDELETEDelete an escalation policy.
  • get_escalation_policyGet escalation policyGETRetrieves an escalation policy.
  • list_escalation_policiesList escalation policiesGETList escalation policies.

Event, 4 operations

  • create_incident_eventCreate incident eventPOSTCreates an incident event.
  • delete_incident_eventDelete incident eventDELETEDelete an incident event.
  • get_incident_eventGet incident eventGETRetrieves an incident event.
  • list_incident_eventsList incident eventsGETList incident events.

Functionalitie, 4 operations

  • create_functionalityCreate functionalityPOSTCreates a functionality.
  • delete_functionalityDelete functionalityDELETEDelete a functionality.
  • get_functionalityGet functionalityGETRetrieves a functionality.
  • list_functionalitiesList functionalitiesGETList functionalities.

Heartbeat, 4 operations

  • create_heartbeatCreate heartbeatPOSTCreates a heartbeat.
  • delete_heartbeatDelete heartbeatDELETEDelete a heartbeat.
  • get_heartbeatGet heartbeatGETRetrieves a heartbeat.
  • list_heartbeatsList heartbeatsGETList heartbeats.

Incident, 4 operations

  • create_incidentCreate incidentPOSTCreates an incident.
  • delete_incidentDelete incidentDELETEDelete an incident.
  • get_incidentGet incidentGETRetrieves an incident.
  • list_incidentsList incidentsGETList incidents.

Incident role, 4 operations

  • create_incident_roleCreate incident rolePOSTCreates an incident role.
  • delete_incident_roleDelete incident roleDELETEDelete an incident role.
  • get_incident_roleGet incident roleGETRetrieves an incident role.
  • list_incident_rolesList incident rolesGETList incident roles.

Incident type, 4 operations

  • create_incident_typeCreate incident typePOSTCreates an incident type.
  • delete_incident_typeDelete incident typeDELETEDelete an incident type.
  • get_incident_typeGet incident typeGETRetrieves an incident type.
  • list_incident_typesList incident typesGETList incident types.

Override shift, 4 operations

  • create_override_shiftCreate override shiftPOSTcreates an override shift.
  • delete_override_shiftDelete override shiftDELETEDelete an override shift.
  • get_override_shiftGet override shiftGETRetrieves an override shift.
  • list_override_shiftsList override shiftsGETList override shifts.

Schedule, 4 operations

  • create_scheduleCreate schedulePOSTCreates a schedule.
  • delete_scheduleDelete scheduleDELETEDelete a schedule.
  • get_scheduleGet scheduleGETRetrieves a schedule.
  • list_schedulesList schedulesGETList schedules.

Schedule rotation, 4 operations

  • create_schedule_rotationCreate schedule rotationPOSTCreates a schedule rotation.
  • delete_schedule_rotationDelete schedule rotationDELETEDelete a schedule rotation.
  • get_schedule_rotationGet schedule rotationGETRetrieves a schedule rotation.
  • list_schedule_rotationsList schedule rotationsGETList schedule rotations.

Service, 4 operations

  • create_serviceCreate servicePOSTCreates a service.
  • delete_serviceDelete serviceDELETEDelete a service.
  • get_serviceGet serviceGETRetrieves a service.
  • list_servicesList servicesGETList services.

Severitie, 4 operations

  • create_severityCreate severityPOSTCreates a severity.
  • delete_severityDelete severityDELETEDelete a severity.
  • get_severityGet severityGETRetrieves a severity.
  • list_severitiesList severitiesGETList severities.

Announcement, 3 operations

  • create_status_page_announcementCreate status page announcementPOSTCreates a status page announcement.
  • delete_status_page_announcementDelete status page announcementDELETEDelete a status page announcement.
  • get_status_page_announcementGet status page announcementGETRetrieves a status page announcement.

Component, 3 operations

  • create_status_page_componentCreate status page componentPOSTCreates a status page component.
  • delete_status_page_componentDelete status page componentDELETEDelete a status page component.
  • get_status_page_componentGet status page componentGETRetrieves a status page component.

Incidents chart, 3 operations

  • get_functionality_incidents_chartGet functionality incidents chartGETGet functionality incidents chart.
  • get_service_incidents_chartGet service incidents chartGETGet service incidents chart.
  • get_team_incidents_chartGet team incidents chartGETGet team incidents chart.

Status page, 3 operations

  • create_status_pageCreate status pagePOSTCreates a status page.
  • delete_status_pageDelete status pageDELETEDelete a status page.
  • get_status_pageGet status pageGETRetrieves a status page.

Team, 3 operations

  • create_teamCreate teamPOSTCreates a team.
  • delete_teamDelete teamDELETEDelete a team.
  • get_teamGet teamGETRetrieves a team.

Workflow, 3 operations

  • create_workflowCreate workflowPOSTCreates a workflow.
  • delete_workflowDelete workflowDELETEDelete a workflow.
  • get_workflowGet workflowGETRetrieves a workflow.

Escalation level, 2 operations

  • delete_escalation_levelDelete escalation levelDELETEDelete an escalation level.
  • get_escalation_levelGet escalation levelGETRetrieves an escalation level.

Post mortem, 2 operations

  • get_incident_retrospectiveGet incident retrospectiveGETRetrieves an incident retrospective.
  • list_incident_retrospectivesList incident retrospectivesGETList incident retrospectives.

Uptime chart, 2 operations

  • get_functionality_uptime_chartGet functionality uptime chartGETGet functionality uptime chart.
  • get_service_uptime_chartGet service uptime chartGETGet service uptime chart.

User, 2 operations

  • delete_userDelete userDELETEDelete an user.
  • get_userGet userGETRetrieves an user.

Acknowledge, 1 operation

  • acknowledge_alertAcknowledge alertPOSTAcknowledges an alert.

Add subscriber, 1 operation

  • add_subscribers_to_incidentAdd subscribers to incidentPOSTAdd subscribers to incident.

Assign role to user, 1 operation

  • assign_user_to_incidentAssign user to incidentPOSTAssign user to incident.

Audit, 1 operation

  • list_auditsList auditsGETList audits.

Cancel, 1 operation

  • cancel_incidentCancel incidentPUTCancel an incident.

Detach from parent, 1 operation

  • detach_from_parent_incidentDetach from parent incidentPUTDetach an incident from its parent.

Escalate, 1 operation

  • escalate_alertEscalate alertPOSTEscalates an alert.

Me, 1 operation

  • get_current_userGet current userGETGet current user.

Oncall, 1 operation

  • list_on_callsList on callsGETList on-calls.

Receipt, 1 operation

  • get_alert_receiptGet alert receiptGETGet a receipt.

Shift, 1 operation

  • list_schedule_shiftsList schedule shiftsGETRetrieves a schedule shifts.

Workflow run, 1 operation

  • create_workflow_runCreate workflow runPOSTCreates a workflow run.

Showing the first 120 of 165 endpoints. The rest are in the product, searchable from the workflow builder and from chat.

Use Rootly from Claude Code, Cursor or Codex

Connect Rootly in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Rootly operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Rootly

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Rootly once

    Add your Rootly connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Rootly integration FAQ

What can you do with the Rootly integration?

LiveContext exposes 165 operations on Rootly, covering action item, alert, alert source and bulk delete.

Popular integrations

Browse the whole catalog