Atlassian
Jira work items and Confluence pages
Atlassian lets agents search and read Jira work items, Confluence pages and Bitbucket pull requests, and create or update work items, pages and comments. Each user signs in to their own Atlassian account through the browser and approves the access on a consent screen. Agents get the same permissions as the user: they can change work items and pages, change page permissions, and merge pull requests. Tools that delete Jira data stay off until an organization admin turns them on. Each tool call uses Rovo credits.
What an agent can do with Atlassian
Find work items and pages
The search tool runs a semantic search across Jira, Confluence and connected apps; Atlassian calls it beta. The searchJiraIssuesUsingJql tool searches work items with JQL, and the searchConfluence tool searches Confluence content with CQL. The agent can find the open work for a release and the pages about it.
Create and update Jira work items
The createJiraIssue tool makes a new work item, and the editJiraIssue tool changes it. The transitionJiraIssue tool moves a work item to a new status, a sprint or the backlog. The addOrEditJiraIssueComment tool adds a comment. The agent can file a bug with steps to reproduce.
Write Confluence pages
The getConfluenceContent tool reads a page. The createConfluenceContent tool makes a page, blog post, live doc, whiteboard, database or folder. The updateConfluenceContent tool changes a page, and the createConfluenceComment tool adds a comment. The agent can turn meeting notes into a page.
Review Bitbucket pull requests
The getBitbucketRepoPullRequestDiff tool reads the changes of a pull request. The addBitbucketRepoPullRequestComment tool adds a review comment, and the mergeBitbucketRepoPullRequest tool merges it. The Bitbucket workspace must be linked to an Atlassian organization.
How to connect Atlassian to OpenBot
Open Atlassian in OpenBot
Press Open in OpenBot on this page, or find Atlassian in the app's Apps tab. Get the app first if it is not on this computer.
Sign in
Press Connect and finish the sign-in in your browser. OpenBot keeps the token on the computer that runs OpenBot. You can disconnect at any time.
Give an agent a task
Ask an agent for work that needs Atlassian, such as one of the example prompts below. The agent uses the plugin's tools to do it.
Example prompts3
AtlassianWhich open Jira work items are assigned to me?
AtlassianFind the Confluence page about our release process and summarize it.
AtlassianCreate a Jira work item for the login bug with steps to reproduce.
Apps1
Atlassian
Jira, Confluence, and Bitbucket, over Atlassian's MCP server with browser sign-in.
Information6
- Developer
- Atlassian
- Category
- Productivity
- Version
- 1.0.0
- Website
- atlassian.com
- Privacy policy
- atlassian.com/legal/privacy-policy
Questions
Is the Atlassian MCP server official?
Yes. Atlassian hosts the Atlassian MCP server, also called the Rovo MCP server, at mcp.atlassian.com. This plugin uses version 2 of the server. Sign-in uses OAuth 2.1, and the actions respect the access controls and permissions that the user has.
Does the Atlassian plugin need an API token?
No. Each user signs in to their own Atlassian account through the browser and approves the access on a consent screen. OpenBot does the sign-in itself, keeps the tokens in encrypted storage, and adds the Authorization header. The plugin catalog holds no secret.
What can the agent see and change in Atlassian?
The agent has the same permissions as your Atlassian account. It finds a tool with the discover tool, then runs it with executeRead, executeWrite or executeDestructive. Write tools change work items, pages, page permissions and public links, and merge pull requests. The tools that delete Jira data or manage Jira projects stay off until an organization admin turns them on. Atlassian gets the requests that the agent sends. Your workspaces, conversations and files stay on the computer that runs OpenBot.
What can an Atlassian admin control, and what does it cost?
Organization admins control the server in Atlassian Administration. By default, Atlassian allows its supported domains, and the list includes localhost and 127.0.0.1, which OpenBot uses for sign-in. IP allowlists also apply to tool calls. Each tool call uses Rovo credits from the pool of the organization. Jira and Confluence Standard, Premium and Enterprise plans include a monthly credit allowance for each user.
Sources
Every statement about Atlassian comes from the pages below, checked on . They can change after that date.
- Atlassian: Get started with the Atlassian MCP server
- Atlassian: Upgrade from Atlassian MCP v1 to v2
- Atlassian: Configure OAuth 2.1
- Atlassian Developer: supported tools
- Atlassian: Understand Atlassian MCP server
- Atlassian: Control Atlassian MCP server settings
- Atlassian: Available Atlassian MCP server domains
- Atlassian: Rovo usage limits