Skip to main content
Book a demo

Connect Atlassian to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

Add Atlassian to Gemini CLI in four steps

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

    Users add the Runlayer Plugin to Gemini CLI by following Runlayer’s setup guide. Gemini CLI reaches Atlassian’s 96 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Gemini CLI 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 Gemini CLI

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

Tools

96 Atlassian tools in Gemini CLI

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

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

  • Gateway policy (available)

    Every Atlassian call from Gemini CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Gemini CLI 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 Gemini CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Gemini CLI’s model sees it.

  • Redact output in place (not available)

    Gemini CLI can only add text to a tool result, not replace it, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

In Gemini CLI

  • Enforcement needs Gemini CLI 0.26.0 or newer.
  • When Runlayer blocks a call or its output, Gemini CLI shows the model the block reason instead.

Frequently asked questions

Connect more

Find another combination