# Rootly MCP Server > Rootly's MCP server for its incident management and on-call platform. Agents list, search and update incidents, alerts, schedules and escalation policies through a hosted endpoint at mcp.rootly.com with OAuth or an API key, or run the Apache-2.0 package themselves. - Canonical: https://www.anchorterminal.com/tools/rootly-mcp - Markdown: https://www.anchorterminal.com/tools/rootly-mcp.md (~8,050 tokens) - Slim: https://www.anchorterminal.com/tools/rootly-mcp.min.md (~1,780 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/rootly-mcp.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade C · 59.7/100 · rank #541 of 950 · #4 in Observability & incidents · not agent-ready · confidence medium** ## Assessment The server is open source under Apache-2.0, ships a dated release about every two weeks, and has a slim profile and a Code Mode endpoint that cut the 218-tool list. Hosted connections expose write tools by default, and the 2.3.21 changelog records telemetry changes that broke tool calls for clients with cached schemas in late September 2026. ## Facts | Field | Value | | --- | --- | | Vendor | Rootly Inc. (https://rootly.com) | | Kind | MCP server | | Category | Observability & incidents (https://www.anchorterminal.com/categories/observability) | | Transport | Streamable HTTP, SSE (legacy), stdio | | Endpoint | `https://mcp.rootly.com/mcp` | | Auth | OAuth or key · The hosted server takes an OAuth 2 login or a Rootly API key as a bearer token. OAuth clients can register themselves (RFC 7591), public clients must use PKCE with S256, access tokens last one hour and refresh tokens rotate. The MCP resource metadata advertises a single `all` scope. API keys are created by a person under Organisation Settings and are global with a chosen role, team-wide or personal. A local server reads `ROOTLY_API_TOKEN`. | | Pricing | Paid ($20 / seat-mo) · No separate charge for MCP. It is included in the Essentials plan at $20 per product per user a month, where incident response and on-call are separate products, and in Enterprise, which is by quote. No free tier. Self-serve sign-up starts a trial of about two weeks, and whether it needs a card wasn't established (https://rootly.com/pricing, checked 2026-10-09). | | x402 | No · No x402, MPP or L402 in the repository, the MCP docs or the pricing page (checked 2026-10-09). | | Licence | Apache-2.0 for the server. The hosted service runs under Rootly's Terms of Use | | Tools exposed | 218 | | Packages | pypi: `rootly-mcp-server` | | MCP registry name | `com.rootly/mcp-server` | | Source | https://github.com/rootlyhq/rootly-mcp-server | | Docs | https://docs.rootly.com/integrations/mcp-server | | llms.txt | https://rootly.com/llms.txt | | Last release | 2026-10-05 | | Endpoints | `https://mcp.rootly.com/mcp` (streamable HTTP), `https://mcp.rootly.com/sse` and `https://mcp.rootly.com/mcp-codemode`. An unauthenticated `initialize` answers 401 with an OAuth resource metadata header | | Tools | About 218 on the default endpoint and about 70 on the slim profile per the README at v2.3.21. Curated tools cover incidents, on-call, alerts and audits, and the rest are generated from Rootly's OpenAPI description | | Code Mode | Five meta-tools (`list_tools`, `tool_search`, `get_schema`, `tags`, `execute`). The model writes a short async Python block that chains tool calls on the server. The README calls it experimental and the docs recommend it | | Writes | Create and update tools are on by default. `ROOTLY_MCP_ENABLE_WRITE_TOOLS=false` or `--no-enable-write-tools` makes a server the owner runs read-only. Deletes are off by default | | Credentials | OAuth 2 with dynamic client registration, PKCE, one-hour tokens and rotating refresh tokens, or a bearer API key (global with a role, team, or personal) | | Rate limits | REST API limits of 3,000 reads and 3,000 writes a minute per API key and 50 alert creations a minute, with X-RateLimit headers. No limit specific to the MCP endpoint was found | | Annotations | `readOnlyHint`, `destructiveHint` and `openWorldHint` on every tool since 2.3.19, with `idempotentHint` on writes | | Telemetry | Hosted deployments send tool-call telemetry to AgentCat, with credential scrubbing and an optional Sentry export. PostHog analytics is opt-in and off wherever AgentCat is active | | Local server | Python 3.12 or later, run with `uvx --from rootly-mcp-server rootly-mcp-server` and `ROOTLY_API_TOKEN`. A Dockerfile is in the repository | | Releases | v2.3.21 on 5 October 2026. Six dated releases between 23 July and 5 October 2026, under semantic versioning | | Security programme | security.txt valid to 1 September 2027, a disclosure policy with safe harbour that names the MCP server in scope, no paid bounty, and SOC 2 Type II stated on the pricing page | | Subprocessors | About 30 listed with purpose, data and location, nearly all in the United States, with AWS as primary hosting. AgentCat isn't on the list | | Capabilities | observability.incidents, work.oncall | | Tags | official, hosted, open-source, mcp, oauth, api-key, incidents, on-call, python, code-mode, status-page, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/rootly-mcp.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 48 | 9.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 78 | 12.7 | | Agent ergonomics | 13% | 16.2 | 77 | 12.5 | | Security & auth | 14% | 17.5 | 65 | 11.4 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 81 | 7.1 | | Transparency & trust (editorial 65, provenance 95) | 7% | 8.8 | 80 | 7.0 | | Negative events | up to −15 | up to −15 | Between 23 and 29 September 2026 two changes to hosted telemetry broke tool calls. Removing an injected `context` parameter failed fifteen curated tools for clients with cached tool lists, and a PostHog analytics layer failed every hosted tool call until it was switched off. Both are fixed and described in the 2.3.21 changelog, so 3 points (https://github.com/rootlyhq/rootly-mcp-server/blob/main/CHANGELOG.md) | -3 | | **Total** | | | | **59.7 → C** | ### Why each score - Reliability 48: Scored as a hosted MCP server, the path the docs recommend. status.rootly.com is linked from the site and llms.txt, but it answered our reader with a bot check, so its components (15) and incident history (5) were unread. The REST API behind the tools allows 3,000 read calls and 3,000 write calls a minute per API key, and 50 alert creations a minute. No separate limit for mcp.rootly.com was found (12). A 429 returns a JSON error with `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Used` and `X-RateLimit-Reset` headers. No `Retry-After`, backoff guidance or idempotency keys were found (8). The pricing table lists "99.99 % Reliability" for on-call, and no SLA document was found (0). The hosted `/mcp` and `/sse` endpoints carry no beta label. The README calls Code Mode experimental while the docs recommend it (8). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 78: Read from the source at v2.3.21. Curated tools declare typed pydantic inputs and the rest are generated from Rootly's OpenAPI 3.0.1 description, 565 operations in the bundled copy, which the API docs also link for download (25). rootly.com/llms.txt and Markdown twins of the docs pages (10). Curated tools such as `list_incidents` say when to use them and when to prefer `search_incidents`. Generated tools carry the API's short summaries, for example "List alerts" (11). Sort orders use enums and generated tools keep the API's `include` enums, but severity, status and ID lists are free strings, with IDs passed comma-separated (9). The README and docs give worked calls for five tools and a troubleshooting section. The error types the server returns aren't documented (8). Semantic versioning with a dated Keep a Changelog file. The docs page still names two tools in camelCase and links the old Rootly-AI-Labs repository (15). - Agent ergonomics 77: The default endpoint lists about 218 tools per the README, which the checklist scores at 5. A slim profile (77 names in the source, about 70 per the README), a Code Mode endpoint with five meta-tools and an exact allowlist for servers the owner runs add back 10 (15). List tools page with bounded sizes, strip alert and incident lists to summary fields and clamp out-of-range counts, reporting each change under `argument_adjustments` (18). Tool errors return `error_type` and a message, with hints for plan-gated 404s, the pagination cap and replaced alert routing tools (16). Every tool sets `readOnlyHint`, `destructiveHint` and `openWorldHint` since 2.3.19, and writes set `idempotentHint`. `create_incident` has no idempotency key (15). Curated tools have no required parameters beyond record references and accept common aliases such as `limit`. Rootly lists REST SDKs for Go, Python and other languages (13). - Security & auth 65: OAuth 2 with dynamic client registration, PKCE with S256, one-hour access tokens, rotating refresh tokens, a revocation endpoint and `:read` and `:write` scopes per resource. The MCP server's resource metadata advertises a single `all` scope since 2.3.13, so MCP logins aren't narrowed by scope. API keys are global with a chosen role, team or personal, sent in the `Authorization` header (26). Delete operations are off by default and API key, user, role and webhook endpoints are excluded. Write tools are on by default for hosted connections, the documented read-only switch applies to servers the owner runs, and no confirmation step was found (11). Incident text, alert payloads and meeting transcripts are untrusted content, and no injection guidance was found (3). `list_audits` reads Rootly's audit log, which the pricing page lists under Enterprise (9). security.txt valid to 1 September 2027, a disclosure policy with safe harbour and response times, no paid bounty, SOC 2 Type II stated with the report on request, and dependency advisories recorded in the changelog (16). - Payments & pricing 20: No x402, MPP or L402 (0). Plan prices are public. Essentials is $20 per product per user a month, with MCP and API access included, and Enterprise is by quote. No per-call price (10). No free tier. Self-serve sign-up starts a trial of about two weeks per the pricing page. The sign-up page answered with a bot check, so whether a card is needed wasn't established, and the line takes half marks (10). A person signs up in a browser and either logs in through OAuth or creates an API key (0). The package is free to run but needs a Rootly account, so the self-hosted rule doesn't apply. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 81: v2.3.21 was tagged on 5 October 2026, four days before this check (30). Six dated releases between 23 July and 5 October 2026 (20). The commit log shows pull requests merged through 6 October and a fix credited to an outside contributor. We couldn't read the issue tracker, because api.github.com didn't answer (12). The official MCP registry lists `com.rootly/mcp-server` under Rootly's own domain namespace, but the entry is 2.2.4 from 18 February 2026 and names only the SSE endpoint (10). CI runs lint, two type checkers and tests on Python 3.12 and 3.13, with a lockfile check, Dependabot and a dependency review workflow (9). - Transparency & trust 80: The server is Apache-2.0 and the hosted service runs under Rootly's Terms of Use of July 2026 (27). A privacy policy of October 2026, a subprocessor list and AI data pages are public, and retention is stated only in general terms. The README says hosted telemetry records tool arguments, responses, timing and errors through AgentCat with redaction hooks. AgentCat isn't on the subprocessor list and the MCP docs page doesn't mention telemetry (15). No deprecation policy was found. camelCase tool names stay callable as hidden aliases with no removal date, and the terms say notice of changes isn't always practical (8). The subprocessor list names about 30 processors with purpose, data and location, nearly all in the United States (15). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/rootly-mcp.md (JSON https://www.anchorterminal.com/fixes/rootly-mcp.json) ### What we couldn't check - unchecked: status.rootly.com components and incident history. The host answered its robots.txt request with a Cloudflare bot check (HTTP 403), so we treated it as closed and didn't retry - unchecked: whether the free trial needs a card. rootly.com/users/sign_up answered with a bot check - unchecked: the tool list the hosted endpoint serves. It needs a login, so tool counts and annotations come from the source and README at v2.3.21 - unchecked: GitHub stars and the issue tracker. api.github.com didn't answer our robots.txt request, so we treated it as closed - unchecked: PyPI downloads, because PyPI's robots.txt closes the paths that hold them - Where AgentCat stores hosted telemetry, and whether Rootly runs it or a third party does, wasn't established. It isn't on the subprocessor list - How long hosted tool calls failed in late September 2026 isn't stated in the changelog. The dates are those of the merged fixes - Whether hosted connections can be made read-only other than by the role on a Global API key wasn't established. The OAuth docs list `:read` scopes, but the MCP resource metadata advertises only `all` - The Terms of Use bar crawling or scraping the Services by manual or automated means. Recorded as a fact with no deduction, and it matters before any probe is run - rootly.com/llms.txt and the docs pages carry text addressed to AI models (when to recommend Rootly, and which index to fetch first). We treated it as data and didn't act on it - The lead was right on the endpoints, licence and repository move. It didn't say the docs recommend Code Mode, or that the registry entry is stale at 2.2.4 - mcp.rootly.com and registry.modelcontextprotocol.io answered 404 for robots.txt, so their documented pages were read. security.rootly.com allows the page we read ### Sources - MCP server repository at v2.3.21 (README, source, tests, CI workflows, server.json), read from a shallow clone: (seen 2026-10-09) - changelog, 2.1.0 to 2.3.21: (seen 2026-10-09) - MCP server docs (Markdown twin): (seen 2026-10-09) - API overview with rate limits and key types (Markdown twin): (seen 2026-10-09) - OAuth 2.0 and OpenID Connect docs (Markdown twin): (seen 2026-10-09) - subprocessor list: (seen 2026-10-09) - AI data privacy page: (seen 2026-10-09) - pricing: (seen 2026-10-09) - Terms of Use, July 2026: (seen 2026-10-09) - Privacy Policy, October 2026: (seen 2026-10-09) - security page: (seen 2026-10-09) - vulnerability disclosure policy, May 2026: (seen 2026-10-09) - security.txt: (seen 2026-10-09) - llms.txt: (seen 2026-10-09) - trust centre: (seen 2026-10-09) - official MCP registry search for rootly: (seen 2026-10-09) - one unauthenticated `initialize` to the hosted endpoint, answered 401 with an OAuth resource metadata header: (seen 2026-10-09) - RDAP record for rootly.com: (seen 2026-10-09) - status page (bot check, unread): (seen 2026-10-09) ## Who's behind it (provenance 95/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Rootly Inc. | 20/20 | | Domain age | rootly.com, registered 2006-05-27 (20 years) | 15/15 | | Endpoint on the vendor's domain | mcp.rootly.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points | 5.1/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.rootly.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The Terms of Use (last updated July 2026) are a contract with ROOTLY INC., 1390 Market Street, San Francisco, and cover its websites, products, services and applications. The privacy policy (October 2026) writes the name as Rootly, Inc. The hosted MCP endpoint is mcp.rootly.com and the REST API is api.rootly.com, both on the vendor's domain. rootly.com/.well-known/security.txt names security@rootly.com and expires on 1 September 2027. status.rootly.com is linked from the site and llms.txt. It answered our reader with a bot check and was unread. RDAP for rootly.com gives a registration date of 2006-05-27. The subprocessor page refers to a U.S. Data Processing Addendum of September 2026, which we didn't find published. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://rootly.com/legal/terms), read 2026-10-09, dated 2026-07-01, states 6 of the 7 things a reader expects. - To know. Restricts automated access (costs points). ""crawls," "scrapes," or "spiders" any page, data, or portion of or relating to the Services or Content (through use of manual or automated means);" - To know. Says the terms or the service can change without notice (costs points). "We'll try to give you notice when we make a material change to the Services that would adversely affect you, but this isn't always practical." - To know. Says access can be ended without notice or for any reason. "Rootly is also free to terminate (or suspend access to) your use of the Services or your account for any reason in our discretion, including your breach of these Terms." - To know. Requires arbitration or waives class actions. "These Terms include information about future changes to these Terms, automatic renewals, limitations of liability, a class action waiver and resolution of disputes by arbitration instead of in court." - Gives the date it was last updated. Last updated 2026-07-01. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Capped at the greater of $100 and the fees paid in the 12 months before the claim. - Says how changes to the terms are announced. Says it gives notice of a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). The terms forbid processes that run or are activated while the user is not logged into the Services. "runs Maillist, Listserv, any form of auto-responder or "spam" on the Services, or any processes that run or are activated while you are not logged into the Services, or that otherwise interfere with the proper working of the Services" - Also in the text (2026-10-08). Paid services renew automatically for the same term at the then-current non-promotional rate unless the customer opts out through the order form. "Unless you opt out of auto-renewal, which can be done through your order form, any Paid Services you have signed up for will be automatically extended for successive renewal periods of the same duration as the subscription term originally selected, at the then-current non-promotional rate." - Also in the text (2026-10-08). A customer may opt out of the arbitration agreement by written notice postmarked within 30 days of first accepting the terms. "You have the right to opt out of the provisions of this Section by sending written notice of your decision to opt out to the following address: 1390 Market Street. #2126 San Francisco, CA 94102 USA postmarked within thirty (30) days of first accepting these Terms." **Privacy policy** (https://rootly.com/legal/privacy), read 2026-10-09, dated 2026-10-01, states 8 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-10-01. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacy@rootly.com. - Says where data is transferred or stored. Relies on the Data Privacy Framework. - Also in the text (2026-10-08). Data sent to AI providers is used only for Rootly AI services and is neither stored nor used for training by those providers. "Purpose of Sharing Data with AI Models: Data sent to AI providers is solely used for providing Rootly AI services and is neither stored nor used for training purposes by the AI providers." - Also in the text (2026-10-08). Rootly AI does not use a customer's data, even anonymously, to improve results for other customers. "Responsible Use: Rootly AI never uses your data (even if anonymously) to improve results for other customers." ## Live (updated 2026-10-10 02:55 UTC) - Right now: up, HTTP 401, 124 ms, checked 2026-10-10 02:55 UTC (mcp-initialize on `https://mcp.rootly.com/mcp`, asks for auth) - Uptime 24h 100.0% (115 probes) · 30 days 100.0% (115 probes) · p50 147 ms · p95 639 ms - Vendor status page: unknown, no machine-readable status found - pypi `rootly-mcp-server` 2.3.21, released 2026-10-05 - Watching changelog - Watching pricing - Watching privacy - Watching terms - Tools: the endpoint asks for credentials before listing them (checked 2026-10-09 21:40 UTC) - Always current: https://www.anchorterminal.com/api/v1/live/rootly-mcp.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Essentials plan, incident response | $20 | per seat per month | MCP, API and status pages included | | Essentials plan, on-call | $20 | per seat per month | added to incident response, $40 for both | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Apache-2.0 source for the same server Rootly hosts, with six dated releases between 23 July and 5 October 2026 - A slim profile of about 70 tools and a Code Mode endpoint with five meta-tools reduce the full list of about 218 - Every tool sets `readOnlyHint`, `destructiveHint` and `openWorldHint` since 2.3.19 of 9 September 2026 - OAuth with dynamic client registration, PKCE, one-hour access tokens, rotating refresh tokens and a revocation endpoint - Delete operations are off by default, and API key, user, role and webhook endpoints are excluded from the tool list ## Weaknesses - Hosted connections expose write tools by default, and the docs describe the read-only switch only for servers the owner runs - The 2.3.21 changelog records two hosted regressions in late September 2026, one failing fifteen tools for clients with cached schemas and one failing every tool call - Hosted telemetry records tool arguments and responses through AgentCat per the README. AgentCat isn't named on Rootly's subprocessor list - status.rootly.com answered our reader with a bot check, so its components and incident history were unread - The official registry entry `com.rootly/mcp-server` is still 2.2.4 from 18 February 2026 and lists only the SSE endpoint - Rootly's Terms of Use bar crawling or scraping the Services by manual or automated means. This matters before any probe is run ## Before you call it (notes for agents) 1. Connect to `https://mcp.rootly.com/mcp-codemode` or add `?tool_profile=slim` to `/mcp`. The default endpoint loads about 218 tool definitions 2. Connect Code Mode in place of the classic endpoint, not beside it. The docs say models skip `execute` when both are present 3. Use a Global API key for `get_oncall_handoff_summary` and `get_oncall_shift_metrics`. Team and personal keys return partial results 4. Refetch the tool list after a server release. Curated tools reject undeclared arguments, which failed calls from cached schemas in September 2026 5. Treat a 404 from a generated tool as a possible plan limit or missing parent record, and read the hint in the response ## Connect Install: ```bash uvx --from rootly-mcp-server rootly-mcp-server ``` Claude Code: ```bash claude mcp add --transport http rootly https://mcp.rootly.com/mcp ``` MCP client configuration: ```json { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/rootly-mcp. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Grafana MCP Server | BB | 74.5 | 70 | observability.incidents, work.oncall | no | https://www.anchorterminal.com/tools/grafana-mcp-server.md | | incident.io API | B | 68.9 | 204 | observability.incidents, work.oncall | no | https://www.anchorterminal.com/tools/incident-io.md | | PagerDuty MCP Server | D | 48.4 | 815 | observability.incidents, work.oncall | no | https://www.anchorterminal.com/tools/pagerduty-mcp.md | | Datadog MCP Server | C | 56.6 | 628 | observability.incidents | no | https://www.anchorterminal.com/tools/datadog-mcp.md | | Sentry MCP | BB | 70.2 | 160 | same category (Observability & incidents) | no | https://www.anchorterminal.com/tools/sentry-mcp.md | | Honeycomb MCP | C | 58.3 | 584 | same category (Observability & incidents) | no | https://www.anchorterminal.com/tools/honeycomb-mcp.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Hosted endpoints are `https://mcp.rootly.com/mcp` (streamable HTTP), `/sse` and `/mcp-codemode`, and the docs recommend Code Mode, which exposes `list_tools`, `tool_search`, `get_schema`, `tags` and `execute` in place of about 200 tool schemas (source: ) - The README puts the default tool list at about 218 and the slim profile at about 70, selected with `?tool_profile=slim` or the `X-Rootly-Tool-Profile` header (source: ) - Write tools are on by default for hosted and local servers, delete operations are off, and API key, user, role and webhook endpoints are excluded (source: ) - The 2.3.21 changelog of 5 October 2026 records that telemetry changes failed fifteen tools for clients with cached schemas and, separately, every hosted tool call, both since fixed (source: ) - The README says hosted telemetry records tool arguments, responses, timing, errors and identity through AgentCat, with redaction hooks and an optional Sentry export (source: ) - The official MCP registry entry `com.rootly/mcp-server` is 2.2.4 from 18 February 2026 and lists only the SSE endpoint (source: ) - The repository moved from Rootly-AI-Labs to rootlyhq, and the docs page still links the old address (source: ) - #4 of 7 in Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md - All 15 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md ## Compare - [Datadog MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp.md): C 56.6 vs C 59.7 - [Grafana MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp.md): BB 74.5 vs C 59.7 - [incident.io API vs Rootly MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp.md): B 68.9 vs C 59.7 - [PagerDuty MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/pagerduty-mcp-vs-rootly-mcp.md): D 48.4 vs C 59.7 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on rootly.com or one of its subdomains, or the README of github.com/rootlyhq/rootly-mcp-server. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "rootly-mcp", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Rootly MCP Server on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Rootly MCP Server on Anchor Terminal](https://www.anchorterminal.com/badges/rootly-mcp.svg)](https://www.anchorterminal.com/tools/rootly-mcp) ``` Plain link: ```html Rootly MCP Server on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Rootly MCP Server is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/rootly-mcp-dark.png - Light: https://www.anchorterminal.com/assets/share/rootly-mcp-light.png