Skip to main content
Book a demo

Connect Honeycomb to Claude

Give Claude governed access to Honeycomb’s 38 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add Honeycomb to Claude in four steps

Admins approve the server once. Everyone in Claude then gets it through the same governed connection.

  1. 1

    Add Honeycomb to Runlayer

    Honeycomb isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Honeycomb’s 38 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 3

    Sign in to Honeycomb

    Sign in the way Honeycomb requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Honeycomb from Claude

    Honeycomb’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

38 Honeycomb tools in Claude

Runlayer policy decides which of these Claude users can call.

  • Canvas agent invoke

    Kick off a single-turn run of the Honeycomb Canvas agent.

  • Canvas agent poll response

    Poll for the result of a previously-issued canvas_agent_invoke call.

  • Create board

    Create a board (dashboard) with query, SLO, and text panels.

  • Create burn alert

    Create a burn alert on an SLO.

  • Create marker

    Creates a marker (a vertical annotation on charts) to mark a point or window in time, such as a deploy, incident, or config change.

  • Create recipient

    Create a notification recipient (email, Slack, PagerDuty, or webhook) so it can be attached to triggers, SLO burn alerts, and Anomaly Detection.

  • Create slo

    Create an SLO (Service Level Objective) backed by an auto-created SLI derived column.

  • Create trigger

    Create a trigger that fires alerts when a query result crosses a threshold.

See all 38 Honeycomb tools

Control

What Runlayer can see and stop in Claude

Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.

  • Gateway policy (available)

    Every Honeycomb call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination