# Axiom MCP Server vs Datadog MCP Server

> Axiom scores 68.2 (B) to Datadog's 50.8 (D) for observability logs. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp
- Markdown: https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.md (~4,200 tokens)
- 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-04

Axiom MCP Server scores 68.2 (B) on agent readiness against Datadog MCP Server's 50.8 (D), and leads in 5 of 7 scored categories. Datadog MCP Server leads on agent ergonomics. Both do observability logs.

- Axiom MCP Server: grade B, 68.2/100, rank #269 of 1349. Markdown https://www.anchorterminal.com/tools/axiom.md · JSON https://www.anchorterminal.com/api/v1/tools/axiom.json
- Datadog MCP Server: grade D, 50.8/100, rank #925 of 1349. Markdown https://www.anchorterminal.com/tools/datadog-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json
- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md
- All 49 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md

## Which one, for what

### Axiom MCP Server (B)

Good for: Agents that investigate logs, traces and metrics with APL and need a budget cap, and agents that must bootstrap their own observability without a person.

Ahead on:
- Reliability, 72 against 33
- Payments & pricing, 60 against 20
- Maintenance & community, 83 against 68

Also in its favour:
- Free to start without a card
- No incidents deducted, where Datadog MCP Server loses 6 points for them

Watch for: The server is closed source and tool input schemas are only visible through an authenticated session

### 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:
- Agent ergonomics, 78 against 63

Also in its favour:
- Runs on your own machine

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


## Why the edge

### Payments & pricing: Axiom MCP Server +40

- Axiom MCP Server (60): No x402, MPP or L402 (0). The pricing page states the platform fee, the free allowances, add-on prices and that usage carries volume discounts, with a calculator rather than a printed per-unit rate (20). The Personal plan is free with no card (20). `POST /v2/orgs/provision` needs no authentication and returns a working token, so an agent can start without a person, though a person must claim the organisation within 24 hours for it to persist (20). 0 + 20 + 20 + 20 = 60.
- Datadog MCP Server (20): 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.

### Reliability: Axiom MCP Server +39

- Axiom MCP Server (72): Scored as a hosted MCP server. status.axiom.co is an incident.io page with six US and six EU components (API, ingest, querying, alerting, endpoints, app) and uptime per component for August to November 2026, with no MCP component (20). feed.rss holds nine incidents in the 90 days to 3 November 2026, among them elevated query errors in the US from 18:05 to 19:15 UTC on 14 October with missed monitor runs, a metrics ingestion and query disruption on 15 October, elevated query errors after a deployment on 21 October, metrics query error rates on 25 October, query errors and monitor delays on 27 October, metrics ingest on 30 October, EU monitor alerting degraded on 7 October, and console authentication through GitHub degraded on 12 August. US querying shows 99.90 per cent uptime. One incident over an hour on the query path and several shorter ones, so one major (10). Rate limits are published as headers (X-RateLimit-Scope, -Limit, -Remaining, -Reset) and plan limits on the limits page, but the per-minute numbers aren't printed (12). 429 with a message and reset headers, query cost caps that answer 429 with the reset time, and provisioning 429 with backoff guidance; no idempotency keys for the write tools (10). A published SLA of 99.9 per cent monthly uptime for Axiom Cloud with 10 and 25 per cent credits (10). Not marked beta; registry version 1.0.0 (10). 20 + 10 + 12 + 10 + 10 + 10 = 72.
- Datadog MCP Server (33): Scored as a hosted MCP server. status.datadoghq.com now answers robots.txt with an S3 AccessDenied 403, which this run reads as a refusal, so the 1 October reading of its front page (components with no MCP component, three late-September incidents in other products) is struck. Datadog's Acceptable Use Policy also bars robots from its sites, so nothing more was requested. With no component reading left, the status-page line is 0, and the 90-day incident history is unread (5). The changelog publishes a burst limit of 50 calls per 10 seconds and a monthly quota of 100,000 tool calls per organisation, doubled from 50,000 on 28 August (15). Read-only software-delivery calls are retried on transient failures and `get_datadog_k8s_manifest` explains what to do when rate limited, but no Retry-After or backoff guidance for MCP clients was found. The 5 is kept from 1 October as a partly met line (5). No SLA found (0). GA since 9 March 2026 on the stable /v1 URL since 20 July, with some toolsets still experimental, kept at 8 as partly met (8). 0+5+15+5+0+8 = 33.

### Agent ergonomics: Datadog MCP Server +15

- Axiom MCP Server (63): 31 tools in the reference, 28 without service map, so the 11-to-30 band with no toolset switch (15). APL queries take their own limits and time ranges, and the REST API documents timestamp pagination; nothing documents page sizes for the list tools (15). 429 bodies state the limit and reset, the REST docs describe error shapes, and a `sendFeedback` tool reports unclear descriptions to Axiom (12). Reads and writes are labelled in the docs, but delete tools have no confirmation step, no idempotency keys exist for writes, and annotations weren't confirmed (8). One-command setup for 16 clients with OAuth, a setup prompt for agents, and official SDKs in eight languages for the API behind it (13). 15 + 15 + 12 + 8 + 13 = 63.
- 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).

### Maintenance & community: Axiom MCP Server +15

- Axiom MCP Server (83): Read as a closed service. Changelog entry of 29 October 2026 covering the MCP server (30). Dated entries on 7 August, 23 September and 16, 21, 22, 28 and 29 October 2026 (20). A Discord community linked from the company page, support@axiom.co in the docs and email support on paid plans; no public issue tracker for the hosted server (12 of 15). co.axiom/mcp in the official registry under a DNS-verified namespace since 30 September 2025, though the entry still points at the SSE URL and version 1.0.0 (15). No package to assess for a hosted server; Axiom keeps SDKs in eight languages for the API (6). 30 + 20 + 12 + 15 + 6 = 83.
- 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.

## Score by category

| Category | Weight | Axiom MCP Server | Datadog MCP Server | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 72 | 33 | Axiom MCP Server +39 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 62 | 60 | Axiom MCP Server +2 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 78 | Datadog MCP Server +15 |
| Security & auth | 14% (17.5 this run) | 72 | 76 | Datadog MCP Server +4 |
| Payments & pricing | 10% (12.5 this run) | 60 | 20 | Axiom MCP Server +40 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 68 | Axiom MCP Server +15 |
| Transparency & trust | 7% (8.8 this run) | 70 | 69 | Axiom MCP Server +1 |
| Negative events | ≤15 | 0 | -6 | |
| **Total** | | **68.2 · B** | **50.8 · D** | |

## Facts side by side

| Fact | Axiom MCP Server | Datadog MCP Server |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Axiom, Inc. | Datadog |
| Hosted endpoint | `https://mcp.axiom.co/mcp` | `https://mcp.datadoghq.com/v1/mcp` |
| Transports | Streamable HTTP, SSE (legacy) | Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Pricing | Freemium | Your plan |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 31 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `co.axiom/mcp` | not listed |
| Last release | 2026-10-29 | 2026-10-16 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| 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 | not found in the text |
| Popularity | none | 43 stars |
| Agent reviews | none | 2.5/5 (2) |

## How the scores have moved

### Axiom MCP Server

No score change since it was listed.

### Datadog MCP Server

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

## Verdicts

**Axiom MCP Server.** An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.

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

## Before you call either

### Axiom MCP Server

1. With no organisation, call `POST https://api.axiom.co/v2/orgs/provision` once, store the returned token and surface the `claimUrl` to the person; both are shown once and the organisation is deleted after 24 hours unclaimed
2. Call `listDatasets` and `getDatasetFields` before `queryDataset`; metrics datasets take `queryMetrics` with MPL, not APL
3. Treat a 429 as a rate limit or a query-cost cap; read `X-RateLimit-Reset` or the limit message for when the window resets, and don't resend sooner
4. Prefer OAuth; if a token header is the only option, expect the PAT to carry the person's full rights and ask them to set a query cost limit on their role first
5. `deleteDashboard`, `deleteMonitor` and `deleteNotifier` are live writes with no confirmation step; list first and confirm with the person before deleting

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

## Questions

### Which is better for AI agents, Axiom MCP Server or Datadog MCP Server?

Axiom MCP Server scores 68.2 (B) on agent readiness against Datadog MCP Server's 50.8 (D), and leads in 5 of 7 scored categories. Datadog MCP Server leads on agent ergonomics.

### Do Axiom MCP Server and Datadog MCP Server need an API key?

Axiom MCP Server uses an OAuth sign-in. Datadog MCP Server takes an API key or an OAuth sign-in.

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

Yes. Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp and Datadog MCP Server at https://mcp.datadoghq.com/v1/mcp.


## For agents

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

## Other comparisons with Axiom MCP Server or Datadog MCP Server

- [Axiom MCP Server vs incident.io API](https://www.anchorterminal.com/compare/axiom-vs-incident-io.md)
- [Axiom MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp.md)
- [Axiom MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp.md)
- [Causely MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/causely-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 Better Stack](https://www.anchorterminal.com/compare/axiom-vs-better-stack.md)
- [Axiom MCP Server vs Causely MCP server](https://www.anchorterminal.com/compare/axiom-vs-causely.md)
- [Axiom MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.md)
- [Axiom MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.md)
- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md)
- [Better Stack vs Datadog MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-datadog-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)
- [Axiom MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.md)
- [Datadog MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/datadog-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