Connect Atlassian to Claude
Give Claude governed access to Atlassian’s 96 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Atlassian to Claude in four steps
Admins approve the server once. Everyone in Claude then gets it through the same governed connection.
- 1
Approve Atlassian in Runlayer
Add Atlassian from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude to Runlayer
Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Atlassian’s 96 tools show up in Claude’s own tool list.
Claude setup guide - 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
Use Atlassian from Claude
Atlassian’s approved tools appear in Claude. Every call is checked against policy and recorded.
Tools
96 Atlassian tools in Claude
Runlayer policy decides which of these Claude 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.
Control
What Runlayer can see and stop in Claude
Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.
Gateway policy (available)
Every Atlassian call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
Compliance API import (available)
Anthropic Compliance API imports Claude web and desktop chats for review.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Stop a call before it runs (available)
Runlayer can reject a Claude 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)
Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.
Frequently asked questions
Connect more