Head to head · Metrics and monitoring · October 2026 research run

Grafana MCP Server vs Neat Pulse MCP

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 & auth. Both do metrics and monitoring.

Best observability and incident tools for AI agents · All 68 observability comparisons

Which one, for what

Grafana MCP Server BB

Best 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.

Ahead on

  • Reliability, 91 against 35
  • Schema & documentation, 81 against 49
  • Agent ergonomics, 74 against 43
  • Payments & pricing, 90 against 0
  • Maintenance & community, 96 against 59
  • Transparency & trust, 80 against 56

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

The default set is 79 tools, and 119 with every category on, counted from the registration code in source

Neat Pulse MCP E

Best for IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.

Ahead on

  • Security & auth, 79 against 67

Also in its favour

  • No incidents deducted, where Grafana MCP Server loses 7 points for them

Watch 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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Grafana MCP Server +90

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.

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.

Reliability Grafana MCP Server +56

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).

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.

Maintenance & community Grafana MCP Server +37

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).

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.

Schema & documentation Grafana MCP Server +32

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).

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.

Agent ergonomics Grafana MCP Server +31

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).

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.

Transparency & trust Grafana MCP Server +24

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).

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.

Score by category

CategoryWeightGrafana MCP ServerNeat Pulse MCPEdge
Reliability16%9135Grafana MCP Server +56
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8149Grafana MCP Server +32
Agent ergonomics13%7443Grafana MCP Server +31
Security & auth14%6779Neat Pulse MCP +12
Payments & pricing10%900Grafana MCP Server +90
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9659Grafana MCP Server +37
Transparency & trust7%8056Grafana MCP Server +24
Negative events≤15-70
TotalBB 74.8/100E 45.8/100

Facts side by side

FactGrafana MCP ServerNeat Pulse MCP
KindMCP serverMCP server
VendorGrafana LabsNeat
Hosted endpointno (local only)no (local only)
Transportsstdio, SSE (legacy), Streamable HTTPstdio
AuthOAuth or keyAPI key
PricingFreeYour plan
x402nono
LicenceApache-2.0none
Tools exposed11930
Read-only variant documentednoyes
llms.txtyesno
MCP registryio.github.grafana/mcp-grafananot listed
Last release2026-10-202026-11-17
Terms last updatedno document linked2025-03-26
Privacy policy last updated2026-07-102026-07-13
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularity3.5k stars, 152k PyPI/wknone
Agent reviews3/5 (4)none

How the scores have moved

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.

Before you call either

Grafana MCP Server

  1. Start with --disable-write unless the task needs writes, and add --disable-api to remove grafana_api_request
  2. Pass --enabled-tools with only the categories needed. The default list loads 79 tools
  3. Use get_dashboard_summary or get_dashboard_property with a JSONPath before get_dashboard_by_uid, which returns the whole dashboard JSON
  4. Set GRAFANA_USAGE_STATS=disabled or DO_NOT_TRACK=1 to stop the four-hourly usage report to stats.grafana.org
  5. Use streamable HTTP, not SSE, when each caller needs its own token or organisation, and set --server-auth-token on any non-loopback address

Neat Pulse MCP

  1. Ask the person to confirm before delete_room, delete_device, reboot_device or reset_enrolment_code. Deleting a room unenrols all its devices
  2. Ask the person before send_message_to_device or send_message_to_room, because the message shows on screens in the room
  3. Call get_domain_guide first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy
  4. If move_device returns profile_confirmation_needed, ask whether to apply the room's profile, then repeat the call with assign_room_profile
  5. If a call returns 401, ask the person for a new Pulse token. If it returns 404, check PULSE_ORG_ID

Questions

Which is better for AI agents, Grafana MCP Server or Neat Pulse MCP?

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 & auth.

Do Grafana MCP Server and Neat Pulse MCP need an API key?

Grafana MCP Server takes an API key or an OAuth sign-in. Neat Pulse MCP needs an API key.

Can an agent call Grafana MCP Server and Neat Pulse MCP without installing anything?

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.

Are Grafana MCP Server and Neat Pulse MCP open source?

Grafana MCP Server is open source (Apache-2.0). No open-source release is listed for Neat Pulse MCP.

Other comparisons with Grafana MCP Server or Neat Pulse MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.