# New Relic MCP Server vs Sentry MCP (slim)

> Sentry MCP scores 66.2 (B) to New Relic's 61 (C) for observability errors. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.md (~4,300 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.json · canonical https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Sentry MCP scores 66.2 (B) on agent readiness against New Relic MCP Server's 61 (C), and leads in 3 of 7 scored categories. New Relic MCP Server leads on reliability. Both do observability errors.

- New Relic MCP Server: C 61, rank #568 of 1349 · https://www.anchorterminal.com/tools/new-relic.min.md
- Sentry MCP: B 66.2, rank #346 of 1349 · https://www.anchorterminal.com/tools/sentry-mcp.min.md
- New Relic MCP Server, good for Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough. Ahead on Reliability, 60 against 36. Also Free to start without a card.
- Sentry MCP, good for Coding agents that triage and fix production errors from Sentry. datadog-mcp covers wider observability data, pagerduty-mcp on-call and incidents. Ahead on Schema & documentation, 87 against 51; Agent ergonomics, 78 against 59; Payments & pricing, 40 against 30. Also Runs on your own machine.

| Category | New Relic MCP Server | Sentry MCP |
| --- | --- | --- |
| Reliability (16%) | 60 | 36 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 51 | 87 |
| Agent ergonomics (13%) | 59 | 78 |
| Security & auth (14%) | 76 | 75 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 80 |
| Transparency & trust (7%) | 81 | 81 |

| Fact (where they differ) | New Relic MCP Server | Sentry MCP |
| --- | --- | --- |
| Vendor | New Relic, Inc. | Sentry |
| Hosted endpoint | `https://mcp.newrelic.com/mcp/` | `https://mcp.sentry.dev/mcp` |
| Transports | Streamable HTTP | stdio, Streamable HTTP |
| Pricing | Freemium | Your plan |
| Licence | none | FSL-1.1-Apache-2.0 |
| Tools exposed | 40 | 77 |
| MCP registry | `com.newrelic/mcp-server` | `io.github.getsentry/sentry-mcp` |
| Last release | 2026-10-28 | 2026-09-25 |
| Terms last updated | 2022-11-08 | no date given |
| Privacy policy last updated | 2026-09-14 | no date given |
| Popularity | none | 837 stars, 91k npm/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Schema & documentation, Sentry MCP +36: 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.); Sentry MCP 87 (Every tool has a Zod input schema published as JSON Schema in toolDefinitions.json (25). llms.txt at docs.sentry.io and linked from mcp.sentry.dev (10). Descriptions are long and structured, with "Use this tool when", `<examples>` and `<hints>` blocks, and some say when not to use the tool, for example `add_issue_note` warns against secrets and unapproved content (18). Inputs carry required lists, `minLength` and `maxLength`, URI formats and nullable unions (13). Examples sit inside the descriptions, and errors map to typed classes with recovery hints (13). GitHub releases and tags. The release guide says to update a CHANGELOG.md the repository doesn't have (8).)
- Reliability, New Relic MCP Server +24: 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.); Sentry MCP 36 (Scored as a hosted MCP server, since mcp.sentry.dev is the default install. status.sentry.io is an Atlassian Statuspage with API, Dashboard and per-region ingestion components, but no MCP component (15). The history pages rendered on 1 November (the 1 October check could read only the front page). The 90 days from 3 August hold 23 incidents (5 critical, 10 major, 8 minor by Sentry's labels, maintenance excluded). Most name one region (US, EU or DE) or one product such as span ingestion or the dashboard, and count as partial. Four name no region or component limit. On 27 August "sentry.io is not available" ran 09:24 to 15:41 UTC and "affects the availability of our product and API". On 1 September requests timed out with 504s, 08:01 to 11:21 UTC. On 10 September 500 errors rose during a control silo migration, 15:25 to 16:26 UTC. On 20 October users had "interruptions using our UI and API", 18:20 to 21:38 UTC. Several majors (0). The hosted server's limits, 60 calls a minute per user and 300 per IP on /mcp, are in the public Wrangler config, not in user docs (8). Upstream 429s become a typed rate-limit error carrying `retry_after` when Sentry sends it, documented only in the contributor docs, and since 27 October (#1673, on main) rate-limited GETs are retried from Sentry's reset headers (8). No SLA on the pricing page (0). Versions are 0.x and `?experimental=1` variants can change between releases, with no GA statement (5). 15+0+8+8+0+5 = 36.)
- Agent ergonomics, Sentry MCP +19: 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.); Sentry MCP 78 (The hosted server deploys from main after CI passes (deploy.yml), and main's default tools/list now has 14 tools, find_organizations, find_projects, update_issue, analyze_issue_with_seer, search_issues, get_sentry_resource, the two catalogue tools and six search tools (`search_errors`, `search_logs`, `search_traces`, `search_metrics`, `search_profiles`, `search_replays`) where 0.42.0 had one `search_events`. Their generated definitions run to about 38,000 characters (name, description and input schema), against about 23,600 for the nine in 0.42.0, the npm latest. A lint rule added on 28 October (#1700) now locks the list. 11 to 30 tools, less 4 for size as the nine were (11). The other 63 tools load on demand through `search_sentry_tools` and `execute_sentry_tool`, skills narrow the set, and org or project scoping in the URL hides discovery tools (plus 7). Limits on searches and org and project constraints (17). Errors come back as typed, actionable messages, with 404s telling the agent to check the org, project or id (18). Catalogue tools set `readOnlyHint`, `destructiveHint` and `idempotentHint`, but every catalogue tool runs through `execute_sentry_tool`, still marked `destructiveHint: true` as a whole, and issue #1254 (open since 14 August per the 1 October check, not re-read on 1 November) says this breaks client allowlists and approval prompts (15). Few required parameters, npm only (10). 18+17+18+15+10 = 78.)
- Payments & pricing, Sentry MCP +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.); Sentry MCP 40 (No x402, MPP or L402 (0). The MCP server has no separate charge and Sentry's plan prices are public, with MCP included on the free Developer plan on 1 November (Team $26 and Business $80 a month billed annually) (20). The Developer plan is free with no card mentioned (20). A person has to create a Sentry account and approve OAuth (0). Self-hosted use of the AI search tools needs your own LLM provider key.)