Skip to main content
Book a demo

Connect Honeycomb to Windsurf

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

Book a demo Windsurf setup guide

Set up

Add Honeycomb to Windsurf in four steps

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

    Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Honeycomb’s 38 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

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

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

Tools

38 Honeycomb tools in Windsurf

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Windsurf runs it.

  • Block output after it runs (not available)

    Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.

In Windsurf

  • Enforcement needs Windsurf 1.12.31 or newer.
  • When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.

Frequently asked questions

Connect more

Find another combination