# Neat Pulse MCP vs New Relic MCP Server (slim)

> New Relic scores 62.9 (B) to Neat Pulse MCP's 45.8 (E) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.md (~4,250 tokens) · this version ~930 tokens · JSON https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.json · canonical https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Neat Pulse MCP: E 45.8, rank #1268 of 1557 · https://www.anchorterminal.com/tools/neat-pulse-mcp.min.md
- New Relic MCP Server: B 62.9, rank #657 of 1557 · https://www.anchorterminal.com/tools/new-relic.min.md
- Neat Pulse MCP, good 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 Runs on your own machine.
- New Relic MCP Server, good 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 A hosted endpoint, with nothing to install; Free to start without a card.

| Category | Neat Pulse MCP | New Relic MCP Server |
| --- | --- | --- |
| Reliability (16%) | 35 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 49 | 51 |
| Agent ergonomics (13%) | 43 | 59 |
| Security & auth (14%) | 79 | 76 |
| Payments & pricing (10%) | 0 | 45 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 59 | 80 |
| Transparency & trust (7%) | 56 | 81 |

| Fact (where they differ) | Neat Pulse MCP | New Relic 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 |
| Tools exposed | 30 | 40 |
| 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 |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |

Why the edge:
- Payments & pricing, New Relic MCP Server +45: Neat Pulse MCP 0 (No payment protocol (0).); New Relic MCP Server 45 (No x402, MPP or L402 (0).)
- 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.); New Relic MCP Server 60 (Scored as a hosted MCP server.)
- Transparency & trust, New Relic MCP Server +25: Neat Pulse MCP 56 (Closed source, and the npm package carries no licence field.); New Relic MCP Server 81 (Closed service with clear dated terms (paid 8 November 2022, unpaid 21 October 2021) naming New Relic, Inc.)
- Maintenance & community, New Relic MCP Server +21: Neat Pulse MCP 59 (1.1.0 on 17 November 2026 (30).); New Relic MCP Server 80 (Read as a closed service.)
- 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).); 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).)
