{ "data": { "a": { "slug": "new-relic", "name": "New Relic MCP Server", "vendor": "New Relic, Inc.", "vendorUrl": "https://newrelic.com", "kind": "mcp", "category": "observability", "summary": "New Relic's hosted MCP server at mcp.newrelic.com gives AI agents read access to an account's entities, NRQL data, alerts, issues, logs, errors, traces and deployments, with OAuth or a user API key, on top of the NerdGraph API.", "url": "https://www.anchorterminal.com/tools/new-relic", "markdownUrl": "https://www.anchorterminal.com/tools/new-relic.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/new-relic.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/new-relic.json", "dns": "new-relic.grade.anchorterminal.com", "repo": "https://github.com/newrelic/nr-skills-hub", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.newrelic.com/mcp/", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 (recommended) with scopes `observability:read`, `offline` and `offline_access`; access tokens expire after 5 minutes and are refreshed, with sign-in again after 24 hours. Or a user API key (`NRAK-...`) in an `api-key` header, which the docs say only works where stated and excludes the AI analysis, gap and preview tools. An administrator must leave the MCP toggles on in feature control manager and the user needs an organisation-scoped read role. EU and JP accounts use mcp.eu.newrelic.com and mcp.jp.newrelic.com.", "pricing": "freemium", "pricingNotes": "MCP is available on every New Relic account, including the free tier (100 GB of ingest a month, one full platform user, no card). Most tools are metered as Core Compute Units against the account's allocation and four AI analysis tools as Advanced Compute Units; no per-call price is published. Data beyond 100 GB costs $0.40 per GB; user and edition prices are quoted on request (https://newrelic.com/pricing).", "priceSummary": "$0.40 / GB", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs, pricing page or terms (checked 2026-11-03). MCP calls are metered as compute units on the account's bill.", "endpoints": [] }, "toolCount": 40, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.newrelic.com/docs/agentic-ai/mcp/overview/", "llmsTxt": "https://docs.newrelic.com/llms.txt", "registryName": "com.newrelic/mcp-server", "capabilities": [ "observability.metrics", "observability.logs", "observability.errors", "observability.traces", "observability.incidents" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "remote-mcp", "mcp-registry", "oauth", "read-only-mode", "llms-txt", "status-page", "security-txt", "bug-bounty", "soc2", "eu-region", "closed-source" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 61, "grade": "C", "agentReady": false, "rank": 568, "ranked": true, "rankOf": 1349, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 59, "maintenance": 80, "payments": 30, "reliability": 60, "schema": 51, "security": 76, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "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.", "bestFor": "Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.", "strengths": [ "OAuth 2.0 with `observability:read`, access tokens that expire after 5 minutes, revocation by user or organisation toggle, and every call bound to the user's roles", "`include-tags` header limits the 40 tools to the groups a task needs, such as `discovery,alerting`", "Sign-ins and NRQL sent through the server are queryable in NrAuditEvent and NrdbQuery with a product label", "Available on the free tier (100 GB a month, no card) and rate-limited at a published 2,000 tool calls an hour per user", "llms.txt and Markdown twins of every docs page, a dated what's-new feed and a verified registry namespace" ], "weaknesses": [ "Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters", "40 tools in the default list, above the 30-tool line, unless the client sends `include-tags`", "No per-call price; tools are metered as Core and Advanced Compute Units on the account's bill", "Public preview since 4 November 2025 with no dated general availability notice found, and preview tools mixed into the list", "Logs, errors and traces come back as untrusted text with no prompt-injection guidance; the trust centre renders through a script our reader can't run" ], "agentNotes": [ "Connect with OAuth; an `api-key` header reaches only the core tools and the docs say the API key route works only where stated", "Send `include-tags` with the groups the task needs (for example `discovery,data-access`) to keep the tool list under 30", "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", "Stay under 2,000 tool calls an hour per user and 25 concurrent NerdGraph requests; a 429 clears as in-flight requests finish", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61 } ], "editorialScores": { "ergonomics": 59, "maintenance": 80, "payments": 30, "reliability": 60, "schema": 51, "security": 76, "transparency": 63 }, "provenanceScore": 98, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http --scope user newrelic https://mcp.newrelic.com/mcp/", "config": { "mcpServers": { "newrelic": { "type": "http", "url": "https://mcp.newrelic.com/mcp/" } } } }, "letme": { "capability": "https://letme.dev/observability.metrics", "tool": "https://letme.dev/new-relic" }, "area": "developer", "unitPrices": [ { "item": "Data ingest beyond 100 GB a month", "unit": "gb", "usd": 0.4, "note": "100 GB a month free on every edition. User and compute prices are quoted on request" } ], "provenance": { "legalEntity": "New Relic, Inc.", "domain": "newrelic.com", "domainRegistered": "2006-04-19", "endpointOnVendorDomain": true, "terms": "https://newrelic.com/termsandconditions/paid", "privacy": "https://newrelic.com/termsandconditions/privacy", "statusPage": "https://status.newrelic.com", "changelog": "https://docs.newrelic.com/whats-new/", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The paid terms of service are dated 8 November 2022 and the unpaid terms 21 October 2021; the master cloud agreement path is disallowed by newrelic.com/robots.txt and wasn't read. The privacy notice is dated 14 September 2026.", "newrelic.com/robots.txt disallows /signup/, /lp/, the master cloud agreement and a few files; /security redirected to trust.newrelic.com, which renders through a script and was not readable. docs.newrelic.com allows everything.", "security.txt at newrelic.com/.well-known/security.txt points to HackerOne for contact and policy.", "status.newrelic.com is an Atlassian Statuspage with 115 components across US, EU and JP; the history page needs JavaScript, so the 90-day record was read from history.rss, which holds 25 incidents back to 12 January 2026.", "RDAP gives newrelic.com a registration date of 19 April 2006. firstReleased is 4 November 2025, the public preview date of the MCP server." ], "score": 98 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/new-relic.json", "live": { "slug": "new-relic", "probe": { "target": "https://mcp.newrelic.com/mcp/", "method": "mcp-initialize", "lastAt": "2026-11-04T22:02:48.316152545Z", "lastOk": true, "lastStatus": 401, "lastMs": 290, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 327, "p95ms24h": 416, "samples24h": 68, "samples30d": 68, "days": [ { "date": "2026-11-04", "probes": 68, "ok": 68 } ] }, "vendorStatus": { "page": "https://status.newrelic.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T22:01:07.788866756Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.newrelic/mcp-server", "version": "0.1.0", "seenAt": "2026-11-04T17:11:44.552009456Z" } ], "githubStars": 7, "securityTxt": { "url": "https://newrelic.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:54:45.364182842Z" }, "updatedAt": "2026-11-04T22:02:48.316152545Z" } }, "answer": "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.", "b": { "slug": "sentry-mcp", "name": "Sentry MCP", "vendor": "Sentry", "vendorUrl": "https://sentry.io", "kind": "mcp", "category": "observability", "summary": "Sentry's MCP for searching errors and traces, triaging issues, reading docs and managing projects, with agent-embedded natural-language search tools.", "url": "https://www.anchorterminal.com/tools/sentry-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/sentry-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sentry-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sentry-mcp.json", "dns": "sentry-mcp.grade.anchorterminal.com", "repo": "https://github.com/getsentry/sentry-mcp", "license": "FSL-1.1-Apache-2.0", "transports": [ "stdio", "streamable-http" ], "remoteUrl": "https://mcp.sentry.dev/mcp", "packages": [ { "registry": "npm", "name": "@sentry/mcp-server" } ], "auth": "oauth", "authNotes": "Remote uses Sentry's own OAuth layer, where the user picks skills (Inspect and Seer by default, Triage and Manage Projects opt-in), or a `Sentry-Bearer` header with a Sentry token. The upstream token always carries org:read, project:write, team:write, event:write and alerts:write. Stdio uses SENTRY_ACCESS_TOKEN, with --host/SENTRY_HOST for self-hosted. Org or project scoping in the URL hides discovery tools; ?experimental=1 enables experimental variants.", "pricing": "byo-plan", "pricingNotes": "No separate charge; uses your Sentry org. AI-powered search tools require an LLM provider key when self-hosting the server.", "priceSummary": "Your plan", "where": "both", "x402": { "level": "no", "evidence": "No x402 support in README or docs.", "endpoints": [] }, "toolCount": 77, "popularity": { "githubStars": 837, "npmWeekly": 90552, "pypiWeekly": null, "asOf": "2026-09-26" }, "docsUrl": "https://mcp.sentry.dev/", "llmsTxt": "https://docs.sentry.io/llms.txt", "registryName": "io.github.getsentry/sentry-mcp", "capabilities": [ "observability.errors" ], "tags": [ "official", "hosted", "local", "source-available", "oauth" ], "lastRelease": "2026-09-25", "graded": true, "anchor": { "graded": true, "score": 66.2, "grade": "B", "agentReady": false, "rank": 346, "ranked": true, "rankOf": 1349, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 80, "payments": 40, "reliability": 36, "schema": 87, "security": 75, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "OAuth with skills chosen at consent keeps the default grant read-only, and tools beyond the default list load on demand. status.sentry.io has no MCP component and recorded four service-wide majors in the 90 days to 1 November, and there's no SLA.", "bestFor": "Coding agents that triage and fix production errors from Sentry. datadog-mcp covers wider observability data, pagerduty-mcp on-call and incidents.", "strengths": [ "OAuth with skills chosen at consent, Inspect and Seer (read-only) by default", "14 default tools with 63 more loaded on demand, plus org and project scoping in the URL", "Descriptions with usage guidance, examples and hints, and typed errors with recovery advice", "Read-only, destructive and idempotent annotations across the catalogue", "Five MCP server releases in the 90 days to 1 November, the newest on 25 September, and a registry entry published from CI" ], "weaknesses": [ "No MCP component on status.sentry.io and no SLA", "Four service-wide major incidents between 27 August and 20 October 2026", "The upstream Sentry token always holds project, team, event and alert write scopes", "`execute_sentry_tool` wraps every catalogue tool and is marked destructive, which breaks per-tool approval (issue #1254)", "Functional Source License, not OSI-approved until each version's two-year conversion" ], "agentNotes": [ "Put the org and project in the URL (mcp.sentry.dev/mcp/\u003corg\u003e/\u003cproject\u003e) to drop the discovery tools", "Call `search_sentry_tools` to find a catalogue tool, then `execute_sentry_tool` to run it", "Use `get_sentry_resource` with an issue or trace URL when you have one. It's faster than natural-language search", "Pick the dataset's own search tool on the hosted server (`search_errors`, `search_logs`, `search_traces`); `search_events` is in the catalogue and in the 0.42.0 stdio package", "Grant Triage only when the task needs to resolve or assign issues. The default skills are read-only" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.2 } ], "editorialScores": { "ergonomics": 78, "maintenance": 80, "payments": 40, "reliability": 36, "schema": 87, "security": 75, "transparency": 70 }, "provenanceScore": 92, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http sentry https://mcp.sentry.dev/mcp", "config": { "mcpServers": { "sentry": { "url": "https://mcp.sentry.dev/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.errors", "tool": "https://letme.dev/sentry-mcp" }, "area": "developer", "provenance": { "legalEntity": "Functional Software, Inc. d/b/a Sentry", "domain": "sentry.dev", "domainRegistered": "2019-02-22", "domainNote": "The MCP server runs on sentry.dev, Sentry's secondary domain. Its security.txt redirects to sentry.io.", "endpointOnVendorDomain": true, "terms": "https://sentry.io/terms/", "privacy": "https://sentry.io/privacy/", "statusPage": "https://status.sentry.io", "changelog": "https://github.com/getsentry/sentry-mcp/releases", "securityTxt": "valid", "checked": "2026-11-01", "score": 92 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sentry-mcp.json", "live": { "slug": "sentry-mcp", "probe": { "target": "https://mcp.sentry.dev/mcp", "method": "mcp-initialize", "lastAt": "2026-11-04T22:02:58.087344106Z", "lastOk": true, "lastStatus": 401, "lastMs": 48, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 62, "p95ms24h": 171, "samples24h": 247, "samples30d": 8094, "days": [ { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 227, "ok": 227 } ] }, "vendorStatus": { "page": "https://status.sentry.io", "indicator": "maintenance", "summary": "Service Under Maintenance", "checkedAt": "2026-11-04T22:01:31.503561036Z" }, "versions": [ { "registry": "github", "name": "getsentry/sentry-mcp", "version": "cli@0.47.0", "released": "2026-10-05", "seenAt": "2026-11-04T20:54:14.207731697Z" }, { "registry": "mcp-registry", "name": "io.github.getsentry/sentry-mcp", "version": "0.42.0", "seenAt": "2026-11-04T17:11:44.552009456Z" }, { "registry": "npm", "name": "@sentry/mcp-server", "version": "0.42.0", "seenAt": "2026-11-04T20:54:13.370558466Z" } ], "githubStars": 956, "npmWeekly": 237679, "securityTxt": { "url": "https://sentry.dev/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:53:11.694970759Z" }, "llmsTxt": { "url": "https://docs.sentry.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:24:12.464298664Z" }, "domain": { "domain": "sentry.dev", "registered": "2019-02-22", "source": "https://pubapi.registry.google/rdap/domain/sentry.dev", "checkedAt": "2026-11-01T14:09:47.922674609Z" }, "pages": [ { "url": "https://sentry.io/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:32:24.987633611Z", "changedAt": "2026-10-16T22:30:47.158468237Z", "fingerprint": "876c46e30cd9" }, { "url": "https://sentry.io/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:32:28.401789551Z", "changedAt": "2026-10-16T22:30:49.493187637Z", "fingerprint": "38f4851f203b" } ], "mcpTools": { "url": "https://mcp.sentry.dev/mcp", "checkedAt": "2026-11-04T01:23:02.742166191Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-09-28T21:55:54.523074666Z" }, "github": { "repo": "getsentry/sentry-mcp", "checkedAt": "2026-11-02T08:50:16.565064068Z", "stars": 952, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T06:16:16Z", "openIssues": 123, "openPRs": 58, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-11-01T20:35:06Z" }, "replies": { "sampled": 25, "unanswered": 7, "medianDays": 0.3 } }, "updatedAt": "2026-11-04T22:02:58.087344106Z" } }, "edges": [ { "by": 36, "category": "schema", "leads": "sentry-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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\", `\u003cexamples\u003e` and `\u003chints\u003e` 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)." }, "scores": { "a": 51, "b": 87 } }, { "by": 24, "category": "reliability", "leads": "new-relic", "name": "Reliability", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 60, "b": 36 } }, { "by": 19, "category": "ergonomics", "leads": "sentry-mcp", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 59, "b": 78 } }, { "by": 10, "category": "payments", "leads": "sentry-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 30, "b": 40 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "New Relic, Inc.", "b": "Sentry", "name": "Vendor" }, { "a": "https://mcp.newrelic.com/mcp/", "b": "https://mcp.sentry.dev/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "stdio, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Your plan", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "FSL-1.1-Apache-2.0", "name": "Licence" }, { "a": "40", "b": "77", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.newrelic/mcp-server", "b": "io.github.getsentry/sentry-mcp", "name": "MCP registry" }, { "a": "2026-10-28", "b": "2026-09-25", "name": "Last release" }, { "a": "2022-11-08", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-09-14", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "837 stars, 91k npm/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "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.", "question": "Which is better for AI agents, New Relic MCP Server or Sentry MCP?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do New Relic MCP Server and Sentry MCP need an API key?" }, { "answer": "Yes. New Relic MCP Server has a hosted endpoint at https://mcp.newrelic.com/mcp/ and Sentry MCP at https://mcp.sentry.dev/mcp.", "question": "Can an agent call New Relic MCP Server and Sentry MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 60 against 36" ], "also": [ "Free to start without a card" ], "goodFor": "Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.", "slug": "new-relic", "watchFor": "Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters" }, { "aheadOn": [ "Schema \u0026 documentation, 87 against 51", "Agent ergonomics, 78 against 59", "Payments \u0026 pricing, 40 against 30" ], "also": [ "Runs on your own machine" ], "goodFor": "Coding agents that triage and fix production errors from Sentry. datadog-mcp covers wider observability data, pagerduty-mcp on-call and incidents.", "slug": "sentry-mcp", "watchFor": "No MCP component on status.sentry.io and no SLA" } ], "history": { "new-relic": null, "sentry-mcp": [ { "causes": [ "product", "evidence", "time" ], "date": "2026-11-01", "delta": -4, "from": 70.2, "fromGrade": "BB", "to": 66.2, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 70.4, "fromGrade": "BB", "to": 70.2, "toGrade": "BB" } ] }, "job": { "capability": "observability.errors", "name": "Observability errors" }, "others": [ { "json": "https://www.anchorterminal.com/compare/causely-vs-new-relic.json", "title": "Causely MCP server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/causely-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/incident-io-vs-new-relic.json", "title": "incident.io API vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/incident-io-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp.json", "title": "New Relic MCP Server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp.json", "title": "New Relic MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-new-relic.json", "title": "Axiom MCP Server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic.json", "title": "Better Stack vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.json", "title": "Datadog MCP Server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.json", "title": "Grafana MCP Server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.json", "title": "Axiom MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp.json", "title": "Better Stack vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/causely-vs-sentry-mcp.json", "title": "Causely MCP server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/causely-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp.json", "title": "Datadog MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-sentry-mcp.json", "title": "Grafana MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp.json", "title": "Honeycomb MCP vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.json", "title": "Honeycomb MCP vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic" } ], "panel": null, "scores": [ { "by": 24, "edge": "new-relic", "key": "reliability", "name": "Reliability", "new-relic": 60, "sentry-mcp": 36, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 36, "edge": "sentry-mcp", "key": "schema", "name": "Schema \u0026 documentation", "new-relic": 51, "sentry-mcp": 87, "weight": 13 }, { "by": 19, "edge": "sentry-mcp", "key": "ergonomics", "name": "Agent ergonomics", "new-relic": 59, "sentry-mcp": 78, "weight": 13 }, { "by": 1, "edge": "new-relic", "key": "security", "name": "Security \u0026 auth", "new-relic": 76, "sentry-mcp": 75, "weight": 14 }, { "by": 10, "edge": "sentry-mcp", "key": "payments", "name": "Payments \u0026 pricing", "new-relic": 30, "sentry-mcp": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 0, "edge": "", "key": "maintenance", "name": "Maintenance \u0026 community", "new-relic": 80, "sentry-mcp": 80, "weight": 7 }, { "by": 0, "edge": "", "key": "transparency", "name": "Transparency \u0026 trust", "new-relic": 81, "sentry-mcp": 81, "weight": 7 } ], "summary": "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.", "tasks": null, "tutorials": [], "verdicts": { "new-relic": "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.", "sentry-mcp": "OAuth with skills chosen at consent keeps the default grant read-only, and tools beyond the default list load on demand. status.sentry.io has no MCP component and recorded four service-wide majors in the 90 days to 1 November, and there's no SLA." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp", "json": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.min.md" }, "markdown": "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.\n\n- 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\n- Sentry MCP: grade B, 66.2/100, rank #346 of 1349. Markdown https://www.anchorterminal.com/tools/sentry-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/sentry-mcp.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 49 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### New Relic MCP Server (C)\n\nGood for: Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.\n\nAhead on:\n- Reliability, 60 against 36\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters\n\n### Sentry MCP (B)\n\nGood for: Coding agents that triage and fix production errors from Sentry. datadog-mcp covers wider observability data, pagerduty-mcp on-call and incidents.\n\nAhead on:\n- Schema \u0026 documentation, 87 against 51\n- Agent ergonomics, 78 against 59\n- Payments \u0026 pricing, 40 against 30\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No MCP component on status.sentry.io and no SLA\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Sentry MCP +36\n\n- 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.\n- 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\", `\u003cexamples\u003e` and `\u003chints\u003e` 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).\n\n### Reliability: New Relic MCP Server +24\n\n- 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.\n- 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.\n\n### Agent ergonomics: Sentry MCP +19\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: Sentry MCP +10\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | New Relic MCP Server | Sentry MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 36 | New Relic MCP Server +24 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 51 | 87 | Sentry MCP +36 |\n| Agent ergonomics | 13% (16.2 this run) | 59 | 78 | Sentry MCP +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 75 | New Relic MCP Server +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Sentry MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 80 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 81 | 81 | even |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61 · C** | **66.2 · B** | |\n\n## Facts side by side\n\n| Fact | New Relic MCP Server | Sentry MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | New Relic, Inc. | Sentry |\n| Hosted endpoint | `https://mcp.newrelic.com/mcp/` | `https://mcp.sentry.dev/mcp` |\n| Transports | Streamable HTTP | stdio, Streamable HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Freemium | Your plan |\n| x402 | no | no |\n| Licence | none | FSL-1.1-Apache-2.0 |\n| Tools exposed | 40 | 77 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| MCP registry | `com.newrelic/mcp-server` | `io.github.getsentry/sentry-mcp` |\n| Last release | 2026-10-28 | 2026-09-25 |\n| Terms last updated | 2022-11-08 | no date given |\n| Privacy policy last updated | 2026-09-14 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 837 stars, 91k npm/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## How the scores have moved\n\n### New Relic MCP Server\n\nNo score change since it was listed.\n\n### Sentry MCP\n\n- -4.0 on 1 November 2026 (BB to B): product, new evidence, time\n- -0.2 on 8 October 2026: checklist\n\n## Verdicts\n\n**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.\n\n**Sentry MCP.** OAuth with skills chosen at consent keeps the default grant read-only, and tools beyond the default list load on demand. status.sentry.io has no MCP component and recorded four service-wide majors in the 90 days to 1 November, and there's no SLA.\n\n## Before you call either\n\n### New Relic MCP Server\n\n1. Connect with OAuth; an `api-key` header reaches only the core tools and the docs say the API key route works only where stated\n2. Send `include-tags` with the groups the task needs (for example `discovery,data-access`) to keep the tool list under 30\n3. 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\n4. Stay under 2,000 tool calls an hour per user and 25 concurrent NerdGraph requests; a 429 clears as in-flight requests finish\n5. 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\n\n### Sentry MCP\n\n1. Put the org and project in the URL (mcp.sentry.dev/mcp/\u003corg\u003e/\u003cproject\u003e) to drop the discovery tools\n2. Call `search_sentry_tools` to find a catalogue tool, then `execute_sentry_tool` to run it\n3. Use `get_sentry_resource` with an issue or trace URL when you have one. It's faster than natural-language search\n4. Pick the dataset's own search tool on the hosted server (`search_errors`, `search_logs`, `search_traces`); `search_events` is in the catalogue and in the 0.42.0 stdio package\n5. Grant Triage only when the task needs to resolve or assign issues. The default skills are read-only\n\n## Questions\n\n### Which is better for AI agents, New Relic MCP Server or Sentry MCP?\n\nSentry 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.\n\n### Do New Relic MCP Server and Sentry MCP need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call New Relic MCP Server and Sentry MCP without installing anything?\n\nYes. New Relic MCP Server has a hosted endpoint at https://mcp.newrelic.com/mcp/ and Sentry MCP at https://mcp.sentry.dev/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"new-relic\", \"b\": \"sentry-mcp\"}`. From a terminal: `anchor compare new-relic sentry-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/new-relic.json and https://www.anchorterminal.com/api/v1/tools/sentry-mcp.json\n\n## Other comparisons with New Relic MCP Server or Sentry MCP\n\n- [Causely MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/causely-vs-new-relic.md)\n- [incident.io API vs New Relic MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-new-relic.md)\n- [New Relic MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp.md)\n- [New Relic MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp.md)\n- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md)\n- [Better Stack vs New Relic MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-new-relic.md)\n- [Datadog MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.md)\n- [Grafana MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.md)\n- [Axiom MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.md)\n- [Better Stack vs Sentry MCP](https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp.md)\n- [Causely MCP server vs Sentry MCP](https://www.anchorterminal.com/compare/causely-vs-sentry-mcp.md)\n- [Datadog MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp.md)\n- [Grafana MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-sentry-mcp.md)\n- [Honeycomb MCP vs Sentry MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp.md)\n- [Honeycomb MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "New Relic MCP Server vs Sentry MCP", "url": "" } ], "description": "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.", "facts": [ "New Relic MCP Server C 61", "Sentry MCP B 66.2", "scores" ], "h1": "New Relic MCP Server vs Sentry MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/new-relic-vs-sentry-mcp", "published": "2026-10-01", "section": "tools", "title": "New Relic vs Sentry MCP for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp" }, "tokens": { "markdown": 4300, "slim": 2580 }, "version": 1 }