{
  "data": {
    "a": {
      "slug": "grafana-mcp-server",
      "name": "Grafana MCP Server",
      "vendor": "Grafana Labs",
      "vendorUrl": "https://grafana.com/docs/grafana/latest/developer-resources/mcp/",
      "company": "grafana.com",
      "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": 74.8,
        "grade": "BB",
        "agentReady": true,
        "rank": 128,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 1,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 74,
          "maintenance": 96,
          "payments": 90,
          "reliability": 91,
          "schema": 81,
          "security": 67,
          "transparency": 80
        },
        "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": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 74.8
          }
        ],
        "editorialScores": {
          "ergonomics": 74,
          "maintenance": 96,
          "payments": 90,
          "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-13",
          "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": {
        "setupChecked": true,
        "complianceChecked": true,
        "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.3.0",
            "released": "2026-11-10",
            "seenAt": "2026-11-18T17:52:54.168085112Z"
          },
          {
            "registry": "mcp-registry",
            "name": "io.github.grafana/mcp-grafana",
            "version": "v2.3.0",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          },
          {
            "registry": "pypi",
            "name": "mcp-grafana",
            "version": "2.2.0",
            "released": "2026-11-02",
            "seenAt": "2026-11-18T17:52:53.981468242Z"
          }
        ],
        "githubStars": 3678,
        "pypiWeekly": 89444,
        "securityTxt": {
          "url": "https://grafana.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2029-12-31T13:26:11Z",
          "checkedAt": "2026-11-18T16:30:16.965274732Z"
        },
        "llmsTxt": {
          "url": "https://grafana.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:14:34.741035025Z"
        },
        "domain": {
          "domain": "grafana.com",
          "registered": "2014-05-27",
          "source": "https://rdap.verisign.com/com/v1/domain/grafana.com",
          "checkedAt": "2026-11-15T15:30:31.607739268Z"
        },
        "pages": [
          {
            "url": "https://raw.githubusercontent.com/grafana/mcp-grafana/main/CHANGELOG.md",
            "kind": "deprecations",
            "status": 304,
            "checkedAt": "2026-11-18T21:55:30.69886645Z",
            "changedAt": "2026-11-11T17:12:34.506058608Z",
            "fingerprint": "7a3a8d93a719"
          },
          {
            "url": "https://grafana.com/legal/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:44:28.373852971Z",
            "changedAt": "2026-11-10T16:21:33.331222319Z",
            "fingerprint": "d8e6a4a9a9bc"
          }
        ],
        "github": {
          "repo": "grafana/mcp-grafana",
          "checkedAt": "2026-11-16T12:05:00.082761882Z",
          "stars": 3671,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-16T11:32:31Z",
          "openIssues": 71,
          "openPRs": 19,
          "issuesOpened90d": 138,
          "issuesClosed90d": 144,
          "prsMerged90d": 341,
          "ci": {
            "branch": "main",
            "runs": 50,
            "success": 45,
            "failure": 5,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-11-16T11:40:17Z"
          },
          "replies": {
            "sampled": 25,
            "unanswered": 7,
            "medianDays": 0.1
          }
        },
        "updatedAt": "2026-11-18T22:45:57.054523297Z"
      }
    },
    "answer": "Grafana MCP Server scores 74.8 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth.",
    "b": {
      "slug": "neat-pulse-mcp",
      "name": "Neat Pulse MCP",
      "vendor": "Neat",
      "vendorUrl": "https://neat.no",
      "company": "neat.no",
      "kind": "mcp",
      "category": "observability",
      "summary": "Neat Pulse MCP is Neat's local MCP server for Neat Pulse, the cloud service that manages Neat's meeting-room video devices. Agents list devices and rooms, read sensor data, reboot devices and change room set-up, for paid Pulse customers.",
      "url": "https://www.anchorterminal.com/tools/neat-pulse-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json",
      "dns": "neat-pulse-mcp.grade.anchorterminal.com",
      "transports": [
        "stdio"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@neat-no/pulse-mcp"
        }
      ],
      "auth": "api-key",
      "authNotes": "A Neat Pulse API token in `PULSE_API_TOKEN`, with the organisation ID in `PULSE_ORG_ID`. Only an Owner of the Pulse organisation can create tokens, in the portal under Settings \u003e API Keys. A token takes either the Read scope or all scopes, is shown once, can be revoked, and the Pulse API has a key-rotation endpoint. The token's name appears in Pulse's audit logs.",
      "pricing": "byo-plan",
      "pricingNotes": "Included at no extra cost with a paid Neat Pulse Plus or Pro plan, and every device in the organisation must be on a paid plan. Plus and Pro are sold through resellers, with no public price. The free Pulse Starter plan doesn't include MCP or API access.",
      "priceSummary": "Your plan",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on neat.no, support.neat.no or the Pulse API reference, read on 2026-11-18. Pulse plans are bought through resellers.",
        "endpoints": []
      },
      "toolCount": 30,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://support.neat.no/article/neat-pulse-mcp-server/",
      "capabilities": [
        "observability.metrics"
      ],
      "tags": [
        "mcp",
        "stdio",
        "npm",
        "node",
        "api-key",
        "audit-log",
        "read-only-mode",
        "hardware",
        "meeting-rooms",
        "paid-plan",
        "iso-27001"
      ],
      "lastRelease": "2026-11-17",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 45.8,
        "grade": "E",
        "agentReady": false,
        "rank": 1268,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 43,
          "maintenance": 59,
          "payments": 0,
          "reliability": 35,
          "schema": 49,
          "security": 79,
          "transparency": 56
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page.",
        "bestFor": "IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.",
        "strengths": [
          "A Pulse API token can be limited to the Read scope, which the docs say stops the server rebooting, deleting, creating or updating anything",
          "Every action taken through the MCP server is recorded in Pulse's audit logs under the token's name, and `list_audit_logs` reads them",
          "security.txt, a vulnerability reporting policy, public security advisories through 2026 and an ISO 27001 statement on Neat's support site",
          "Version 1.1.0 on 17 November 2026, four releases since 17 September 2026, and setup steps for seven MCP clients",
          "A data model guide served as an MCP resource and a tool, with IDs, hierarchy and which actions can't be undone"
        ],
        "weaknesses": [
          "Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent",
          "No public source repository, licence, changelog or status page found",
          "Irreversible tools (delete room, delete device, reboot, reset enrolment code) rely on the assistant asking first. No server-side confirmation was found",
          "No rate limits or 429 handling documented for the server or the Pulse API",
          "Runs only in clients that can start local programs, and needs Node.js 20 or later"
        ],
        "agentNotes": [
          "Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices",
          "Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room",
          "Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy",
          "If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`",
          "If a call returns 401, ask the person for a new Pulse token. If it returns 404, check `PULSE_ORG_ID`"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 45.8
          }
        ],
        "editorialScores": {
          "ergonomics": 43,
          "maintenance": 59,
          "payments": 0,
          "reliability": 35,
          "schema": 49,
          "security": 79,
          "transparency": 47
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npx -y @neat-no/pulse-mcp@latest   # needs PULSE_API_TOKEN and PULSE_ORG_ID in the environment",
        "claudeCode": "claude mcp add neat-pulse -s user -e PULSE_API_TOKEN=YOUR_PULSE_TOKEN -e PULSE_ORG_ID=YOUR_ORG_ID -- npx -y @neat-no/pulse-mcp@latest",
        "config": {
          "mcpServers": {
            "neat-pulse": {
              "args": [
                "-y",
                "@neat-no/pulse-mcp@latest"
              ],
              "command": "npx",
              "env": {
                "PULSE_API_TOKEN": "YOUR_PULSE_TOKEN",
                "PULSE_ORG_ID": "YOUR_ORG_ID"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/observability.metrics",
        "tool": "https://letme.dev/neat-pulse-mcp"
      },
      "area": "developer",
      "provenance": {
        "legalEntity": "Neatframe Limited",
        "domain": "neat.no",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://neat.no/neat-pulse-terms-and-conditions/",
        "privacy": "https://neat.no/privacy-policy/",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "valid",
        "checked": "2026-11-18",
        "notes": [
          "The Neat Pulse Agreement (last updated 26 March 2025) is between Neatframe Ltd. and the customer, and the privacy notice (13 July 2026) is Neatframe Limited's. The company page says Neat is based in Oslo.",
          "neat.no/robots.txt allows ClaudeBot and anthropic-ai outside account, cart, checkout and admin paths, with a crawl delay of 10 seconds. support.neat.no, api.pulse.neat.no and registry.npmjs.org allow all agents.",
          "neat.no/.well-known/security.txt gives security@neat.no, expires 7 August 2027 and links the vulnerability reporting policy on support.neat.no.",
          "No status page for Neat Pulse was linked from any page read. The MCP server calls the Pulse API at api.pulse.neat.no."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.json"
    },
    "edges": [
      {
        "by": 90,
        "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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.",
          "b": "No payment protocol (0). Pulse Plus and Pro are sold through resellers and the Pulse Agreement says the price is on the reseller's invoice, so no price is public (0). The free Starter plan excludes MCP and API access (0). A person must buy a plan and an Owner must create the token in the portal (0). 0 + 0 + 0 + 0 = 0."
        },
        "scores": {
          "a": 90,
          "b": 0
        }
      },
      {
        "by": 56,
        "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": "Read with the local-software lines, since the server is an npm package the client starts on the person's machine. Official npm package with Node.js 20 or later stated (20). No public repository, so no CI or test suite could be seen (0). No public issue tracker (0). Versions follow semver on npm, but no changelog was found (0). Version 1.1.0 and generally available since 18 November 2026 (15). The Pulse cloud API it relays to has no status page linked from the pages read. 20 + 0 + 0 + 0 + 15 = 35."
        },
        "scores": {
          "a": 91,
          "b": 35
        }
      },
      {
        "by": 37,
        "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": "1.1.0 on 17 November 2026 (30). 0.2.2, 0.2.3, 1.0.0 and 1.1.0 since 17 September 2026 (20). Closed source with no public changelog. Paid plans include priority email support with an SLA per the Pulse Agreement, and the setup guide was updated on 17 November (5). Not in the official MCP registry, by a search for Neat (0). Current MCP SDK and zod versions in the npm metadata, with no visible CI (4). 30 + 20 + 5 + 0 + 4 = 59."
        },
        "scores": {
          "a": 96,
          "b": 59
        }
      },
      {
        "by": 32,
        "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": "The npm metadata lists zod and the MCP SDK, but the tool schemas themselves weren't read, since the source isn't public and the package wasn't installed. Partial credit for a contract that exists but isn't published, as for Causely (12). No llms.txt found. The README points agents to an `llms-install.md` in the package, which wasn't read (5). The support reference describes every tool, what it returns and which changes can't be undone, and the domain guide explains the data model (14). Inputs are described only in passing, such as `assign_room_profile` (5). Example prompts, a troubleshooting table for 401, 404 and npx errors, and the `profile_confirmation_needed` status (8). Semver versions on npm and dated support articles, but no changelog (5). 12 + 5 + 14 + 5 + 8 + 5 = 49."
        },
        "scores": {
          "a": 81,
          "b": 49
        }
      },
      {
        "by": 31,
        "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": "30 tools, in the 11 to 30 band, with no toolsets or read-only subset that hides write tools that we found (15). `list_audit_logs` pages between dates, but `list_devices` and `list_rooms` return everything in the organisation (6). Documented 401 and 404 causes, and `move_device` returns a status asking for confirmation instead of failing (10). Annotations couldn't be read. The docs ask the assistant to confirm reboots and messages, and no idempotency is described (5). Two environment variables to start. The Pulse API reference shows generated client snippets, but no official SDK package was found (7). 15 + 6 + 10 + 5 + 7 = 43."
        },
        "scores": {
          "a": 74,
          "b": 43
        }
      },
      {
        "by": 24,
        "category": "transparency",
        "leads": "grafana-mcp-server",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Apache-2.0 (30). Local software that talks to the configured Grafana. A docs page lists every field in the usage report, the destination, and the region and network name the receiving service adds, and the Grafana Labs privacy policy (last updated 10 July 2026) covers usage statistics from its open-source software. No retention period for the reports was found (24 of 30). No deprecation policy. Notices come without dates, such as `GRAFANA_API_KEY` to be removed 'in a future version', and the Sift tools were marked deprecated before 2.0.0 removed them (10 of 20). Usage statistics are documented with three opt-outs and a `log` mode that prints the report without sending it. They arrived off by default in 1.5.0 on 17 September 2026 and were switched on by default in 2.0.0, noted in the changelog (17 of 20).",
          "b": "Closed source, and the npm package carries no licence field. The Pulse Agreement covers the service clearly (12). A privacy notice of 13 July 2026, a DPA, a GDPR page and a data residency article, with retention described only as long as necessary (18). The Pulse Agreement supports the current and prior major release, and nothing covers the MCP server's deprecation (3). Pulse data stays in one Azure region per chosen zone, mapped by name. No subprocessor list was read (14). 12 + 18 + 3 + 14 = 47."
        },
        "scores": {
          "a": 80,
          "b": 56
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Grafana Labs",
        "b": "Neat",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "stdio, SSE (legacy), Streamable HTTP",
        "b": "stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Free",
        "b": "Your plan",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Apache-2.0",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "119",
        "b": "30",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "io.github.grafana/mcp-grafana",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-20",
        "b": "2026-11-17",
        "name": "Last release"
      },
      {
        "a": "no document linked",
        "b": "2025-03-26",
        "name": "Terms last updated"
      },
      {
        "a": "2026-07-10",
        "b": "2026-07-13",
        "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": "not found in the text",
        "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": "yes",
        "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 74.8 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth.",
        "question": "Which is better for AI agents, Grafana MCP Server or Neat Pulse MCP?"
      },
      {
        "answer": "Grafana MCP Server takes an API key or an OAuth sign-in. Neat Pulse MCP needs an API key.",
        "question": "Do Grafana MCP Server and Neat Pulse MCP need an API key?"
      },
      {
        "answer": "Grafana MCP Server runs on your own machine, with no hosted endpoint listed. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.",
        "question": "Can an agent call Grafana MCP Server and Neat Pulse MCP without installing anything?"
      },
      {
        "answer": "Grafana MCP Server is open source (Apache-2.0). No open-source release is listed for Neat Pulse MCP.",
        "question": "Are Grafana MCP Server and Neat Pulse MCP open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 91 against 35",
          "Schema \u0026 documentation, 81 against 49",
          "Agent ergonomics, 74 against 43",
          "Payments \u0026 pricing, 90 against 0",
          "Maintenance \u0026 community, 96 against 59",
          "Transparency \u0026 trust, 80 against 56"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "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, 79 against 67"
        ],
        "also": [
          "No incidents deducted, where Grafana MCP Server loses 7 points for them"
        ],
        "goodFor": "IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.",
        "slug": "neat-pulse-mcp",
        "watchFor": "Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent"
      }
    ],
    "history": {
      "grafana-mcp-server": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 3.8,
          "from": 71,
          "fromGrade": "BB",
          "to": 74.8,
          "toGrade": "BB"
        },
        {
          "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"
        }
      ],
      "neat-pulse-mcp": 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/cronitor-mcp-vs-grafana-mcp-server.json",
        "title": "Cronitor MCP server vs Grafana MCP Server",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server"
      },
      {
        "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/axiom-vs-neat-pulse-mcp.json",
        "title": "Axiom MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.json",
        "title": "Better Stack vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.json",
        "title": "Causely MCP server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.json",
        "title": "Cronitor MCP server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp"
      },
      {
        "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-neat-pulse-mcp.json",
        "title": "Datadog MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp"
      },
      {
        "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/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/honeycomb-mcp-vs-neat-pulse-mcp.json",
        "title": "Honeycomb MCP vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.json",
        "title": "Neat Pulse MCP vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic"
      },
      {
        "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/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/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/neat-pulse-mcp-vs-sentry-mcp.json",
        "title": "Neat Pulse MCP vs Sentry MCP",
        "url": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 56,
        "edge": "grafana-mcp-server",
        "grafana-mcp-server": 91,
        "key": "reliability",
        "name": "Reliability",
        "neat-pulse-mcp": 35,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 32,
        "edge": "grafana-mcp-server",
        "grafana-mcp-server": 81,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "neat-pulse-mcp": 49,
        "weight": 13
      },
      {
        "by": 31,
        "edge": "grafana-mcp-server",
        "grafana-mcp-server": 74,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "neat-pulse-mcp": 43,
        "weight": 13
      },
      {
        "by": 12,
        "edge": "neat-pulse-mcp",
        "grafana-mcp-server": 67,
        "key": "security",
        "name": "Security \u0026 auth",
        "neat-pulse-mcp": 79,
        "weight": 14
      },
      {
        "by": 90,
        "edge": "grafana-mcp-server",
        "grafana-mcp-server": 90,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "neat-pulse-mcp": 0,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 37,
        "edge": "grafana-mcp-server",
        "grafana-mcp-server": 96,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "neat-pulse-mcp": 59,
        "weight": 7
      },
      {
        "by": 24,
        "edge": "grafana-mcp-server",
        "grafana-mcp-server": 80,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "neat-pulse-mcp": 56,
        "weight": 7
      }
    ],
    "summary": "Grafana MCP Server scores 74.8 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP 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.",
      "neat-pulse-mcp": "Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp",
    "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.min.md"
  },
  "markdown": "Grafana MCP Server scores 74.8 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth. Both do metrics and monitoring.\n\n- Grafana MCP Server: grade BB, 74.8/100, rank #128 of 1557. Markdown https://www.anchorterminal.com/tools/grafana-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/grafana-mcp-server.json\n- Neat Pulse MCP: grade E, 45.8/100, rank #1268 of 1557. Markdown https://www.anchorterminal.com/tools/neat-pulse-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 68 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 35\n- Schema \u0026 documentation, 81 against 49\n- Agent ergonomics, 74 against 43\n- Payments \u0026 pricing, 90 against 0\n- Maintenance \u0026 community, 96 against 59\n- Transparency \u0026 trust, 80 against 56\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\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### Neat Pulse MCP (E)\n\nGood for: IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.\n\nAhead on:\n- Security \u0026 auth, 79 against 67\n\nAlso in its favour:\n- No incidents deducted, where Grafana MCP Server loses 7 points for them\n\nWatch for: Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Grafana MCP Server +90\n\n- Grafana MCP Server (90): 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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.\n- Neat Pulse MCP (0): No payment protocol (0). Pulse Plus and Pro are sold through resellers and the Pulse Agreement says the price is on the reseller's invoice, so no price is public (0). The free Starter plan excludes MCP and API access (0). A person must buy a plan and an Owner must create the token in the portal (0). 0 + 0 + 0 + 0 = 0.\n\n### Reliability: Grafana MCP Server +56\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- Neat Pulse MCP (35): Read with the local-software lines, since the server is an npm package the client starts on the person's machine. Official npm package with Node.js 20 or later stated (20). No public repository, so no CI or test suite could be seen (0). No public issue tracker (0). Versions follow semver on npm, but no changelog was found (0). Version 1.1.0 and generally available since 18 November 2026 (15). The Pulse cloud API it relays to has no status page linked from the pages read. 20 + 0 + 0 + 0 + 15 = 35.\n\n### Maintenance \u0026 community: Grafana MCP Server +37\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- Neat Pulse MCP (59): 1.1.0 on 17 November 2026 (30). 0.2.2, 0.2.3, 1.0.0 and 1.1.0 since 17 September 2026 (20). Closed source with no public changelog. Paid plans include priority email support with an SLA per the Pulse Agreement, and the setup guide was updated on 17 November (5). Not in the official MCP registry, by a search for Neat (0). Current MCP SDK and zod versions in the npm metadata, with no visible CI (4). 30 + 20 + 5 + 0 + 4 = 59.\n\n### Schema \u0026 documentation: Grafana MCP Server +32\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- Neat Pulse MCP (49): The npm metadata lists zod and the MCP SDK, but the tool schemas themselves weren't read, since the source isn't public and the package wasn't installed. Partial credit for a contract that exists but isn't published, as for Causely (12). No llms.txt found. The README points agents to an `llms-install.md` in the package, which wasn't read (5). The support reference describes every tool, what it returns and which changes can't be undone, and the domain guide explains the data model (14). Inputs are described only in passing, such as `assign_room_profile` (5). Example prompts, a troubleshooting table for 401, 404 and npx errors, and the `profile_confirmation_needed` status (8). Semver versions on npm and dated support articles, but no changelog (5). 12 + 5 + 14 + 5 + 8 + 5 = 49.\n\n### Agent ergonomics: Grafana MCP Server +31\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- Neat Pulse MCP (43): 30 tools, in the 11 to 30 band, with no toolsets or read-only subset that hides write tools that we found (15). `list_audit_logs` pages between dates, but `list_devices` and `list_rooms` return everything in the organisation (6). Documented 401 and 404 causes, and `move_device` returns a status asking for confirmation instead of failing (10). Annotations couldn't be read. The docs ask the assistant to confirm reboots and messages, and no idempotency is described (5). Two environment variables to start. The Pulse API reference shows generated client snippets, but no official SDK package was found (7). 15 + 6 + 10 + 5 + 7 = 43.\n\n### Transparency \u0026 trust: Grafana MCP Server +24\n\n- Grafana MCP Server (80): Apache-2.0 (30). Local software that talks to the configured Grafana. A docs page lists every field in the usage report, the destination, and the region and network name the receiving service adds, and the Grafana Labs privacy policy (last updated 10 July 2026) covers usage statistics from its open-source software. No retention period for the reports was found (24 of 30). No deprecation policy. Notices come without dates, such as `GRAFANA_API_KEY` to be removed 'in a future version', and the Sift tools were marked deprecated before 2.0.0 removed them (10 of 20). Usage statistics are documented with three opt-outs and a `log` mode that prints the report without sending it. They arrived off by default in 1.5.0 on 17 September 2026 and were switched on by default in 2.0.0, noted in the changelog (17 of 20).\n- Neat Pulse MCP (56): Closed source, and the npm package carries no licence field. The Pulse Agreement covers the service clearly (12). A privacy notice of 13 July 2026, a DPA, a GDPR page and a data residency article, with retention described only as long as necessary (18). The Pulse Agreement supports the current and prior major release, and nothing covers the MCP server's deprecation (3). Pulse data stays in one Azure region per chosen zone, mapped by name. No subprocessor list was read (14). 12 + 18 + 3 + 14 = 47.\n\n## Score by category\n\n| Category | Weight | Grafana MCP Server | Neat Pulse MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 91 | 35 | Grafana MCP Server +56 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 81 | 49 | Grafana MCP Server +32 |\n| Agent ergonomics | 13% | 74 | 43 | Grafana MCP Server +31 |\n| Security \u0026 auth | 14% | 67 | 79 | Neat Pulse MCP +12 |\n| Payments \u0026 pricing | 10% | 90 | 0 | Grafana MCP Server +90 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 96 | 59 | Grafana MCP Server +37 |\n| Transparency \u0026 trust | 7% | 80 | 56 | Grafana MCP Server +24 |\n| Negative events | ≤15 | -7 | 0 | |\n| **Total** | | **74.8 · BB** | **45.8 · E** | |\n\n## Facts side by side\n\n| Fact | Grafana MCP Server | Neat Pulse MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Grafana Labs | Neat |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio, SSE (legacy), Streamable HTTP | stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Free | Your plan |\n| x402 | no | no |\n| Licence | Apache-2.0 | none |\n| Tools exposed | 119 | 30 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| MCP registry | `io.github.grafana/mcp-grafana` | not listed |\n| Last release | 2026-10-20 | 2026-11-17 |\n| Terms last updated | no document linked | 2025-03-26 |\n| Privacy policy last updated | 2026-07-10 | 2026-07-13 |\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 | not found in the text |\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 | yes |\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.8 on 13 November 2026: checklist\n- -3.0 on 1 November 2026: negative event\n- +0.1 on 28 October 2026: checklist\n\n### Neat Pulse MCP\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**Neat Pulse MCP.** Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page.\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### Neat Pulse MCP\n\n1. Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices\n2. Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room\n3. Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy\n4. If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`\n5. If a call returns 401, ask the person for a new Pulse token. If it returns 404, check `PULSE_ORG_ID`\n\n## Questions\n\n### Which is better for AI agents, Grafana MCP Server or Neat Pulse MCP?\n\nGrafana MCP Server scores 74.8 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth.\n\n### Do Grafana MCP Server and Neat Pulse MCP need an API key?\n\nGrafana MCP Server takes an API key or an OAuth sign-in. Neat Pulse MCP needs an API key.\n\n### Can an agent call Grafana MCP Server and Neat Pulse MCP without installing anything?\n\nGrafana MCP Server runs on your own machine, with no hosted endpoint listed. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.\n\n### Are Grafana MCP Server and Neat Pulse MCP open source?\n\nGrafana MCP Server is open source (Apache-2.0). No open-source release is listed for Neat Pulse MCP.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"grafana-mcp-server\", \"b\": \"neat-pulse-mcp\"}`. From a terminal: `anchor compare grafana-mcp-server neat-pulse-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/grafana-mcp-server.json and https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json\n\n## Other comparisons with Grafana MCP Server or Neat Pulse MCP\n\n- [Causely MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/causely-vs-grafana-mcp-server.md)\n- [Cronitor MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.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- [Axiom MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.md)\n- [Better Stack vs Neat Pulse MCP](https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.md)\n- [Causely MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.md)\n- [Cronitor MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.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 Neat Pulse MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.md)\n- [Grafana MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.md)\n- [Grafana MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.md)\n- [Honeycomb MCP vs Neat Pulse MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.md)\n- [Neat Pulse MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.md)\n- [Axiom MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.md)\n- [Better Stack vs Grafana MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server.md)\n- [Grafana MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-sentry-mcp.md)\n- [Neat Pulse MCP vs Sentry MCP](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp.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-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "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 Neat Pulse MCP",
        "url": ""
      }
    ],
    "description": "Grafana scores 74.8 (BB) to Neat Pulse MCP's 45.8 (E) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Grafana MCP Server BB 74.8",
      "Neat Pulse MCP E 45.8",
      "scores"
    ],
    "h1": "Grafana MCP Server vs Neat Pulse MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/grafana-mcp-server-vs-neat-pulse-mcp",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Grafana vs Neat Pulse MCP for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp"
  },
  "tokens": {
    "markdown": 5000,
    "slim": 1180
  },
  "version": 1
}
