list_environments
List Environments
List all environments configured in Rootly (e.g., production, staging, development). Use this to find environment IDs when creating incidents or alerts.
Ask your agent in plain language. Each of these maps to a real tool on the server.
list_environments
List all environments configured in Rootly (e.g., production, staging, development). Use this to find environment IDs when creating incidents or alerts.
create_incident
Create a new incident in Rootly. Optionally associate it with services, environments, severities, and teams. The incident title is auto-generated if not provided.
list_incidents
Search and list incidents in Rootly. Filter by status, severity, services, or teams. Supports pagination and sorting. Use this to find active incidents, review past incidents, or audit incident history.
list_on_call
List who is currently on call. Returns active on-call assignments across schedules and escalation policies. Use this to find who is responsible for responding to incidents right now. Pagination slices the current assignments locally; the API returns the full collection.
update_incident
Update an existing incident in Rootly. Change status, severity, title, summary, linked services, or add mitigation/resolution messages. Use this to transition incidents through their lifecycle (e.g., triage → mitigated → resolved).
create_action_item
Create a follow-up action item for an incident. Action items track tasks that need to be completed after an incident. Assign to a user, set priority, and optionally set a due date.
list_severities
List all severity levels configured in the Rootly organization. Use this to find severity IDs when creating or updating incidents.
list_teams
List teams in Rootly. Search by name, slug, or keyword. Use this to find team IDs for filtering incidents or assigning ownership.
get_incident
Retrieve detailed information about a specific incident by its ID or slug. Returns full incident details including status, severity, assigned services, timeline timestamps, and linked integrations.
list_alerts
Search and list alerts from monitoring and observability tools. Filter by status, source, services, or environments. Use this to review incoming alerts, find unacknowledged alerts, or audit alert history. Text search and sorting apply within the returned provider page because the API exposes neither option.
create_alert
Ingest a new alert into Rootly from an external source. Alerts can be routed to escalation policies, services, or specific users. Supports deduplication keys to prevent duplicate alerts and labels for categorization.
update_action_item
Update an existing action item. Change status, reassign, update priority or due date.
list_schedules
List on-call schedules. Search by name or keyword to find specific schedules. Returns schedule configuration details including rotation settings and coverage information.
list_heartbeats
List heartbeat monitors configured in Rootly. Heartbeats monitor system health by expecting periodic pings. Returns heartbeat status (waiting, active, expired), interval configuration, and alert settings.
list_users
List users in the Rootly organization. Search by name or email. Use this to find user IDs for assigning incidents, action items, or notification targets.
list_workflows
List automated workflows configured in Rootly. Workflows are triggered by incident or alert events and perform automated tasks. Search by name to find specific workflow automations.
create_heartbeat
Create a new heartbeat monitor. Heartbeats expect periodic pings and trigger alerts if a ping is missed. Configure the expected interval and notification target for when the heartbeat expires.
list_services
List services from the Rootly service catalog. Search by name, slug, or keyword. Use this to find service IDs for linking to incidents or alerts.
list_escalation_policies
List escalation policies configured in Rootly. Escalation policies define how alerts escalate when responders don't acknowledge. Optionally include escalation levels and paths for full policy details.
manage_alert
Acknowledge or resolve an alert. Open alerts cannot be acknowledged; inspect a triggered alert before acknowledgement. Resolving an alert does not resolve its related incidents.
list_action_items
List follow-up action items across all incidents or a selected incident. Status filtering and sorting are provider-wide for the organization collection, and apply within the returned page when an incident is selected. Text search applies to the returned provider page. Action items track post-incident follow-up tasks.
get_action_item
Read an incident action item by its identifier. Call list_action_items to discover identifiers.
manage_heartbeat
Read, update or delete a heartbeat monitor. Use enabled=false to disable missed-ping alerts. Deletion permanently removes the monitor. Call list_heartbeats to discover identifiers.
delete_action_item
Permanently delete an incident action item. Verify its identifier with get_action_item or list_action_items first.
get_current_user
Inspect the current user associated with the API connection, including its identifier and profile.
delete_incident
Permanently delete an incident and its incident record. Call list_incidents or get_incident to verify the target before deletion.
get_alert
Read the current state and details of an alert. Call list_alerts to discover alert identifiers.
Every client uses the same Magic MCP URL, and so does any other MCP client. Add it once and sign in with SSO.
{"mcpServers": {"metorial": {"url": "<your-magic-mcp-url>"}}}
claude mcp add --transport http metorial <your-magic-mcp-url>
codex mcp add metorial --url <your-magic-mcp-url>codex mcp login metorial
One governed layer for every app your agents reach, not a separate connector per tool.
Manage incidents and follow-up action items, ingest and inspect alerts, acknowledge or resolve alerts, and maintain heartbeat monitors. Read current on-call coverage, schedules, escalation policies, services, teams, users, workflows, severities and environments.
Common questions about connecting Rootly to AI agents with Metorial.