Skip to main content
Book a demo

Connect DeepWiki to Windsurf

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

Book a demo Windsurf setup guide

Set up

Add DeepWiki to Windsurf in four steps

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

  1. 1

    Approve DeepWiki in Runlayer

    Add DeepWiki from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Windsurf to Runlayer

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

    Windsurf setup guide
  3. 3

    Sign in to DeepWiki

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

  4. 4

    Use DeepWiki from Windsurf

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

Tools

4 DeepWiki tools in Windsurf

Runlayer policy decides which of these Windsurf users can call.

  • Ask question

    Ask any question about a GitHub repository and get an AI-powered, context-grounded response.

  • Ask wiki question

    Ask any question about a GitHub repository's codebase and get an AI-powered answer grounded in its DeepWiki.

  • Read wiki contents

    View documentation about a GitHub repository.

  • Read wiki structure

    Get a list of documentation topics for a GitHub repository.

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