Honeycomb for AI agents
Honeycomb is an observability platform for high-cardinality event data, letting engineers query traces and spans to debug production systems. Developers wire it into their own apps and internal tools instead of building the underlying capability from scratch. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Honeycomb.
Run a query on a dataset
Run a query against a dataset to find the slowest requests in the last hour.
Pull a trace's spans
Fetch the spans for a specific trace to diagnose where latency is coming from.
Create a trigger with approval
Create a new alert trigger only after the on-call engineer confirms the threshold.
33 Honeycomb actions, graded by risk.
Every Honeycomb action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
16Look things up. Allowed by default.
- honeycomb.get_traceGet trace
- honeycomb.list_spansList spans
- honeycomb.get_datasetGet dataset
- honeycomb.get_signalsGet signals
- honeycomb.list_boardsList boards
- honeycomb.find_columnsFind columns
- honeycomb.find_queriesFind queries
- honeycomb.get_triggersGet triggers
- honeycomb.get_environmentGet environment
- honeycomb.list_recipientsList recipients
- honeycomb.get_span_detailsGet span details
- honeycomb.get_query_resultsGet query results
- honeycomb.get_aiconversationGet aiconversation
- honeycomb.get_dataset_columnsGet dataset columns
- honeycomb.list_aiconversationsList aiconversations
- honeycomb.get_workspace_contextGet workspace context
write
17Create and change things. Allow, or ask the user first.
- honeycomb.create_sloCreate slo
- honeycomb.update_sloUpdate slo
- honeycomb.create_boardCreate board
- honeycomb.update_boardUpdate board
- honeycomb.create_markerCreate marker
- honeycomb.create_triggerCreate trigger
- honeycomb.update_triggerUpdate trigger
- honeycomb.create_recipientCreate recipient
- honeycomb.semconvSemconv
- honeycomb.feedbackFeedback
- honeycomb.run_queryRun query
- honeycomb.run_bubbleupRun bubbleup
- honeycomb.refinery_docsRefinery docs
- honeycomb.migration_guideMigration guide
- honeycomb.canvas_agent_invokeCanvas agent invoke
- honeycomb.record_onboarding_stateRecord onboarding state
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Honeycomb in three steps.
- 01Your users connect HoneycombThey sign in to Honeycomb on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, and writes like “create slo” can wait for the user to approve.
- 03Any agent can actYour agent calls Honeycomb through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('honeycomb', { read: 'allow', write: 'ask', // create_slo destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Honeycomb connects.
Honeycomb runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Honeycomb through the same endpoint, policies and audit log as every other app.
The same Honeycomb connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- OAuth 2.0 (MCP)
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Honeycomb from any agent.
Honeycomb and Arc0, answered.
Can I use Honeycomb with Claude, ChatGPT or Cursor?
Yes. Connect Honeycomb to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Honeycomb actions you allow.
How do users connect Honeycomb?
Honeycomb runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Honeycomb through the same endpoint, policies and audit log as every other app.
Which Honeycomb actions can my agent take?
33 in total: 16 read, 17 write and 0 destructive, such as “create slo”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Honeycomb?
Yes. Allow read actions and deny writes in the Honeycomb policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Honeycomb too?
Yes. The same Honeycomb connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Honeycomb into your agent.
Your users connect Honeycomb once, under your brand. Your agent gets 33 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan