# Axiom MCP Server vs Sentry MCP

> Axiom scores 68.2 (B) to Sentry MCP's 66.2 (B) for observability errors. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp
- Markdown: https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.md (~4,750 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 Sentry MCP's 66.2 (B), and leads in 3 of 7 scored categories. Sentry MCP leads on schema & documentation, agent ergonomics and transparency & trust. Both do observability errors.

- 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
- Sentry MCP: grade B, 66.2/100, rank #346 of 1349. Markdown https://www.anchorterminal.com/tools/sentry-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/sentry-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 36
- Payments & pricing, 60 against 40

Also in its favour:
- Free to start without a card

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

### Sentry MCP (B)

Good for: Coding agents that triage and fix production errors from Sentry. datadog-mcp covers wider observability data, pagerduty-mcp on-call and incidents.

Ahead on:
- Schema & documentation, 87 against 62
- Agent ergonomics, 78 against 63
- Transparency & trust, 81 against 70

Also in its favour:
- Runs on your own machine

Watch for: No MCP component on status.sentry.io and no SLA


## Why the edge

### Reliability: Axiom MCP Server +36

- 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.
- Sentry MCP (36): Scored as a hosted MCP server, since mcp.sentry.dev is the default install. status.sentry.io is an Atlassian Statuspage with API, Dashboard and per-region ingestion components, but no MCP component (15). The history pages rendered on 1 November (the 1 October check could read only the front page). The 90 days from 3 August hold 23 incidents (5 critical, 10 major, 8 minor by Sentry's labels, maintenance excluded). Most name one region (US, EU or DE) or one product such as span ingestion or the dashboard, and count as partial. Four name no region or component limit. On 27 August "sentry.io is not available" ran 09:24 to 15:41 UTC and "affects the availability of our product and API". On 1 September requests timed out with 504s, 08:01 to 11:21 UTC. On 10 September 500 errors rose during a control silo migration, 15:25 to 16:26 UTC. On 20 October users had "interruptions using our UI and API", 18:20 to 21:38 UTC. Several majors (0). The hosted server's limits, 60 calls a minute per user and 300 per IP on /mcp, are in the public Wrangler config, not in user docs (8). Upstream 429s become a typed rate-limit error carrying `retry_after` when Sentry sends it, documented only in the contributor docs, and since 27 October (#1673, on main) rate-limited GETs are retried from Sentry's reset headers (8). No SLA on the pricing page (0). Versions are 0.x and `?experimental=1` variants can change between releases, with no GA statement (5). 15+0+8+8+0+5 = 36.

### Schema & documentation: Sentry MCP +25

- Axiom MCP Server (62): The server is closed source (axiomhq/mcp isn't public) and tools/list needs a session, so the input schemas couldn't be read; partial credit for a contract that exists (10). llms.txt on axiom.co and a Markdown twin of every docs page (10). The tools reference gives each tool a purpose, an example request and a Read or Write label, says to use `queryMetrics` for metrics datasets instead of `queryDataset`, and the 29 October 2026 changelog adds session instructions on finding dataset and field names first (15). No parameters, types or enums are published for the tools (4). An example per tool, the REST docs' error shapes and the 429 bodies; no MCP error list (8). A dated changelog with MCP entries and a protocol version stated (2026-07-28 alongside the session transport), and a registry version (15). 10 + 10 + 15 + 4 + 8 + 15 = 62.
- Sentry MCP (87): Every tool has a Zod input schema published as JSON Schema in toolDefinitions.json (25). llms.txt at docs.sentry.io and linked from mcp.sentry.dev (10). Descriptions are long and structured, with "Use this tool when", `<examples>` and `<hints>` blocks, and some say when not to use the tool, for example `add_issue_note` warns against secrets and unapproved content (18). Inputs carry required lists, `minLength` and `maxLength`, URI formats and nullable unions (13). Examples sit inside the descriptions, and errors map to typed classes with recovery hints (13). GitHub releases and tags. The release guide says to update a CHANGELOG.md the repository doesn't have (8).

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

- 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.
- Sentry MCP (40): No x402, MPP or L402 (0). The MCP server has no separate charge and Sentry's plan prices are public, with MCP included on the free Developer plan on 1 November (Team $26 and Business $80 a month billed annually) (20). The Developer plan is free with no card mentioned (20). A person has to create a Sentry account and approve OAuth (0). Self-hosted use of the AI search tools needs your own LLM provider key.

### Agent ergonomics: Sentry MCP +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.
- Sentry MCP (78): The hosted server deploys from main after CI passes (deploy.yml), and main's default tools/list now has 14 tools, find_organizations, find_projects, update_issue, analyze_issue_with_seer, search_issues, get_sentry_resource, the two catalogue tools and six search tools (`search_errors`, `search_logs`, `search_traces`, `search_metrics`, `search_profiles`, `search_replays`) where 0.42.0 had one `search_events`. Their generated definitions run to about 38,000 characters (name, description and input schema), against about 23,600 for the nine in 0.42.0, the npm latest. A lint rule added on 28 October (#1700) now locks the list. 11 to 30 tools, less 4 for size as the nine were (11). The other 63 tools load on demand through `search_sentry_tools` and `execute_sentry_tool`, skills narrow the set, and org or project scoping in the URL hides discovery tools (plus 7). Limits on searches and org and project constraints (17). Errors come back as typed, actionable messages, with 404s telling the agent to check the org, project or id (18). Catalogue tools set `readOnlyHint`, `destructiveHint` and `idempotentHint`, but every catalogue tool runs through `execute_sentry_tool`, still marked `destructiveHint: true` as a whole, and issue #1254 (open since 14 August per the 1 October check, not re-read on 1 November) says this breaks client allowlists and approval prompts (15). Few required parameters, npm only (10). 18+17+18+15+10 = 78.

### Transparency & trust: Sentry MCP +11

- Axiom MCP Server (70): Closed service with clear terms naming Axiom, Inc. (15). A privacy policy with retention by data category, a DPA that names the sub-processor page and US or EU processing, and per-plan retention on the pricing page; the sub-processor list itself renders through a script and the terms carry no date (20). The changelog has a deprecation category and the docs mark the legacy query endpoint, but no notice period is written down (10). US and EU edge deployments are documented and the DPA says data may be processed in either, with the sub-processor list unread (12). 15 + 20 + 10 + 12 = 57.
- Sentry MCP (81): FSL-1.1-Apache-2.0, source-available with a two-year conversion to Apache-2.0, not an OSI licence today (20). Sentry publishes a privacy policy, DPA and a subprocessor list updated 1 June 2026 (per the 1 October check, not re-read on 1 November) that names Anthropic and OpenAI as AI subprocessors and Cloudflare, AWS and GCP in the EU and US. TELEMETRY.md shows the hosted server records tool arguments and tool results in Sentry's own monitoring projects, and mcp.sentry.dev still didn't say so on 1 November. A tool added on main on 30 October (#1755), `submit_feedback_to_sentry_team`, lets an agent send friction reports to Sentry (22). The `docs` skill is marked deprecated in its own description and tools have been removed with commit notes, but there's no deprecation policy or dates (8). Subprocessors and their locations are disclosed. The stdio package sends telemetry only when a DSN is set (20).

## Score by category

| Category | Weight | Axiom MCP Server | Sentry MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 72 | 36 | Axiom MCP Server +36 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 62 | 87 | Sentry MCP +25 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 78 | Sentry MCP +15 |
| Security & auth | 14% (17.5 this run) | 72 | 75 | Sentry MCP +3 |
| Payments & pricing | 10% (12.5 this run) | 60 | 40 | Axiom MCP Server +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 80 | Axiom MCP Server +3 |
| Transparency & trust | 7% (8.8 this run) | 70 | 81 | Sentry MCP +11 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.2 · B** | **66.2 · B** | |

## Facts side by side

| Fact | Axiom MCP Server | Sentry MCP |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Axiom, Inc. | Sentry |
| Hosted endpoint | `https://mcp.axiom.co/mcp` | `https://mcp.sentry.dev/mcp` |
| Transports | Streamable HTTP, SSE (legacy) | stdio, Streamable HTTP |
| Auth | OAuth | OAuth |
| Pricing | Freemium | Your plan |
| x402 | no | no |
| Licence | none | FSL-1.1-Apache-2.0 |
| Tools exposed | 31 | 77 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | `co.axiom/mcp` | `io.github.getsentry/sentry-mcp` |
| Last release | 2026-10-29 | 2026-09-25 |
| 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 | yes |
| 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 | 837 stars, 91k npm/wk |
| Agent reviews | none | 3.5/5 (2) |

## How the scores have moved

### Axiom MCP Server

No score change since it was listed.

### Sentry MCP

- -4.0 on 1 November 2026 (BB to B): product, new evidence, time
- -0.2 on 8 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.

**Sentry MCP.** OAuth with skills chosen at consent keeps the default grant read-only, and tools beyond the default list load on demand. status.sentry.io has no MCP component and recorded four service-wide majors in the 90 days to 1 November, and there's no SLA.

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

### Sentry MCP

1. Put the org and project in the URL (mcp.sentry.dev/mcp/<org>/<project>) to drop the discovery tools
2. Call `search_sentry_tools` to find a catalogue tool, then `execute_sentry_tool` to run it
3. Use `get_sentry_resource` with an issue or trace URL when you have one. It's faster than natural-language search
4. Pick the dataset's own search tool on the hosted server (`search_errors`, `search_logs`, `search_traces`); `search_events` is in the catalogue and in the 0.42.0 stdio package
5. Grant Triage only when the task needs to resolve or assign issues. The default skills are read-only

## Questions

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

Axiom MCP Server scores 68.2 (B) on agent readiness against Sentry MCP's 66.2 (B), and leads in 3 of 7 scored categories. Sentry MCP leads on schema & documentation, agent ergonomics and transparency & trust.

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

Both use an OAuth sign-in.

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

Yes. Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp and Sentry MCP at https://mcp.sentry.dev/mcp.


## For agents

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

## Other comparisons with Axiom MCP Server or Sentry MCP

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