# New Relic MCP Server vs Rootly MCP Server > New Relic scores 61 (C) to Rootly's 53.8 (D) for incidents. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp - Markdown: https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp.md (~5,050 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-04 New Relic MCP Server scores 61 (C) on agent readiness against Rootly MCP Server's 53.8 (D), and leads in 3 of 7 scored categories. Rootly MCP Server leads on schema & documentation and agent ergonomics. Both do incidents. - New Relic MCP Server: grade C, 61/100, rank #568 of 1349. Markdown https://www.anchorterminal.com/tools/new-relic.md · JSON https://www.anchorterminal.com/api/v1/tools/new-relic.json - Rootly MCP Server: grade D, 53.8/100, rank #832 of 1349. Markdown https://www.anchorterminal.com/tools/rootly-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/rootly-mcp.json - Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md - All 49 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md ## Which one, for what ### New Relic MCP Server (C) Good for: Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough. Ahead on: - Reliability, 60 against 48 - Security & auth, 76 against 65 - Payments & pricing, 30 against 20 Also in its favour: - Free to start without a card - No incidents deducted, where Rootly MCP Server loses 9 points for them Watch for: Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters ### Rootly MCP Server (D) Good for: Incident and on-call agents in teams that already run Rootly. Ahead on: - Schema & documentation, 78 against 51 - Agent ergonomics, 77 against 59 Also in its favour: - Runs on your own machine - Open source Watch for: Hosted connections expose write tools by default, and the docs describe the read-only switch only for servers the owner runs ## Why the edge ### Schema & documentation: Rootly MCP Server +27 - New Relic MCP Server (51): Tool input schemas are only visible through an authenticated session; the tool reference names 40 tools with one-line descriptions, so partial credit for a contract that exists but isn't public (10). docs.newrelic.com publishes llms.txt, updated 3 November 2026, and a Markdown twin of every page (10). Each tool's line says what it does, tags say which group it belongs to, and the reference says which tools need OAuth and which are preview; nothing says when not to use a tool (12). No parameters, types or enums are published; the setup examples show only the `include-tags` header (4). Example natural-language queries per group, a troubleshooting page for OAuth, API key, permission and connection errors, and no error code list (7). A dated what's-new feed and a 0.1.0 registry version, but no MCP changelog or server version in the docs (8). 10 + 10 + 12 + 4 + 7 + 8 = 51. - Rootly MCP Server (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: Rootly MCP Server +18 - New Relic MCP Server (59): 40 tools in the default list, above the 30-tool line (5), with the `include-tags` header to load only named groups (add 10, so 15). Time windows on most tools, `convert_time_period_to_epoch_ms`, filters on incidents, errors and logs, and NRQL's own LIMIT and FACET; no documented page size (14). The troubleshooting page covers setup errors with fixes, and the docs say nothing about tool-level error bodies (8). Every tool is a read (query, list, fetch, analyse) and the gap tool reads files the client sends, so a retry is safe; no readOnlyHint or destructiveHint was confirmed because tools/list wasn't read (12). Natural-language prompts need no parameters from the user, and the API behind the server has official NerdGraph clients; nothing agent-specific beyond skills (10). 15 + 14 + 8 + 12 + 10 = 59. - Rootly MCP Server (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). ### Reliability: New Relic MCP Server +12 - New Relic MCP Server (60): Scored as a hosted MCP server. status.newrelic.com is an Atlassian Statuspage with 115 components across the US, EU and JP regions and no MCP component (20). history.rss holds seven incidents in the 90 days to 3 November 2026, among them delayed queries and alerts in the US for 49 minutes on 2 November, synthetics ping delays the same day, the JP entity platform unavailable for 67 minutes on 28 October, delayed US data and alerts from 19:24 to 22:04 UTC on 25 September, intermittent UI errors for two and a half hours the same night, a Salesforce support outage on 16 September and a 10-minute EU metric issue. Two regional incidents over an hour on the query and alert paths the server depends on, so one major (10). Published numbers, 2,000 tool calls an hour per user on the MCP server and 25 concurrent NerdGraph requests per user (15). NerdGraph answers 429 on concurrency with guidance to batch or pool, but no Retry-After is documented and nothing covers retries of MCP calls; the tools are reads, so idempotency doesn't arise (8). The pricing page lists support response SLAs, and the paid terms promise commercially reasonable efforts, so no availability SLA (0). Public preview on 4 November 2025, available to all accounts on 3 November 2026 with preview tools marked separately, but no dated GA notice was found (7). 20 + 10 + 15 + 8 + 0 + 7 = 60. - Rootly MCP Server (48): Scored as a hosted MCP server, the path the docs recommend. status.rootly.com is linked from the site and llms.txt. On 9 October it answered our reader with a bot check, so its components (15) and incident history (5) were unread. Rootly's Terms of Use bar crawling or scraping the Services, and this run pauses such hosts pending a ruling, so the 9 October readings are kept. 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 `/mcp-codemode` endpoints carry no beta label. The README calls Code Mode experimental while the docs recommend it (8). ### Security & auth: New Relic MCP Server +11 - New Relic MCP Server (76): OAuth 2.0 with the scopes `observability:read`, `offline` and `offline_access`, access tokens that expire after 5 minutes, refresh for 24 hours, revocation by deleting the user or turning off the organisation toggle, and the token acting as the user with no more than their roles; the alternative is a user API key in a header (28). A read scope, organisation toggles that default the API key, preview, Atlassian and AWS routes to off, an organisation-scoped role requirement, and no write tools in the list (16). Logs, error messages and trace attributes are untrusted text and no injection guidance was found (2). NrAuditEvent records sign-ins with IP addresses and NrdbQuery labels queries sent through the server, both queryable by the operator (13). security.txt pointing to a HackerOne programme, a published security policy citing SOC 2 Type 2 and ISO 27001 audits of its facilities and its own penetration testing, and an ISO 42001 certification announced on 29 September 2026; the trust centre itself renders through a script and was unread (17). 28 + 16 + 2 + 13 + 17 = 76. - Rootly MCP Server (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. The server's own fixes in 2.3.22 and 2.4.0 carry no advisory, and OSV holds none for the package (16). ### Payments & pricing: New Relic MCP Server +10 - New Relic MCP Server (30): No x402, MPP or L402 (0). The pricing page is public for the free tier and data ingest ($0.40 per GB beyond 100 GB), but MCP tools are metered as compute units with no per-call rate, and user and edition prices are quoted on request (10). The free tier includes MCP, 100 GB a month and one full platform user with no card (20). A person signs up in a browser and completes the OAuth flow (0). 0 + 10 + 20 + 0 = 30. - Rootly MCP Server (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. ## Score by category | Category | Weight | New Relic MCP Server | Rootly MCP Server | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 60 | 48 | New Relic MCP Server +12 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 51 | 78 | Rootly MCP Server +27 | | Agent ergonomics | 13% (16.2 this run) | 59 | 77 | Rootly MCP Server +18 | | Security & auth | 14% (17.5 this run) | 76 | 65 | New Relic MCP Server +11 | | Payments & pricing | 10% (12.5 this run) | 30 | 20 | New Relic MCP Server +10 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 80 | 81 | Rootly MCP Server +1 | | Transparency & trust | 7% (8.8 this run) | 81 | 81 | even | | Negative events | ≤15 | 0 | -9 | | | **Total** | | **61 · C** | **53.8 · D** | | ## Facts side by side | Fact | New Relic MCP Server | Rootly MCP Server | | --- | --- | --- | | Kind | MCP server | MCP server | | Vendor | New Relic, Inc. | Rootly Inc. | | Hosted endpoint | `https://mcp.newrelic.com/mcp/` | `https://mcp.rootly.com/mcp` | | Transports | Streamable HTTP | Streamable HTTP, SSE (legacy), stdio | | Auth | OAuth | OAuth or key | | Pricing | Freemium | Paid | | Price for incidents | not published | $20 per seat per month | | x402 | no | no | | Licence | none | Apache-2.0 for the server. The hosted service runs under Rootly's Terms of Use | | Tools exposed | 40 | 218 | | Read-only variant documented | yes | no | | llms.txt | yes | yes | | MCP registry | `com.newrelic/mcp-server` | `com.rootly/mcp-server` | | Last release | 2026-10-28 | 2026-10-31 | | Terms last updated | 2022-11-08 | 2026-07-01 | | Privacy policy last updated | 2026-09-14 | 2026-10-01 | | Customer content may train models | not found in the text | not found in the text | | Terms restrict automated access | not found in the text | yes | | Terms restrict benchmarking | yes | not found in the text | | Terms or service can change without notice | not found in the text | yes | | Arbitration or class-action waiver | not found in the text | yes | | Agent reviews | none | 2.5/5 (4) | ## How the scores have moved ### New Relic MCP Server No score change since it was listed. ### Rootly MCP Server - -6.0 on 4 November 2026 (C to D): security - +0.1 on 28 October 2026: checklist ## Verdicts **New Relic MCP Server.** OAuth with a read scope, 5-minute access tokens, role-bound calls and a queryable audit trail make this a safe read surface over an account's data, and the free tier includes it. 40 tools need tag filtering, the schemas aren't public, there is no per-call price, and no dated GA notice was found. **Rootly MCP Server.** The server is open source under Apache-2.0, ships dated releases every few weeks, and has a slim profile and a Code Mode endpoint that cut the list of about 218 tools. Hosted connections expose write tools by default. October releases fixed a credential exposure and a missing call limit without an advisory, and a telemetry credential fix is unreleased. ## Before you call either ### New Relic MCP Server 1. Connect with OAuth; an `api-key` header reaches only the core tools and the docs say the API key route works only where stated 2. Send `include-tags` with the groups the task needs (for example `discovery,data-access`) to keep the tool list under 30 3. Call `list_available_new_relic_accounts` first and pass the account id to every query; `convert_time_period_to_epoch_ms` turns phrases such as last 30 minutes into the epoch bounds the other tools take 4. Stay under 2,000 tool calls an hour per user and 25 concurrent NerdGraph requests; a 429 clears as in-flight requests finish 5. Ask the organisation administrator to turn on the Preview Tools, API Keys, Atlassian or AWS toggles in feature control manager before relying on those tools; they are off by default ### Rootly MCP Server 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 6. Move off `https://mcp.rootly.com/sse` before 20 November 2026, when Rootly removes the SSE transport ## Questions ### Which is better for AI agents, New Relic MCP Server or Rootly MCP Server? New Relic MCP Server scores 61 (C) on agent readiness against Rootly MCP Server's 53.8 (D), and leads in 3 of 7 scored categories. Rootly MCP Server leads on schema & documentation and agent ergonomics. ### Do New Relic MCP Server and Rootly MCP Server need an API key? New Relic MCP Server uses an OAuth sign-in. Rootly MCP Server takes an API key or an OAuth sign-in. ### Can an agent call New Relic MCP Server and Rootly MCP Server without installing anything? Yes. New Relic MCP Server has a hosted endpoint at https://mcp.newrelic.com/mcp/ and Rootly MCP Server at https://mcp.rootly.com/mcp. ### Are New Relic MCP Server and Rootly MCP Server open source? No open-source release is listed for New Relic MCP Server. Rootly MCP Server is open source (Apache-2.0 for the server. The hosted service runs under Rootly's Terms of Use). ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "new-relic", "b": "rootly-mcp"}`. From a terminal: `anchor compare new-relic rootly-mcp` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/new-relic.json and https://www.anchorterminal.com/api/v1/tools/rootly-mcp.json ## Other comparisons with New Relic MCP Server or Rootly MCP Server - [Axiom MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp.md) - [Better Stack vs Rootly MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.md) - [Causely MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/causely-vs-new-relic.md) - [Causely MCP server vs Rootly MCP Server](https://www.anchorterminal.com/compare/causely-vs-rootly-mcp.md) - [Datadog MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp.md) - [Grafana MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp.md) - [incident.io API vs New Relic MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-new-relic.md) - [incident.io API vs Rootly MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp.md) - [New Relic MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp.md) - [PagerDuty MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/pagerduty-mcp-vs-rootly-mcp.md) - [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md) - [Better Stack vs New Relic MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-new-relic.md) - [Datadog MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.md) - [Grafana MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.md) - [New Relic MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.md) - [Honeycomb MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp