# io.github.WYRE-AI/rootly-mcp

MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.2.6
- **Author:** io.github.WYRE-AI
- **License:** Unknown
- **Source:** https://github.com/WYRE-AI/rootly-mcp

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-25T07:43:38.158Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

23 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `rootly_alerts_list` — List Rootly alerts with optional status filter
- `rootly_alerts_acknowledge` — Acknowledge a Rootly alert
- `rootly_alerts_resolve` — Resolve a Rootly alert
- `rootly_alerts_create` — Create a new Rootly alert
- `rootly_alerts_update` — Update an existing Rootly alert
- `rootly_incidents_list` — List Rootly incidents with optional status/severity filters
- `rootly_incidents_get` — Get a single Rootly incident by ID
- `rootly_incidents_create` — Create a new Rootly incident
- `rootly_incidents_update` — Update an existing Rootly incident (title, summary, status, severity)
- `rootly_incidents_resolve` — Mark a Rootly incident as resolved
- `rootly_navigate` — Navigate to a Rootly domain to see its available tools.
- `rootly_status` — Check Rootly API connection status and available domains.
- `rootly_back` — Return to the Rootly domain navigation menu.
- `rootly_org_teams_list` — List all Rootly teams
- `rootly_org_teams_get` — Get a single Rootly team by ID
- `rootly_org_teams_create` — Create a new Rootly team
- `rootly_org_teams_update` — Update an existing Rootly team (uses PUT — full replacement of mutable fields)
- `rootly_org_teams_delete` — ⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a Rootly team and removes
- `rootly_org_teams_patch` — Safely update specific fields on a team without wiping others.
- `rootly_org_severities_list` — List Rootly incident severity levels
- `rootly_org_current_user` — Get the current authenticated Rootly user (verifies token)
- `rootly_schedules_list` — List Rootly on-call schedules
- `rootly_schedules_get` — Get a single Rootly on-call schedule by ID

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 43, ceiling 55 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Frootly-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Frootly-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.WYRE-AI%2Frootly-mcp
- HTML page: https://forgeregistry.com/registry/io.github.WYRE-AI%2Frootly-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.