Head to head · Metrics and monitoring · October 2026 research run
Neat Pulse MCP vs New Relic MCP Server
New Relic MCP Server scores 62.9 (B) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Both do metrics and monitoring.
Best observability and incident tools for AI agents · All 68 observability comparisons
Which one, for what
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.
Also in its favour
- Runs on your own machine
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
Best for Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.
Ahead on
- Reliability, 60 against 35
- Agent ergonomics, 59 against 43
- Payments & pricing, 45 against 0
- Maintenance & community, 80 against 59
- Transparency & trust, 81 against 56
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters
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 New Relic MCP Server +45
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.
New Relic MCP Server 45
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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Reliability New Relic MCP Server +25
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.
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.
Transparency & trust New Relic MCP Server +25
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.
New Relic MCP Server 81
Closed service with clear dated terms (paid 8 November 2022, unpaid 21 October 2021) naming New Relic, Inc. (15). A privacy notice of 14 September 2026, a data retention page with per-namespace periods, a security policy, and the MCP docs' statement that gap-analysis responses aren't stored; the master cloud agreement and the trust centre couldn't be read (22). End-of-life notices with dates (REST API keys, 2025) and a pre-release policy that says preview services can change or end (16). US, EU and JP regions are documented for the server and the platform, but no sub-processor list was found on a readable page (10). 15 + 22 + 16 + 10 = 63.
Maintenance & community New Relic MCP Server +21
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.
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.
Agent ergonomics New Relic MCP Server +16
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.
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.
Score by category
| Category | Weight | Neat Pulse MCP | New Relic MCP Server | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 60 | New Relic MCP Server +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 49 | 51 | New Relic MCP Server +2 |
| Agent ergonomics | 13% | 43 | 59 | New Relic MCP Server +16 |
| Security & auth | 14% | 79 | 76 | Neat Pulse MCP +3 |
| Payments & pricing | 10% | 0 | 45 | New Relic MCP Server +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 59 | 80 | New Relic MCP Server +21 |
| Transparency & trust | 7% | 56 | 81 | New Relic MCP Server +25 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 45.8/100 | B 62.9/100 |
Facts side by side
| Fact | Neat Pulse MCP | New Relic MCP Server |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Neat | New Relic, Inc. |
| Hosted endpoint | no (local only) | https://mcp.newrelic.com/mcp/ |
| Transports | stdio | Streamable HTTP |
| Auth | API key | OAuth |
| Pricing | Your plan | Freemium |
| x402 | no | no |
| Tools exposed | 30 | 40 |
| Read-only variant documented | yes | yes |
| llms.txt | no | yes |
| MCP registry | not listed | com.newrelic/mcp-server |
| Last release | 2026-11-17 | 2026-10-28 |
| Terms last updated | 2025-03-26 | 2022-11-08 |
| Privacy policy last updated | 2026-07-13 | 2026-09-14 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
How the scores have moved
Neat Pulse MCP
No score change since it was listed.
Verdicts
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.
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.
Before you call either
Neat Pulse MCP
- Ask the person to confirm before
delete_room,delete_device,reboot_deviceorreset_enrolment_code. Deleting a room unenrols all its devices - Ask the person before
send_message_to_deviceorsend_message_to_room, because the message shows on screens in the room - Call
get_domain_guidefirst if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy - If
move_devicereturnsprofile_confirmation_needed, ask whether to apply the room's profile, then repeat the call withassign_room_profile - If a call returns 401, ask the person for a new Pulse token. If it returns 404, check
PULSE_ORG_ID
New Relic MCP Server
- Connect with OAuth; an
api-keyheader reaches only the core tools and the docs say the API key route works only where stated - Send
include-tagswith the groups the task needs (for examplediscovery,data-access) to keep the tool list under 30 - Call
list_available_new_relic_accountsfirst and pass the account id to every query;convert_time_period_to_epoch_msturns 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
Questions
Which is better for AI agents, Neat Pulse MCP or New Relic MCP Server?
New Relic MCP Server scores 62.9 (B) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories.
Do Neat Pulse MCP and New Relic MCP Server need an API key?
Neat Pulse MCP needs an API key. New Relic MCP Server uses an OAuth sign-in.
Can an agent call Neat Pulse MCP and New Relic MCP Server without installing anything?
Neat Pulse MCP runs on your own machine, with no hosted endpoint listed. New Relic MCP Server has a hosted endpoint at https://mcp.newrelic.com/mcp/.
Other comparisons with Neat Pulse MCP or New Relic MCP Server
- Causely MCP server vs New Relic MCP Server
- Cronitor MCP server vs New Relic MCP Server
- incident.io API vs New Relic MCP Server
- New Relic MCP Server vs PagerDuty MCP Server
- New Relic MCP Server vs Rootly MCP Server
- Axiom MCP Server vs Neat Pulse MCP
- Better Stack vs Neat Pulse MCP
- Causely MCP server vs Neat Pulse MCP
- Cronitor MCP server vs Neat Pulse MCP
- Datadog MCP Server vs Neat Pulse MCP
- Datadog MCP Server vs New Relic MCP Server
- Grafana MCP Server vs Neat Pulse MCP
- Grafana MCP Server vs New Relic MCP Server
- Honeycomb MCP vs Neat Pulse MCP
- Axiom MCP Server vs New Relic MCP Server
- Better Stack vs New Relic MCP Server
- Neat Pulse MCP vs Sentry MCP
- New Relic MCP Server vs Sentry MCP
- Honeycomb MCP vs New Relic MCP Server
Machine-readable
- This page as Markdown
/compare/neat-pulse-mcp-vs-new-relic.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/neat-pulse-mcp.json·/api/v1/tools/new-relic.json - From a terminal
anchor compare neat-pulse-mcp new-relic(the CLI) - Over MCP
compare_tools {"a": "neat-pulse-mcp", "b": "new-relic"}at/mcp, no key