Skip to main content
Book a demo

Connect Atlassian to Windsurf

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

Book a demo Windsurf setup guide

Set up

Add Atlassian to Windsurf in four steps

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

  1. 1

    Approve Atlassian in Runlayer

    Add Atlassian 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 Atlassian’s 96 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Windsurf setup guide
  3. 3

    Sign in to Atlassian

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

  4. 4

    Use Atlassian from Windsurf

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

Tools

96 Atlassian tools in Windsurf

Runlayer policy decides which of these Windsurf users can call. 12 read data only and 1 can change or delete data.

  • Add comment to Jira issue

    Add or update a comment on a Jira issue

  • Add Confluence content permissions

    Adds one or more content-level permission grants to a single Confluence content entity.

  • Add Confluence reaction

    Add emoji reaction to Confluence content

  • Add connections to goals

    Add one type of connection to one or more Atlassian Goals.

  • Add connections to projects

    Add one type of connection to one or more Atlassian Projects.

  • Add Teamwork Graph context

    Adds a relationship between two entities in the Teamwork Graph (e.g. linking two Jira work items, marking one as blocking another, attaching a remote link, or connecting a Jira work item to an Atlas…

  • Add labels to Confluence content

    Add labels to any Confluence content (page, blogpost, attachment, custom content)

  • Add or edit Jira issue comment

    Add a comment to a Jira issue, or edit an existing one: omit commentId to add, or pass one from listJiraIssueComments to edit.

See all 96 Atlassian 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 Atlassian 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