# Axiom MCP Server vs Honeycomb MCP

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

- Canonical: https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp
- Markdown: https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.md (~3,550 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 Honeycomb MCP's 60.7 (C), and leads in 6 of 7 scored categories. 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
- Honeycomb MCP: grade C, 60.7/100, rank #579 of 1349. Markdown https://www.anchorterminal.com/tools/honeycomb-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/honeycomb-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:
- Schema & documentation, 62 against 57
- Agent ergonomics, 63 against 53
- Payments & pricing, 60 against 30

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

### Honeycomb MCP (C)

Good for: Agents that investigate latency and error spikes in a team already sending traces and events to Honeycomb, and that record findings as Boards, Triggers or SLOs.

Watch for: Tool input schemas and annotations are visible only through `tools/list` after sign-in. The public reference gives descriptions, not parameters


## Why the edge

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

- 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.
- Honeycomb MCP (30): No x402, MPP or L402 (0). Plan prices are public, Free and Pro from $150 a month for 50 million events, and MCP is in every plan with no per-call price (10). The Free plan is described as free forever and the signup guide asks for an email address or Google account with no payment step (20). A person signs up in a browser, a Team Owner enables Honeycomb Intelligence, and then OAuth consent or a Team Owner's API key is needed (0).

### Agent ergonomics: Axiom MCP Server +10

- 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.
- Honeycomb MCP (53): 36 tools is above the 30 line (5). The `X-MCP-Toolset` header loads `query` or `canvas` subsets, and the docs don't say how many tools each holds (add 8, so 13). Size controls are described per tool, such as up to 100 datasets or 100 columns a call, subtree zoom on `get_trace` and query limits. Pagination parameters aren't documented (10). Errors are documented with causes and fixes, and the rate-limit message names the retry time. No error code list was found (12). The reference labels each tool read or write and `update_slo` keeps omitted fields. No idempotency keys were found, and we couldn't confirm readOnlyHint or destructiveHint annotations (8). `get_workspace_context` takes no parameters, relative time is the default, and setup is one command or link in nine documented clients. SDKs don't apply (10).

### Schema & documentation: Axiom MCP Server +5

- 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.
- Honeycomb MCP (57): The server is closed source and `tools/list` needs sign-in, so we could not read the input schemas. Partial credit for a contract that exists but is not public (12). docs.honeycomb.io publishes llms.txt and a Markdown twin of every page (10). The tools reference says what each of the 36 tools returns and when an agent reaches for it, for example calling `get_workspace_context` first and `list_memories` before `read_memory`. These are docs, not the definitions the model sees (14). Parameters are mentioned only in passing, with no types, enums or required fields published (4). A use-cases page and a troubleshooting page document the Unauthorized, rate-limit, permission and not-found errors with causes and fixes (9). The registry entry carries version 1.0.0 and Honeycomb links a UI changelog and an API changelog, but changelog.honeycomb.io still disallows unnamed crawlers, so we could not confirm MCP entries (8).

## Score by category

| Category | Weight | Axiom MCP Server | Honeycomb MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 72 | 70 | Axiom MCP Server +2 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 62 | 57 | Axiom MCP Server +5 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 53 | Axiom MCP Server +10 |
| Security & auth | 14% (17.5 this run) | 72 | 68 | Axiom MCP Server +4 |
| Payments & pricing | 10% (12.5 this run) | 60 | 30 | Axiom MCP Server +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 81 | Axiom MCP Server +2 |
| Transparency & trust | 7% (8.8 this run) | 70 | 70 | even |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.2 · B** | **60.7 · C** | |

## Facts side by side

| Fact | Axiom MCP Server | Honeycomb MCP |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Axiom, Inc. | Honeycomb |
| Hosted endpoint | `https://mcp.axiom.co/mcp` | `https://mcp.honeycomb.io/mcp` |
| Transports | Streamable HTTP, SSE (legacy) | Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Freemium | Your plan |
| x402 | no | no |
| Licence | none | Proprietary hosted service under Honeycomb's Terms of Service and Honeycomb Intelligence Supplemental Terms. The companion plugin in honeycombio/agent-skill is MIT |
| Tools exposed | 31 | 36 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `co.axiom/mcp` | `io.honeycomb/mcp` |
| Last release | 2026-10-29 | 2026-10-09 |
| Terms last updated | no date given | 2025-05-22 |
| 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 | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 27 stars |

## How the scores have moved

### Axiom MCP Server

No score change since it was listed.

### Honeycomb MCP

- +2.2 on 4 November 2026: product, correction
- +0.2 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.

**Honeycomb MCP.** OAuth now lets an owner grant read or write per resource, so an agent can be held to queries and reads across the 36 tools, and per-tool rate limits are published. Tool input schemas are visible only after sign-in, no injection guidance was found for telemetry content, and the product changelogs disallow unnamed crawlers.

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

### Honeycomb MCP

1. Use https://mcp.honeycomb.io/mcp for US teams and https://mcp.eu1.honeycomb.io/mcp for EU teams. A team's data lives in one region only
2. If no tools appear after sign-in, ask a Team Owner to enable Honeycomb Intelligence in team settings
3. Ask the owner to choose Customize on the consent screen and grant only the resources the task needs. The agent sees only the tools its scopes allow
4. Send `X-MCP-Toolset: query` or `canvas` to load a subset of the 36 tools. Call `get_workspace_context` first, then `find_columns`, before `run_query`
5. For unattended runs send `Authorization: Bearer <KEY_ID>:<SECRET_KEY>` from a Management key with only Model Context Protocol and Environments scopes

## Questions

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

Axiom MCP Server scores 68.2 (B) on agent readiness against Honeycomb MCP's 60.7 (C), and leads in 6 of 7 scored categories.

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

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

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

Yes. Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp and Honeycomb MCP at https://mcp.honeycomb.io/mcp.


## For agents

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

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

---

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