Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Rootly (BYOK) — connector documentation

  • MCP endpoint: https://byok-rootly.connectorbay.com/mcp
  • REST API: POST https://byok-rootly.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-rootly.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Rootly Rootly API key (Organization Settings > API Keys), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-rootly.connectorbay.com/health · Tool schemas: https://byok-rootly.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-rootly · agent@connectorbay.com

What Rootly (BYOK) is for

Rootly (BYOK) lets an AI assistant read your own Rootly data through the Rootly API with a key you supply (Rootly API key (Organization Settings > API Keys)). Read-only: 12 tools (get_current_user, list_incidents, get_incident, list_alerts, list_services, list_teams, list_severities, list_environments, list_schedules, list_escalation_policies, list_action_items, list_users). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.rootly.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Rootly. Rootly and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Rootly user does my API key belong to?"
  • "What open incidents does Rootly have right now?"
  • "Show the details of Rootly incident 1a2b3c4d"
  • "Which Rootly alerts are triggered and not yet acknowledged?"
  • "What services are defined in Rootly?"
  • "What teams exist in Rootly?"

What it does

  • get_current_user: Show the Rootly user the API key acts as: name, email and time zone.
  • list_incidents: List incidents (newest first by default) with title, number, status, kind, severity, summary, link and key timestamps. Filter by status, severity, search text or creation time. Rootly allows only a few read calls per minute per key by default.
  • get_incident: Get one incident by id with title, status, severity, summary, mitigation and resolution messages, link and timestamps. Rootly allows only a few read calls per minute per key by default.
  • list_alerts: List alerts with summary, status (open, triggered, acknowledged, resolved, deferred), source, noise flag, link and times. Filter by status or source. Rootly allows only a few read calls per minute per key by default.
  • list_services: List services in the Rootly catalog with name, slug, description, owning teams and escalation policy id. Rootly allows only a few read calls per minute per key by default.
  • list_teams: List teams with name, slug, description, member ids and Slack channels. Rootly allows only a few read calls per minute per key by default.
  • list_severities: List the severity levels with name, slug, level (critical, high, medium or low), color and description. Rootly allows only a few read calls per minute per key by default.
  • list_environments: List environments (for example production and staging) with name, slug and color. Rootly allows only a few read calls per minute per key by default.
  • list_schedules: List on-call schedules with name, description, time zone, owning team ids and shift notification settings. Rootly allows only a few read calls per minute per key by default.
  • list_escalation_policies: List escalation policies with name, description, repeat count and attached team and service ids. Rootly allows only a few read calls per minute per key by default.
  • list_action_items: List incident action items (tasks and follow-ups) across the organization with summary, kind, priority, status and due date. Rootly allows only a few read calls per minute per key by default.
  • list_users: List Rootly users with name, email and time zone. Search by email or text. Rootly allows only a few read calls per minute per key by default.

BYOK key

You bring your own Rootly Rootly API key (Organization Settings > API Keys) (https://docs.rootly.com/api-reference/overview). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.rootly.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Rootly API (api.rootly.com) with a BYOK key; documentation: https://docs.rootly.com/api-reference/overview. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Rootly. Rootly and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Rootly account.

Built for: Worldwide. Languages: English.