Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Query observability data, traces and SLOs.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Honeycomb MCP server connects a Honeycomb observability account to Claude, ChatGPT and any MCP-compatible agent. It lets an agent run aggregation queries over OpenTelemetry telemetry, walk distributed traces span by span, and read SLOs, Triggers and service maps — then write findings back as Boards or alerts. Sign-in is OAuth, and a Team Owner must enable Honeycomb Intelligence first.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
readOnlyHint or destructiveHint annotation was readable. Read/write classification here is Honeycomb's, from its documentation, not ours from the wire.get_service_map allows 10 calls a minute, the create tools 20, update_trigger and update_slo 30. Honeycomb notes limits are subject to change and suggests upgrading a plan if you hit them regularly.get_service_map is Enterprise-only, and get_anomaly_service_profiles requires anomaly detection enabled for the team.It can change things. Honeycomb's own tools reference documents eight write tools that create or update Boards, Triggers, SLOs, notification recipients and Canvas investigations, plus a `feedback` tool that sends a message to Honeycomb. Every one of them requires the `mcp:write` scope, which you grant separately during OAuth consent or on an API key. Read tools need only `mcp:read`.
The directory snapshot is stale, and Honeycomb's documentation is the current surface. Anthropic's 2026-08-16 snapshot names 13 tools, five of which no longer appear in Honeycomb's tools reference under those names. Honeycomb's page documents 34 tools across twelve categories, 26 of them read-only. Treat the directory list as a historic subset and the vendor page as authoritative.
Honeycomb Intelligence is probably disabled for your team. Honeycomb's troubleshooting page says authenticating successfully but seeing no tools, or having every call fail on authorization, usually means the team-level AI setting is off. Only a Team Owner can enable it in team settings. That switch gates the whole connector, not individual tools.
Yes, if that data is in your telemetry. `get_trace` returns every span for a trace ID as a waterfall, and `get_dataset_columns` can return sample values. Honeycomb's AI policies page states MCP uses sample telemetry values, and its AI terms forbid customers from putting protected health information or GDPR special-category data through Honeycomb Intelligence at all.
No. Honeycomb prices its plans by events ingested and metrics data points, not by queries run, so reading through MCP does not consume ingest allowance. Queries are instead governed by per-tool rate limits: 200 or 300 calls a minute for discovery tools, 100 for `run_query` and `get_trace`, and as low as 10 for the Enterprise-only service map.
The documentation no longer says so. Anthropic's directory points at a URL under a `product-lifecycle/beta/` path, but that URL now redirects to `/integrations/mcp/concepts`, a permanent integrations page. Nothing in Honeycomb's four current MCP pages carries a beta, preview or experimental label, and the pricing page lists Honeycomb MCP as a Free-plan feature.
The Free plan is enough. Honeycomb's pricing page lists Honeycomb MCP among Free-tier features, alongside distributed tracing, BubbleUp and the Canvas AI copilot, with an ingest ceiling of 20 million events a month. Two tools carry extra gates: `get_service_map` is badged Enterprise, and `get_anomaly_service_profiles` needs anomaly detection enabled for the team.
.md suffix; the directory's documentation URL docs.honeycomb.io/troubleshoot/product-lifecycle/beta/mcp/ returns 308 to /integrations/mcp, which returns 307 to this page) · retrieved 2026-08-18/mcp-suffixed form returns a byte-identical body) · retrieved 2026-08-18POST returns HTTP 401 with www-authenticate: Bearer resource_metadata=…; GET returns 405 · retrieved 2026-08-18docs.honeycomb.io/robots.txt disallows only /cdn-cgi/ and /_next/, names a sitemap, and carries Content-Signal: ai-train=yes, search=yes, ai-input=yes — synthesis is expressly permitted on all three axes (fetched 2026-08-18) · retrieved 2026-08-18Connect Honeycomb once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.