Skip to main content
Glama
rootlyhq

Rootly MCP server

Official
by rootlyhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROOTLY_API_TOKENNoYour Rootly API token
ROOTLY_AUTH_HEADERNoBearer token for authentication (format: Bearer <YOUR_ROOTLY_API_TOKEN>)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
listIncidentAlertsD

List incident alerts

Path Parameters:

  • incident_id (Required): No description.

Query Parameters:

  • include: No description.

  • filter_source: No description.

  • filter_services: No description.

  • filter_environments: No description.

  • filter_groups: No description.

  • filter_labels: No description.

  • filter_started_at_gt: No description.

  • filter_started_at_gte: No description.

  • filter_started_at_lt: No description.

  • filter_started_at_lte: No description.

  • filter_ended_at_gt: No description.

  • filter_ended_at_gte: No description.

  • filter_ended_at_lt: No description.

  • filter_ended_at_lte: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • page_number: No description.

  • page_size: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
attachAlertC

Attach alerts to an incident from provided data

Path Parameters:

  • incident_id (Required): No description.

Responses:

  • 200 (Success): alert created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listAlertsD

List alerts

Query Parameters:

  • include: No description.

  • page_number: No description.

  • page_size: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createAlertC

Creates a new alert from provided data

Responses:

  • 201 (Success): alert created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: resource not found

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 422: invalid request

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listEnvironmentsD

List environments

Query Parameters:

  • include: No description.

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_slug: No description.

  • filter_name: No description.

  • filter_color: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • sort: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createEnvironmentC

Creates a new environment from provided data

Responses:

  • 201 (Success): environment created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 422: invalid request

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listFunctionalitiesD

List functionalities

Query Parameters:

  • include: No description.

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_name: No description.

  • filter_backstage_id: No description.

  • filter_cortex_id: No description.

  • filter_opslevel_id: No description.

  • filter_external_id: No description.

  • filter_slug: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • sort: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createFunctionalityC

Creates a new functionality from provided data

Responses:

  • 201 (Success): functionality created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 422: invalid request

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listWorkflowsC

List workflows

Query Parameters:

  • include: comma separated if needed. eg: form_field_conditions,genius_tasks

  • sort: comma separated if needed. eg: created_at,updated_at

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_name: No description.

  • filter_slug: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createWorkflowB

Creates a new workflow from provided data

Responses:

  • 201 (Success): admins can set 'locked' while creating a workflow

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 403: non-admins can't set 'locked' while creating a workflow

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listIncidentActionItemsC

List incident action items

Path Parameters:

  • incident_id (Required): No description.

Query Parameters:

  • include: No description.

  • page_number: No description.

  • page_size: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createIncidentActionItemC

Creates a new action item from provided data

Path Parameters:

  • incident_id (Required): No description.

Responses:

  • 201 (Success): incident_action_item created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 422: invalid request

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listIncident_TypesC

List incident types

Query Parameters:

  • include: No description.

  • page_number: No description.

  • page_size: No description.

  • filter_slug: No description.

  • filter_name: No description.

  • filter_color: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • sort: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createIncidentTypeC

Creates a new incident_type from provided data

Responses:

  • 201 (Success): incident_type created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: resource not found

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 422: invalid request

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listIncidentsC

List incidents

Query Parameters:

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_kind: No description.

  • filter_status: No description.

  • filter_private: No description.

  • filter_user_id: No description.

  • filter_severity: No description.

  • filter_severity_id: No description.

  • filter_labels: No description.

  • filter_types: No description.

  • filter_type_ids: No description.

  • filter_environments: No description.

  • filter_environment_ids: No description.

  • filter_functionalities: No description.

  • filter_functionality_ids: No description.

  • filter_services: No description.

  • filter_service_ids: No description.

  • filter_teams: No description.

  • filter_team_ids: No description.

  • filter_cause: No description.

  • filter_cause_ids: No description.

  • filter_custom_field_selected_option_ids: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • filter_updated_at_gt: No description.

  • filter_updated_at_gte: No description.

  • filter_updated_at_lt: No description.

  • filter_updated_at_lte: No description.

  • filter_started_at_gt: No description.

  • filter_started_at_gte: No description.

  • filter_started_at_lt: No description.

  • filter_started_at_lte: No description.

  • filter_detected_at_gt: No description.

  • filter_detected_at_gte: No description.

  • filter_detected_at_lt: No description.

  • filter_detected_at_lte: No description.

  • filter_acknowledged_at_gt: No description.

  • filter_acknowledged_at_gte: No description.

  • filter_acknowledged_at_lt: No description.

  • filter_acknowledged_at_lte: No description.

  • filter_mitigated_at_gt: No description.

  • filter_mitigated_at_gte: No description.

  • filter_mitigated_at_lt: No description.

  • filter_mitigated_at_lte: No description.

  • filter_resolved_at_gt: No description.

  • filter_resolved_at_gte: No description.

  • filter_resolved_at_lt: No description.

  • filter_resolved_at_lte: No description.

  • filter_closed_at_gt: No description.

  • filter_closed_at_gte: No description.

  • filter_closed_at_lt: No description.

  • filter_closed_at_lte: No description.

  • filter_in_triage_at_gt: No description.

  • filter_in_triage_at_gte: No description.

  • filter_in_triage_at_lt: No description.

  • filter_in_triage_at_lte: No description.

  • sort: comma separated if needed. eg: created_at,updated_at

  • include: comma separated if needed. eg: sub_statuses,causes,subscribers

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createIncidentC

Creates a new incident from provided data

Responses:

  • 201 (Success): incident created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 422: invalid causes association

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listServicesD

List services

Query Parameters:

  • include: No description.

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_name: No description.

  • filter_slug: No description.

  • filter_backstage_id: No description.

  • filter_cortex_id: No description.

  • filter_opslevel_id: No description.

  • filter_external_id: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • sort: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createServiceC

Creates a new service from provided data

Responses:

  • 201 (Success): service created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 422: invalid request

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listSeveritiesD

List severities

Query Parameters:

  • include: No description.

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_slug: No description.

  • filter_name: No description.

  • filter_severity: No description.

  • filter_color: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • sort: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createSeverityC

Creates a new severity from provided data

Responses:

  • 201 (Success): severity created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 422: invalid request

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listTeamsD

List teams

Query Parameters:

  • include: No description.

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_slug: No description.

  • filter_name: No description.

  • filter_backstage_id: No description.

  • filter_cortex_id: No description.

  • filter_opslevel_id: No description.

  • filter_external_id: No description.

  • filter_color: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • sort: No description.

Responses:

  • 200 (Success): success

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
createTeamC

Creates a new team from provided data

Responses:

  • 201 (Success): team created

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 422: invalid association

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
listUsersC

List users

Query Parameters:

  • page_number: No description.

  • page_size: No description.

  • filter_search: No description.

  • filter_email: No description.

  • filter_created_at_gt: No description.

  • filter_created_at_gte: No description.

  • filter_created_at_lt: No description.

  • filter_created_at_lte: No description.

  • sort: comma separated if needed. eg: created_at,updated_at

  • include: comma separated if needed. eg: email_addresses,phone_numbers

Responses:

  • 200 (Success): user found

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
getCurrentUserB

Get current user

Responses:

  • 200 (Success): user found

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}

  • 401: responds with unauthorized for invalid token

    • Content-Type: application/vnd.api+json

    • Example:

{
  "key": "value"
}
list_endpointsA

List all available Rootly API endpoints with their descriptions.

search_incidents_paginatedC

Search incidents with enhanced pagination control.

This tool provides better pagination handling than the standard API endpoint.

get_all_incidents_matchingB

Get all incidents matching a query by automatically fetching multiple pages.

This tool automatically handles pagination to fetch multiple pages of results.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.3/5.0

Scored across 27 tools

Disambiguation4/5

Most tools are clearly distinct by resource and action, such as createIncident vs listIncidents, with minimal overlap. However, get_all_incidents_matching and search_incidents_paginated both search incidents, potentially causing confusion, and attachAlert vs createAlert have subtle differences that might not be immediately clear from names alone.

Naming Consistency3/5

The majority of tools follow a consistent verb_noun pattern (e.g., createIncident, listServices), but there are notable deviations like get_all_incidents_matching (snake_case with underscores), list_endpoints (snake_case), and search_incidents_paginated (mixed style). This inconsistency reduces predictability, though the core pattern is still readable.

Tool Count2/5

With 27 tools, the count feels heavy for an incident management domain, especially given some redundancy (e.g., multiple incident search tools). While the domain is broad, the tool set could be more streamlined, as many tools are simple CRUD operations that might be better consolidated or scoped down to avoid overwhelming agents.

Completeness4/5

The tool set covers a wide range of incident management resources (incidents, alerts, services, teams, etc.) with create and list operations for most, providing good lifecycle coverage. However, there are gaps in update and delete operations for many resources, which could limit agent workflows, though the core create and list functions are well-represented.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources