{ "data": { "a": { "slug": "grafana-mcp-server", "name": "Grafana MCP Server", "vendor": "Grafana Labs", "vendorUrl": "https://grafana.com/docs/grafana/latest/developer-resources/mcp/", "kind": "mcp", "category": "observability", "summary": "Grafana Labs' open-source MCP server for Grafana. It runs locally or self-hosted and gives agents dashboards, datasource queries (Prometheus, Loki, Tempo, Pyroscope and others), alerting, incidents and OnCall on a self-managed Grafana or Grafana Cloud.", "url": "https://www.anchorterminal.com/tools/grafana-mcp-server", "markdownUrl": "https://www.anchorterminal.com/tools/grafana-mcp-server.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/grafana-mcp-server.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/grafana-mcp-server.json", "dns": "grafana-mcp-server.grade.anchorterminal.com", "repo": "https://github.com/grafana/mcp-grafana", "license": "Apache-2.0", "transports": [ "stdio", "sse", "streamable-http" ], "packages": [ { "registry": "pypi", "name": "mcp-grafana" }, { "registry": "oci", "name": "grafana/mcp-grafana" }, { "registry": "go", "name": "github.com/grafana/mcp-grafana/v2" } ], "auth": "mixed", "authNotes": "The server signs in to Grafana with a service account token (`GRAFANA_SERVICE_ACCOUNT_TOKEN`, or a file path in `GRAFANA_SERVICE_ACCOUNT_TOKEN_FILE` that is re-read on each request), or with `GRAFANA_USERNAME` and `GRAFANA_PASSWORD`. An admin creates the token in Grafana, self-serve, and Grafana RBAC sets what it can do. The README lists the permissions each tool needs. Over streamable HTTP a caller can send its own token in `X-Grafana-Service-Account-Token`, and `--server-auth-token` makes callers present a bearer token to the server itself. stdio needs no caller credential.", "pricing": "free", "pricingNotes": "Free and open source under Apache-2.0, with nothing to buy for the server. It needs a Grafana instance, which can be self-managed open-source Grafana or Grafana Cloud. Grafana Cloud prices were not checked. The separate hosted Grafana Cloud MCP server counts towards Grafana Assistant usage (checked 2026-10-08).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, the docs or the changelog (checked 2026-10-08).", "endpoints": [] }, "toolCount": 119, "popularity": { "githubStars": 3535, "npmWeekly": null, "pypiWeekly": 151923, "asOf": "2026-10-08" }, "docsUrl": "https://grafana.com/docs/grafana/latest/developer-resources/mcp/", "llmsTxt": "https://grafana.com/llms.txt", "registryName": "io.github.grafana/mcp-grafana", "capabilities": [ "observability.metrics", "observability.logs", "observability.traces", "observability.incidents", "work.oncall" ], "tags": [ "official", "local", "open-source", "self-hosted", "mcp", "go", "docker", "helm", "grafana", "llms-txt", "telemetry-default-on" ], "lastRelease": "2026-10-20", "graded": true, "anchor": { "graded": true, "score": 71, "grade": "BB", "agentReady": true, "rank": 154, "ranked": true, "rankOf": 1349, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 96, "payments": 60, "reliability": 91, "schema": 81, "security": 67, "transparency": 80 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-01" }, "negative": -7, "negativeNotes": [ "-2: CVE-2026-15583 (high, CVSS 8.6), published by Grafana Labs on 15 July 2026. Before the fix, a URL in the then undocumented `X-Grafana-URL` request header made the server send its environment service account token to a host the caller chose, an unauthenticated exfiltration path on the HTTP transports. The changelog records the fix in 0.17.2 on 13 July, the advisory lists 0.17.1. Fixed and published, about three months old (https://grafana.com/security/security-advisories/cve-2026-15583/).", "-2: CVE-2026-19516 (critical, CVSS 9.1), published on 11 August 2026. A caller of `grafana_api_request` could still steer the server's requests through `X-Grafana-URL` to internal, loopback and link-local services, metadata endpoints included, and read the responses, since the July fix guarded only the token. Fixed in 1.1.0 on 10 August, which removed the header, and published, about two months old (https://grafana.com/security/security-advisories/cve-2026-19516/).", "-3: v2.1.0, a minor release on 20 October 2026, changed `list_users_by_org` to a paginated tool that returns `{totalCount, page, perPage, orgUsers}` instead of an array of users. The changelog labels it Breaking on the day, and no earlier notice was found (CHANGELOG.md changed only in the release commit, and the 7 October pull request changed only the tool's description). The admin tools are off by default and Grafana Labs says agents need no changes, so the floor (https://github.com/grafana/mcp-grafana/blob/main/CHANGELOG.md)." ], "verdict": "Every default tool declares typed inputs and read-only and destructive annotations in source, and `--disable-write` cuts the default 79 tools to 62. Writes and a general `grafana_api_request` tool are on by default, the default list is long at 79 tools, and two `X-Grafana-URL` flaws, one rated critical, were fixed in July and August 2026.", "bestFor": "Teams on Grafana, self-managed or Cloud, that want an agent to read dashboards and query Prometheus, Loki, Tempo and Pyroscope, and to work with alert rules, incidents and OnCall.", "strengths": [ "All 79 default tools in 2.0.2 build typed JSON Schema inputs from Go parameter structs and set `readOnlyHint` and `destructiveHint`, and 73 also set `idempotentHint`, read from source at tag v2.0.2", "`--disable-write`, `--disable-query`, per-category flags and Loki enforced matchers narrow what the server can do, with a per-tool table of required RBAC permissions", "16 tagged releases between 28 July and 7 October 2026, with a Keep a Changelog file that labels breaking changes", "Listed in the official MCP registry under the verified `io.github.grafana` namespace, with 2.0.2 marked latest from 10 October 2026", "Dashboard summary, JSONPath property reads, jq filtering and a 100-line Loki default keep responses small" ], "weaknesses": [ "The default set is 79 tools, and 119 with every category on, counted from the registration code in source", "Write tools and `grafana_api_request`, which can call any Grafana API path, are enabled unless the operator turns them off", "Anonymous usage statistics went from off by default in 1.5.0 (17 September 2026) to on by default in 2.0.0", "Two `X-Grafana-URL` flaws in 2026, a token leak (CVE-2026-15583, high) and an SSRF (CVE-2026-19516, critical), fixed in 0.17.2 and 1.1.0", "Minor release 2.1.0 changed `list_users_by_org` output on 20 October 2026 with no advance notice, and the repository has no SECURITY.md" ], "agentNotes": [ "Start with `--disable-write` unless the task needs writes, and add `--disable-api` to remove `grafana_api_request`", "Pass `--enabled-tools` with only the categories needed. The default list loads 79 tools", "Use `get_dashboard_summary` or `get_dashboard_property` with a JSONPath before `get_dashboard_by_uid`, which returns the whole dashboard JSON", "Set `GRAFANA_USAGE_STATS=disabled` or `DO_NOT_TRACK=1` to stop the four-hourly usage report to stats.grafana.org", "Use streamable HTTP, not SSE, when each caller needs its own token or organisation, and set `--server-auth-token` on any non-loopback address" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71 } ], "editorialScores": { "ergonomics": 74, "maintenance": 96, "payments": 60, "reliability": 91, "schema": 81, "security": 67, "transparency": 81 }, "provenanceScore": 78, "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": { "install": "uvx mcp-grafana", "config": { "mcpServers": { "grafana": { "args": [ "mcp-grafana" ], "command": "uvx", "env": { "GRAFANA_SERVICE_ACCOUNT_TOKEN": "\u003cyour service account token\u003e", "GRAFANA_URL": "http://localhost:3000" } } } } }, "letme": { "capability": "https://letme.dev/observability.metrics", "tool": "https://letme.dev/grafana-mcp-server" }, "area": "developer", "provenance": { "legalEntity": "Raintank Inc., d/b/a Grafana Labs", "domain": "grafana.com", "domainRegistered": "2014-05-27", "endpointOnVendorDomain": null, "terms": "", "privacy": "https://grafana.com/legal/privacy-policy/", "statusPage": "", "changelog": "https://github.com/grafana/mcp-grafana/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "No terms document governs this software beyond the Apache-2.0 licence, so `terms` is left out.", "The privacy policy (last updated 10 July 2026) names Raintank Inc., d/b/a Grafana Labs, 165 Broadway, 23rd Floor, New York, and says its open-source and commercial software may report usage statistics.", "grafana.com/.well-known/security.txt returns 404. Reports go to an Intigriti disclosure programme or security@grafana.com, with no bounties (https://grafana.com/legal/report-a-security-issue/).", "RDAP for grafana.com gives a registration date of 2014-05-27.", "The server runs on the owner's machine. Usage reports go to stats.grafana.org, a second Grafana Labs domain." ], "score": 78 }, "requirements": { "card": "no", "freeTier": true, "minutes": 10, "credential": "api-key", "hosting": [ "self-hosted" ], "euResidency": "unknown", "trainsOnData": "no", "zeroRetention": "unknown", "selfHost": "yes" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/grafana-mcp-server.json", "live": { "slug": "grafana-mcp-server", "versions": [ { "registry": "github", "name": "grafana/mcp-grafana", "version": "v2.2.0", "released": "2026-11-02", "seenAt": "2026-11-04T20:20:27.77772694Z" }, { "registry": "mcp-registry", "name": "io.github.grafana/mcp-grafana", "version": "v2.2.0", "seenAt": "2026-11-04T17:11:44.552009456Z" }, { "registry": "pypi", "name": "mcp-grafana", "version": "2.2.0", "released": "2026-11-02", "seenAt": "2026-11-04T20:20:27.648731705Z" } ], "githubStars": 3640, "pypiWeekly": 99402, "securityTxt": { "url": "https://grafana.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:18.985935709Z" }, "llmsTxt": { "url": "https://grafana.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:23:07.728680516Z" }, "domain": { "domain": "grafana.com", "registered": "2014-05-27", "source": "https://rdap.verisign.com/com/v1/domain/grafana.com", "checkedAt": "2026-11-01T14:20:13.960632327Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/grafana/mcp-grafana/main/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-04T08:33:44.229180515Z", "changedAt": "2026-11-03T07:59:43.081071646Z", "fingerprint": "78c3abe924b6" }, { "url": "https://grafana.com/legal/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:24:38.454854719Z", "changedAt": "2026-11-04T08:24:38.454854719Z", "fingerprint": "dec83a9810c5" } ], "github": { "repo": "grafana/mcp-grafana", "checkedAt": "2026-11-02T08:52:46.468852437Z", "stars": 3631, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T08:37:17Z", "openIssues": 55, "openPRs": 38, "issuesOpened90d": 92, "issuesClosed90d": 113, "prsMerged90d": 267, "ci": { "branch": "main", "runs": 50, "success": 48, "failure": 2, "other": 0, "latest": "success", "latestAt": "2026-11-02T08:35:00Z" }, "replies": { "sampled": 25, "unanswered": 6, "medianDays": 1.2 } }, "updatedAt": "2026-11-04T20:20:27.77772694Z" } }, "answer": "Grafana MCP Server scores 71 (BB) on agent readiness against New Relic MCP Server's 61 (C), and leads in 5 of 7 scored categories. New Relic MCP Server leads on security \u0026 auth.", "b": { "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": 567, "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-04T21:39:36.212939859Z", "lastOk": true, "lastStatus": 401, "lastMs": 302, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 327, "p95ms24h": 416, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-04", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://status.newrelic.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T21:38:31.653792842Z" }, "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-04T21:39:36.212939859Z" } }, "edges": [ { "by": 31, "category": "reliability", "leads": "grafana-mcp-server", "name": "Reliability", "reasons": { "a": "Scored as local software, since the owner runs it over stdio, SSE or streamable HTTP. Official PyPI package `mcp-grafana` (a wheel that carries the Go binary, Python 3.10 or later), a Docker image, release binaries and a Helm chart, with Grafana 9.0 or later stated as the requirement (20). Unit, integration and end-to-end workflows all concluded in success on main on 8 October 2026, per the 8 October check, not re-read on 1 November (25). Per the 8 October check, not re-read on 1 November, 54 open issues, none labelled bug, and 38 closed in the 30 days before that check. Three bug reports remained open from July and August (#992 `run_panel_query` 422, #1005 `grafana_api_request` 500 on plugin resources, #1049 a dropped table row in `get_panel_image`), each with replies. A stale issue and pull request workflow was added on 27 October (19 of 25). The changelog follows Keep a Changelog and semantic versioning and labels breaking changes, and 1.6.2 announced that 2.0 came next. Patch release 1.4.1 carried a breaking parameter change on the Sift tools, 2.0.0 followed 1.0.0 by two months, and minor release 2.1.0 on 20 October changed the output of `list_users_by_org`, labelled on the day (12 of 15). Version 2.1.1, the latest release on 1 November (15).", "b": "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." }, "scores": { "a": 91, "b": 60 } }, { "by": 30, "category": "schema", "leads": "grafana-mcp-server", "name": "Schema \u0026 documentation", "reasons": { "a": "Read from source at tag v2.0.2, without running it, and unchanged in count at v2.1.1. All 79 default tools build their JSON Schema input by reflection from a typed Go parameter struct, and `buildInputSchema` in `tools.go` sets `additionalProperties` to false. No tool sets an output schema, which issue #1278 asks for (23 of 25). grafana.com serves llms.txt and a Markdown form of every docs page, the MCP pages included (10). Descriptions state purpose and inputs. Version 2.0.2 removed model directives and references to other tools from descriptions to meet connector directory rules, so guidance on when to use a tool is thinner than it was (14 of 20). Nearly every parameter field in the source structs carries a description tag, but few declare an enum. Values such as `queryType` ('range' or 'instant') and incident `status` are named in prose, and some parameters are free-form objects (9 of 15). The docs have client configuration examples, task guides and a troubleshooting page, and empty results return hints. No catalogue of error responses was found (10 of 15). Semantic versions, tagged releases and a dated changelog (15).", "b": "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." }, "scores": { "a": 81, "b": 51 } }, { "by": 30, "category": "payments", "leads": "grafana-mcp-server", "name": "Payments \u0026 pricing", "reasons": { "a": "Read with the self-hosted rule. The server is free under Apache-2.0 and needs no signup of its own, so 20 + 20 + 20. No x402, MPP or L402 (0). It needs a Grafana instance, which can be the free open-source Grafana. Grafana Cloud prices were not checked. The separate hosted Grafana Cloud MCP server counts towards Grafana Assistant usage and is not what this listing grades.", "b": "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." }, "scores": { "a": 60, "b": 30 } }, { "by": 16, "category": "maintenance", "leads": "grafana-mcp-server", "name": "Maintenance \u0026 community", "reasons": { "a": "v2.1.1 tagged on 20 October 2026, 12 days before the check, after v2.1.0 the same day, with commits on main to 31 October (30). 17 tagged releases from 1.1.0 on 10 August to 2.1.1 in the 90 days to 1 November (20). Per the 8 October check, not re-read on 1 November, 38 issues closed in the 30 days before that check against 54 open and 22 open pull requests, and several feature requests from March and April without a reply (21 of 25). Listed in the official MCP registry as `io.github.grafana/mcp-grafana`, a GitHub-verified namespace, with v2.1.1 published on 20 October and marked latest (15). Renovate, a Docker image scan workflow, cosign signing with SPDX SBOMs for releases from 2.1.0, and Go toolchain and dependency bumps for CVEs on 21 and 28 October (10).", "b": "Read as a closed service. The what's-new feed and press releases record changes through October 2026, the latest on 28 October (Change Tracking in GitHub Copilot), and docs llms.txt was regenerated on 3 November (30). More than three dated entries in 90 days, among them the Ground Truth CLI on 6 October, the CEO appointment on 1 October, OpenTelemetry AI monitoring in August and the ISO 42001 announcement (20). A support portal, in-app support and a community forum; the skills hub repository on GitHub, whose issue replies couldn't be read (10 of 15). com.newrelic/mcp-server in the official registry since 28 October 2025 under a DNS-verified namespace, still at 0.1.0 (15). No package to assess for a hosted server; NerdGraph has official clients (5). 30 + 20 + 10 + 15 + 5 = 80." }, "scores": { "a": 96, "b": 80 } }, { "by": 15, "category": "ergonomics", "leads": "grafana-mcp-server", "name": "Agent ergonomics", "reasons": { "a": "79 tools load by default and 119 with every category on, counted from the registration code in `cmd/mcp-grafana/main.go` and `tools/*.go` at tag v2.0.2, with no tool added or removed by v2.1.1. That is 5 of 25 by count, plus 9 for `--enabled-tools`, per-category `--disable-*` flags, 12 opt-in categories and `--disable-write`, which leaves 62 (14). `limit` and `page` on searches, `get_dashboard_summary`, JSONPath reads through `get_dashboard_property`, a jq filter on `grafana_api_request`, and a 100-line default on `query_loki_logs` with an optional byte and time-range guardrail (18 of 20). Unknown argument keys are rejected with the valid ones listed, empty results carry likely causes and next steps, and TraceQL errors return correction hints. No documented error list (16 of 20). In source every default tool sets `readOnlyHint` and `destructiveHint` (60 read-only, 9 marked destructive), and 73 of 79 also set `idempotentHint`. The six that leave it unset are writes, for which the protocol default is false. No idempotency keys on creates (17 of 20). Most parameters are optional in the source structs. The Go module is the only library, with a Python wrapper for install (9 of 15).", "b": "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." }, "scores": { "a": 74, "b": 59 } }, { "by": 9, "category": "security", "leads": "new-relic", "name": "Security \u0026 auth", "reasons": { "a": "The server holds a Grafana service account token, which Grafana RBAC can scope by action and resource and which can be revoked. `GRAFANA_SERVICE_ACCOUNT_TOKEN_FILE` is re-read on each request for rotation. Username and password and a deprecated API key also work. The open-source server has no OAuth, and no secret travels in a URL (25 of 30). `--disable-write`, `--disable-query`, per-category flags, Loki enforced matchers and a per-tool RBAC table support least privilege. Writes are on by default, the default set includes `grafana_api_request` for any API path, and nothing asks for confirmation (14 of 20). Log lines, dashboards and annotations reach the model as stored. No injection guidance was found in the README or docs, and issue #680 on the subject has been open since 24 March 2026 (2 of 15). OpenTelemetry traces, metrics and logs per tool call and slow-request logging, with arguments left out of spans unless `--include-args-in-spans` is set (10 of 15). Grafana Labs runs a disclosure programme on Intigriti without bounties, lists ISO 27001 and SOC 2 Type 2, and publishes advisories on grafana.com, two of them for this server (CVE-2026-15583 on 15 July and CVE-2026-19516 on 11 August 2026). The repository has no SECURITY.md and grafana.com has no security.txt (16 of 20).", "b": "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." }, "scores": { "a": 67, "b": 76 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Grafana Labs", "b": "New Relic, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://mcp.newrelic.com/mcp/", "name": "Hosted endpoint" }, { "a": "stdio, SSE (legacy), Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "none", "name": "Licence" }, { "a": "119", "b": "40", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.grafana/mcp-grafana", "b": "com.newrelic/mcp-server", "name": "MCP registry" }, { "a": "2026-10-20", "b": "2026-10-28", "name": "Last release" }, { "a": "no document linked", "b": "2022-11-08", "name": "Terms last updated" }, { "a": "2026-07-10", "b": "2026-09-14", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "3.5k stars, 152k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Grafana MCP Server scores 71 (BB) on agent readiness against New Relic MCP Server's 61 (C), and leads in 5 of 7 scored categories. New Relic MCP Server leads on security \u0026 auth.", "question": "Which is better for AI agents, Grafana MCP Server or New Relic MCP Server?" }, { "answer": "Grafana MCP Server takes an API key or an OAuth sign-in. New Relic MCP Server uses an OAuth sign-in.", "question": "Do Grafana MCP Server and New Relic MCP Server need an API key?" }, { "answer": "Grafana MCP Server runs on your own machine, with no hosted endpoint listed. New Relic MCP Server has a hosted endpoint at https://mcp.newrelic.com/mcp/.", "question": "Can an agent call Grafana MCP Server and New Relic MCP Server without installing anything?" }, { "answer": "Grafana MCP Server is open source (Apache-2.0). No open-source release is listed for New Relic MCP Server.", "question": "Are Grafana MCP Server and New Relic MCP Server open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 91 against 60", "Schema \u0026 documentation, 81 against 51", "Agent ergonomics, 74 against 59", "Payments \u0026 pricing, 60 against 30", "Maintenance \u0026 community, 96 against 80" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine", "Open source" ], "goodFor": "Teams on Grafana, self-managed or Cloud, that want an agent to read dashboards and query Prometheus, Loki, Tempo and Pyroscope, and to work with alert rules, incidents and OnCall.", "slug": "grafana-mcp-server", "watchFor": "The default set is 79 tools, and 119 with every category on, counted from the registration code in source" }, { "aheadOn": [ "Security \u0026 auth, 76 against 67" ], "also": [ "A hosted endpoint, with nothing to install", "Free to start without a card", "No incidents deducted, where Grafana MCP Server loses 7 points for them" ], "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" } ], "history": { "grafana-mcp-server": [ { "causes": [ "event" ], "date": "2026-11-01", "delta": -3, "from": 74, "fromGrade": "BB", "to": 71, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-28", "delta": 0.1, "from": 73.9, "fromGrade": "BB", "to": 74, "toGrade": "BB" }, { "causes": [ "product", "evidence", "event" ], "date": "2026-10-17", "delta": -0.6, "from": 74.5, "fromGrade": "BB", "to": 73.9, "toGrade": "BB" } ], "new-relic": null }, "job": { "capability": "observability.metrics", "name": "Metrics and monitoring" }, "others": [ { "json": "https://www.anchorterminal.com/compare/causely-vs-grafana-mcp-server.json", "title": "Causely MCP server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/causely-vs-grafana-mcp-server" }, { "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/grafana-mcp-server-vs-incident-io.json", "title": "Grafana MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-pagerduty-mcp.json", "title": "Grafana MCP Server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp.json", "title": "Grafana MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp" }, { "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-grafana-mcp-server.json", "title": "Axiom MCP Server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server" }, { "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-grafana-mcp-server.json", "title": "Better Stack vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server" }, { "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-grafana-mcp-server.json", "title": "Datadog MCP Server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server" }, { "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-honeycomb-mcp.json", "title": "Grafana MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.json", "title": "New Relic MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/new-relic-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-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": 31, "edge": "grafana-mcp-server", "grafana-mcp-server": 91, "key": "reliability", "name": "Reliability", "new-relic": 60, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 30, "edge": "grafana-mcp-server", "grafana-mcp-server": 81, "key": "schema", "name": "Schema \u0026 documentation", "new-relic": 51, "weight": 13 }, { "by": 15, "edge": "grafana-mcp-server", "grafana-mcp-server": 74, "key": "ergonomics", "name": "Agent ergonomics", "new-relic": 59, "weight": 13 }, { "by": 9, "edge": "new-relic", "grafana-mcp-server": 67, "key": "security", "name": "Security \u0026 auth", "new-relic": 76, "weight": 14 }, { "by": 30, "edge": "grafana-mcp-server", "grafana-mcp-server": 60, "key": "payments", "name": "Payments \u0026 pricing", "new-relic": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "edge": "grafana-mcp-server", "grafana-mcp-server": 96, "key": "maintenance", "name": "Maintenance \u0026 community", "new-relic": 80, "weight": 7 }, { "by": 1, "edge": "new-relic", "grafana-mcp-server": 80, "key": "transparency", "name": "Transparency \u0026 trust", "new-relic": 81, "weight": 7 } ], "summary": "Grafana MCP Server scores 71 (BB) on agent readiness against New Relic MCP Server's 61 (C), and leads in 5 of 7 scored categories. New Relic MCP Server leads on security \u0026 auth. Both do metrics and monitoring.", "tasks": null, "tutorials": [], "verdicts": { "grafana-mcp-server": "Every default tool declares typed inputs and read-only and destructive annotations in source, and `--disable-write` cuts the default 79 tools to 62. Writes and a general `grafana_api_request` tool are on by default, the default list is long at 79 tools, and two `X-Grafana-URL` flaws, one rated critical, were fixed in July and August 2026.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic", "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.min.md" }, "markdown": "Grafana MCP Server scores 71 (BB) on agent readiness against New Relic MCP Server's 61 (C), and leads in 5 of 7 scored categories. New Relic MCP Server leads on security \u0026 auth. Both do metrics and monitoring.\n\n- Grafana MCP Server: grade BB, 71/100, rank #154 of 1349. Markdown https://www.anchorterminal.com/tools/grafana-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/grafana-mcp-server.json\n- New Relic MCP Server: grade C, 61/100, rank #567 of 1349. Markdown https://www.anchorterminal.com/tools/new-relic.md · JSON https://www.anchorterminal.com/api/v1/tools/new-relic.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### Grafana MCP Server (BB)\n\nGood for: Teams on Grafana, self-managed or Cloud, that want an agent to read dashboards and query Prometheus, Loki, Tempo and Pyroscope, and to work with alert rules, incidents and OnCall.\n\nAhead on:\n- Reliability, 91 against 60\n- Schema \u0026 documentation, 81 against 51\n- Agent ergonomics, 74 against 59\n- Payments \u0026 pricing, 60 against 30\n- Maintenance \u0026 community, 96 against 80\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Open source\n\nWatch for: The default set is 79 tools, and 119 with every category on, counted from the registration code in source\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- Security \u0026 auth, 76 against 67\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n- No incidents deducted, where Grafana MCP Server loses 7 points for them\n\nWatch for: Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters\n\n\n## Why the edge\n\n### Reliability: Grafana MCP Server +31\n\n- Grafana MCP Server (91): Scored as local software, since the owner runs it over stdio, SSE or streamable HTTP. Official PyPI package `mcp-grafana` (a wheel that carries the Go binary, Python 3.10 or later), a Docker image, release binaries and a Helm chart, with Grafana 9.0 or later stated as the requirement (20). Unit, integration and end-to-end workflows all concluded in success on main on 8 October 2026, per the 8 October check, not re-read on 1 November (25). Per the 8 October check, not re-read on 1 November, 54 open issues, none labelled bug, and 38 closed in the 30 days before that check. Three bug reports remained open from July and August (#992 `run_panel_query` 422, #1005 `grafana_api_request` 500 on plugin resources, #1049 a dropped table row in `get_panel_image`), each with replies. A stale issue and pull request workflow was added on 27 October (19 of 25). The changelog follows Keep a Changelog and semantic versioning and labels breaking changes, and 1.6.2 announced that 2.0 came next. Patch release 1.4.1 carried a breaking parameter change on the Sift tools, 2.0.0 followed 1.0.0 by two months, and minor release 2.1.0 on 20 October changed the output of `list_users_by_org`, labelled on the day (12 of 15). Version 2.1.1, the latest release on 1 November (15).\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\n### Schema \u0026 documentation: Grafana MCP Server +30\n\n- Grafana MCP Server (81): Read from source at tag v2.0.2, without running it, and unchanged in count at v2.1.1. All 79 default tools build their JSON Schema input by reflection from a typed Go parameter struct, and `buildInputSchema` in `tools.go` sets `additionalProperties` to false. No tool sets an output schema, which issue #1278 asks for (23 of 25). grafana.com serves llms.txt and a Markdown form of every docs page, the MCP pages included (10). Descriptions state purpose and inputs. Version 2.0.2 removed model directives and references to other tools from descriptions to meet connector directory rules, so guidance on when to use a tool is thinner than it was (14 of 20). Nearly every parameter field in the source structs carries a description tag, but few declare an enum. Values such as `queryType` ('range' or 'instant') and incident `status` are named in prose, and some parameters are free-form objects (9 of 15). The docs have client configuration examples, task guides and a troubleshooting page, and empty results return hints. No catalogue of error responses was found (10 of 15). Semantic versions, tagged releases and a dated changelog (15).\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\n### Payments \u0026 pricing: Grafana MCP Server +30\n\n- Grafana MCP Server (60): Read with the self-hosted rule. The server is free under Apache-2.0 and needs no signup of its own, so 20 + 20 + 20. No x402, MPP or L402 (0). It needs a Grafana instance, which can be the free open-source Grafana. Grafana Cloud prices were not checked. The separate hosted Grafana Cloud MCP server counts towards Grafana Assistant usage and is not what this listing grades.\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\n### Maintenance \u0026 community: Grafana MCP Server +16\n\n- Grafana MCP Server (96): v2.1.1 tagged on 20 October 2026, 12 days before the check, after v2.1.0 the same day, with commits on main to 31 October (30). 17 tagged releases from 1.1.0 on 10 August to 2.1.1 in the 90 days to 1 November (20). Per the 8 October check, not re-read on 1 November, 38 issues closed in the 30 days before that check against 54 open and 22 open pull requests, and several feature requests from March and April without a reply (21 of 25). Listed in the official MCP registry as `io.github.grafana/mcp-grafana`, a GitHub-verified namespace, with v2.1.1 published on 20 October and marked latest (15). Renovate, a Docker image scan workflow, cosign signing with SPDX SBOMs for releases from 2.1.0, and Go toolchain and dependency bumps for CVEs on 21 and 28 October (10).\n- New Relic MCP Server (80): Read as a closed service. The what's-new feed and press releases record changes through October 2026, the latest on 28 October (Change Tracking in GitHub Copilot), and docs llms.txt was regenerated on 3 November (30). More than three dated entries in 90 days, among them the Ground Truth CLI on 6 October, the CEO appointment on 1 October, OpenTelemetry AI monitoring in August and the ISO 42001 announcement (20). A support portal, in-app support and a community forum; the skills hub repository on GitHub, whose issue replies couldn't be read (10 of 15). com.newrelic/mcp-server in the official registry since 28 October 2025 under a DNS-verified namespace, still at 0.1.0 (15). No package to assess for a hosted server; NerdGraph has official clients (5). 30 + 20 + 10 + 15 + 5 = 80.\n\n### Agent ergonomics: Grafana MCP Server +15\n\n- Grafana MCP Server (74): 79 tools load by default and 119 with every category on, counted from the registration code in `cmd/mcp-grafana/main.go` and `tools/*.go` at tag v2.0.2, with no tool added or removed by v2.1.1. That is 5 of 25 by count, plus 9 for `--enabled-tools`, per-category `--disable-*` flags, 12 opt-in categories and `--disable-write`, which leaves 62 (14). `limit` and `page` on searches, `get_dashboard_summary`, JSONPath reads through `get_dashboard_property`, a jq filter on `grafana_api_request`, and a 100-line default on `query_loki_logs` with an optional byte and time-range guardrail (18 of 20). Unknown argument keys are rejected with the valid ones listed, empty results carry likely causes and next steps, and TraceQL errors return correction hints. No documented error list (16 of 20). In source every default tool sets `readOnlyHint` and `destructiveHint` (60 read-only, 9 marked destructive), and 73 of 79 also set `idempotentHint`. The six that leave it unset are writes, for which the protocol default is false. No idempotency keys on creates (17 of 20). Most parameters are optional in the source structs. The Go module is the only library, with a Python wrapper for install (9 of 15).\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\n### Security \u0026 auth: New Relic MCP Server +9\n\n- Grafana MCP Server (67): The server holds a Grafana service account token, which Grafana RBAC can scope by action and resource and which can be revoked. `GRAFANA_SERVICE_ACCOUNT_TOKEN_FILE` is re-read on each request for rotation. Username and password and a deprecated API key also work. The open-source server has no OAuth, and no secret travels in a URL (25 of 30). `--disable-write`, `--disable-query`, per-category flags, Loki enforced matchers and a per-tool RBAC table support least privilege. Writes are on by default, the default set includes `grafana_api_request` for any API path, and nothing asks for confirmation (14 of 20). Log lines, dashboards and annotations reach the model as stored. No injection guidance was found in the README or docs, and issue #680 on the subject has been open since 24 March 2026 (2 of 15). OpenTelemetry traces, metrics and logs per tool call and slow-request logging, with arguments left out of spans unless `--include-args-in-spans` is set (10 of 15). Grafana Labs runs a disclosure programme on Intigriti without bounties, lists ISO 27001 and SOC 2 Type 2, and publishes advisories on grafana.com, two of them for this server (CVE-2026-15583 on 15 July and CVE-2026-19516 on 11 August 2026). The repository has no SECURITY.md and grafana.com has no security.txt (16 of 20).\n- 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.\n\n## Score by category\n\n| Category | Weight | Grafana MCP Server | New Relic MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 91 | 60 | Grafana MCP Server +31 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 81 | 51 | Grafana MCP Server +30 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 59 | Grafana MCP Server +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 67 | 76 | New Relic MCP Server +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 30 | Grafana MCP Server +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 96 | 80 | Grafana MCP Server +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 80 | 81 | New Relic MCP Server +1 |\n| Negative events | ≤15 | -7 | 0 | |\n| **Total** | | **71 · BB** | **61 · C** | |\n\n## Facts side by side\n\n| Fact | Grafana MCP Server | New Relic MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Grafana Labs | New Relic, Inc. |\n| Hosted endpoint | no (local only) | `https://mcp.newrelic.com/mcp/` |\n| Transports | stdio, SSE (legacy), Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 | none |\n| Tools exposed | 119 | 40 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.grafana/mcp-grafana` | `com.newrelic/mcp-server` |\n| Last release | 2026-10-20 | 2026-10-28 |\n| Terms last updated | no document linked | 2022-11-08 |\n| Privacy policy last updated | 2026-07-10 | 2026-09-14 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | yes |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | 3.5k stars, 152k PyPI/wk | none |\n| Agent reviews | 3/5 (4) | none |\n\n## How the scores have moved\n\n### Grafana MCP Server\n\n- -3.0 on 1 November 2026: negative event\n- +0.1 on 28 October 2026: checklist\n- -0.6 on 17 October 2026: product, new evidence, negative event\n\n### New Relic MCP Server\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Grafana MCP Server.** Every default tool declares typed inputs and read-only and destructive annotations in source, and `--disable-write` cuts the default 79 tools to 62. Writes and a general `grafana_api_request` tool are on by default, the default list is long at 79 tools, and two `X-Grafana-URL` flaws, one rated critical, were fixed in July and August 2026.\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## Before you call either\n\n### Grafana MCP Server\n\n1. Start with `--disable-write` unless the task needs writes, and add `--disable-api` to remove `grafana_api_request`\n2. Pass `--enabled-tools` with only the categories needed. The default list loads 79 tools\n3. Use `get_dashboard_summary` or `get_dashboard_property` with a JSONPath before `get_dashboard_by_uid`, which returns the whole dashboard JSON\n4. Set `GRAFANA_USAGE_STATS=disabled` or `DO_NOT_TRACK=1` to stop the four-hourly usage report to stats.grafana.org\n5. Use streamable HTTP, not SSE, when each caller needs its own token or organisation, and set `--server-auth-token` on any non-loopback address\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## Questions\n\n### Which is better for AI agents, Grafana MCP Server or New Relic MCP Server?\n\nGrafana MCP Server scores 71 (BB) on agent readiness against New Relic MCP Server's 61 (C), and leads in 5 of 7 scored categories. New Relic MCP Server leads on security \u0026 auth.\n\n### Do Grafana MCP Server and New Relic MCP Server need an API key?\n\nGrafana MCP Server takes an API key or an OAuth sign-in. New Relic MCP Server uses an OAuth sign-in.\n\n### Can an agent call Grafana MCP Server and New Relic MCP Server without installing anything?\n\nGrafana MCP Server runs on your own machine, with no hosted endpoint listed. New Relic MCP Server has a hosted endpoint at https://mcp.newrelic.com/mcp/.\n\n### Are Grafana MCP Server and New Relic MCP Server open source?\n\nGrafana MCP Server is open source (Apache-2.0). No open-source release is listed for New Relic MCP Server.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.json, and with the fewest tokens: https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"grafana-mcp-server\", \"b\": \"new-relic\"}`. From a terminal: `anchor compare grafana-mcp-server new-relic`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/grafana-mcp-server.json and https://www.anchorterminal.com/api/v1/tools/new-relic.json\n\n## Other comparisons with Grafana MCP Server or New Relic MCP Server\n\n- [Causely MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/causely-vs-grafana-mcp-server.md)\n- [Causely MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/causely-vs-new-relic.md)\n- [Grafana MCP Server vs incident.io API](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io.md)\n- [Grafana MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-pagerduty-mcp.md)\n- [Grafana MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp.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 Grafana MCP Server](https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.md)\n- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md)\n- [Better Stack vs Grafana MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server.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 Grafana MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.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 Honeycomb MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.md)\n- [New Relic MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/new-relic-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 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": "Grafana MCP Server vs New Relic MCP Server", "url": "" } ], "description": "Grafana scores 71 (BB) to New Relic's 61 (C) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grafana MCP Server BB 71", "New Relic MCP Server C 61", "scores" ], "h1": "Grafana MCP Server vs New Relic MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/grafana-mcp-server-vs-new-relic", "published": "2026-10-01", "section": "tools", "title": "Grafana vs New Relic for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic" }, "tokens": { "markdown": 5700, "slim": 3830 }, "version": 1 }