incident-io vs Rootly
incident-io is a plugin bundle for AI coding tools published by incident-io. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Rootly is an MCP server published by rootly.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  incident-io |  Rootly |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.20261009.666 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.2.4 Downloads/month (PyPI): 4 198 Downloads/week (PyPI): 823 Forks (GitHub): 23 Stars (GitHub): 45 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | incident-io | Rootly |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 45 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 23 (better) |
| Last release (differs) | 2026-10-14 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.rootly.com/sse) |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/incident-io/skills | github.com/rootly-ai-labs/rootly-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
incident-io
Official incident.io plugins for AI agents: skills for working with [incident.io](https://incident.io/) — incidents, on-call, and investigations — and for authoring the operational content our platform draws on.
Rootly
Incident management, on-call scheduling, and intelligent analysis powered by Rootly.
How to run each
incident-io
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Rootly As a remote MCP server
claude mcp add --transport sse rootly https://mcp.rootly.com/sse --header "Authorization: Bearer <YOUR_TOKEN>"Requires: ROOTLY_API_TOKEN (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Rootly has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of incident-io publish no settings it asks for, so we do not compare settings.
What it can do: incident-io · What it can do: Rootly · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.