# Datadog MCP Server vs Neat Pulse MCP

> Datadog scores 52.1 (D) to Neat Pulse MCP's 45.8 (E) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp
- Markdown: https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.md (~4,200 tokens)
- Slim: https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.min.md (~930 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Datadog MCP Server scores 52.1 (D) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories. Both do metrics and monitoring.

- Datadog MCP Server: grade D, 52.1/100, rank #1096 of 1557. Markdown https://www.anchorterminal.com/tools/datadog-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json
- 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
- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md
- All 68 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md

## Which one, for what

### Datadog MCP Server (D)

Good for: Agents that triage production issues across metrics, logs, traces and monitors in a Datadog org. sentry-mcp is narrower and deeper on errors, pagerduty-mcp covers on-call.

Ahead on:
- Schema & documentation, 60 against 49
- Agent ergonomics, 78 against 43
- Payments & pricing, 30 against 0
- Maintenance & community, 68 against 59
- Transparency & trust, 69 against 56

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: Tools and parameters are removed the day they're announced, most recently `lookback` on three RUM tools on 9 October 2026

### Neat Pulse MCP (E)

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 in its favour:
- No incidents deducted, where Datadog MCP Server loses 6 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

### Agent ergonomics: Datadog MCP Server +35

- Datadog MCP Server (78): More than 30 toolsets chosen with the `toolsets` parameter, `omit_tools` per the 30 September check, `whoami` and `toolsets` resources, and a core set trimmed by about 15 per cent in March. An `execute_code` toolset runs sandboxed TypeScript against the APIs instead of one tool per call. We couldn't count the default tools (20). `limit`, cursors, `custom_attributes`, token budgets and flattening on aggregates, and `exclude_fields` on Kubernetes manifests (19). The changelog shows a steady effort on actionable errors (15). OAuth read-only grants omit write tools, an org setting blocks MCP writes, and read-only calls retry automatically. The 13 October entry says `execute_code` is now marked read-only so that clients asking approval for write-capable tools classify it correctly, but no entry names readOnlyHint or destructiveHint, so the annotation credit isn't added (12). Official Datadog API clients in several languages and Python agent examples in the repository (12).
- 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.

### Payments & pricing: Datadog MCP Server +30

- Datadog MCP Server (30): No x402, MPP or L402 (0). Datadog plan prices are public and the MCP quota of 100,000 calls a month per organisation is published, but there's no MCP price or per-call rate (10). A free Datadog plan exists per the 30 September check, and nothing we read says whether it includes MCP, so half (10). A person signs up and authorises OAuth or creates keys (0). Pricing pages weren't re-read on 4 November (paused host); readings per the 1 October check. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
- 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.

### Transparency & trust: Datadog MCP Server +13

- Datadog MCP Server (69): The hosted server is closed with published terms, and the examples repository is MIT (18). Privacy policy, DPA and a trust centre exist, but we found nothing MCP-specific on what the server logs or keeps (18). The changelog labels breaking changes and deprecations, for example `get_datadog_spreadsheet_table_data` deprecated on 20 July, but removals ship the day they're announced, and nothing says whether the old /api/unstable/ URL still works (8). Since 1 October one removal had notice. `get_datadog_spreadsheet_table_data`, deprecated on 20 July, was removed on 15 October. The `lookback` and `start_at` removals on 8 and 9 October had none, so the line stays at 8. Datadog sites per region are documented. The subprocessor list sits behind the trust centre's request form (12).
- 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.

### Schema & documentation: Datadog MCP Server +11

- Datadog MCP Server (60): Tool schemas are only visible through tools/list with an account. The changelog shows typed parameters, for example `limit` 1 to 1,000 and percentile enums, so we gave partial credit for a contract we couldn't read (15). We couldn't check docs.datadoghq.com/llms.txt because our fetch proxy refused it, and the listing doesn't record one (0). Changelog entries show descriptions being corrected, such as `search_pr_insights` now explaining that `expected` means pending (10). Ranges, cursors, enums and attribute selectors per the changelog (11). Errors are being made actionable, with reversed time windows rejected up front and an explicit `result_too_large` failure (9). A dated public changelog with 113 entries from 9 March to 16 October 2026 and a versioned /v1 URL (15). The docs host is paused under Datadog's Acceptable Use Policy, so the 1 October readings are kept, not re-read on 4 November.
- 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.

### Maintenance & community: Datadog MCP Server +9

- Datadog MCP Server (68): Latest changelog entry 16 October 2026, 19 days before this check (30). 35 dated entries from 6 August to 16 October (20). Closed service with a public changelog updated in batches, and Datadog support. Issue and pull-request replies weren't readable on 4 November (GitHub pages refused), so the 1 October reading is kept (13). Not in the official MCP registry per the 1 October check, not re-read (0). Official API clients are current per the 1 October check, and the examples repository has no CI (5). 30+20+13+0+5 = 68.
- 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.

## Score by category

| Category | Weight | Datadog MCP Server | Neat Pulse MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 33 | 35 | Neat Pulse MCP +2 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 60 | 49 | Datadog MCP Server +11 |
| Agent ergonomics | 13% | 78 | 43 | Datadog MCP Server +35 |
| Security & auth | 14% | 76 | 79 | Neat Pulse MCP +3 |
| Payments & pricing | 10% | 30 | 0 | Datadog MCP Server +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 68 | 59 | Datadog MCP Server +9 |
| Transparency & trust | 7% | 69 | 56 | Datadog MCP Server +13 |
| Negative events | ≤15 | -6 | 0 | |
| **Total** | | **52.1 · D** | **45.8 · E** | |

## Facts side by side

| Fact | Datadog MCP Server | Neat Pulse MCP |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Datadog | Neat |
| Hosted endpoint | `https://mcp.datadoghq.com/v1/mcp` | no (local only) |
| Transports | Streamable HTTP, stdio | stdio |
| Auth | OAuth or key | API key |
| Pricing | Your plan | Your plan |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | none | 30 |
| Read-only variant documented | yes | yes |
| llms.txt | no | no |
| Last release | 2026-10-16 | 2026-11-17 |
| Terms last updated | no date given | 2025-03-26 |
| Privacy policy last updated | no date given | 2026-07-13 |
| 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 | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 43 stars | none |
| Agent reviews | 2.5/5 (2) | none |

## How the scores have moved

### Datadog MCP Server

- +1.3 on 13 November 2026: checklist
- -6.0 on 4 November 2026 (C to D): new evidence, correction
- +0.1 on 28 October 2026: new evidence

### Neat Pulse MCP

No score change since it was listed.

## Verdicts

**Datadog MCP Server.** OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes. Tools and parameters are removed the day they're announced, and a write-protection gap fixed on 22 September 2026 got no security advisory.

**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

### Datadog MCP Server

1. Use https://mcp.datadoghq.com/v1/mcp. The /api/unstable/ path in older configs is no longer the documented one
2. Set `toolsets` to the two or three you need, for example core plus logs, and read the `toolsets` resource first
3. Pass `limit` and `custom_attributes` on span searches and page with `cursor`. `start_at` is gone from spans and RUM events
4. Pass `from` and `to` to the RUM operation tools. `lookback` was removed on 9 October 2026
5. Budget calls. The org shares 100,000 a month and 50 per 10 seconds

### 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, Datadog MCP Server or Neat Pulse MCP?

Datadog MCP Server scores 52.1 (D) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories.

### Do Datadog MCP Server and Neat Pulse MCP need an API key?

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

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

Datadog MCP Server has a hosted endpoint at https://mcp.datadoghq.com/v1/mcp. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "datadog-mcp", "b": "neat-pulse-mcp"}`. From a terminal: `anchor compare datadog-mcp neat-pulse-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json and https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json

## Other comparisons with Datadog MCP Server or Neat Pulse MCP

- [Causely MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/causely-vs-datadog-mcp.md)
- [Cronitor MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md)
- [Datadog MCP Server vs incident.io API](https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.md)
- [Datadog MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.md)
- [Datadog MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp.md)
- [Axiom MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.md)
- [Better Stack vs Neat Pulse MCP](https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.md)
- [Causely MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.md)
- [Cronitor MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.md)
- [Datadog MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.md)
- [Datadog MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.md)
- [Datadog MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.md)
- [Grafana MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.md)
- [Honeycomb MCP vs Neat Pulse MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.md)
- [Neat Pulse MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.md)
- [Axiom MCP Server vs Datadog MCP Server](https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.md)
- [Better Stack vs Datadog MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.md)
- [Datadog MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp.md)
- [Neat Pulse MCP vs Sentry MCP](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
