Skip to main content
Book a demo

Connect Honeycomb to Claude Cowork

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

Book a demo Claude Cowork setup guide

Set up

Add Honeycomb to Claude Cowork in four steps

Admins approve the server once. Everyone in Claude Cowork 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 Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Honeycomb’s 38 tools show up in Claude Cowork’s own tool list.

    Claude Cowork 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 Cowork

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

Tools

38 Honeycomb tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork 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 Cowork

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork 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)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination