Skip to main content
The Atlassian MCP Server connects your AI agents directly to Jira and Confluence via the Atlassian Rovo MCP Server, enabling real-time interaction with your Atlassian Cloud data. Within Caylex, agents can search, read, create, and update Jira issues and Confluence pages using natural language-driven tool calls — no manual context switching required. Authentication is handled securely via OAuth 2.1, ensuring all actions respect the authenticated user’s existing Atlassian permissions. Agents can automate repetitive workflows such as generating Jira tickets from notes, transitioning issue states, adding worklogs, managing page comments, and executing complex multi-step operations across Jira and Confluence. This server is ideal for developer, content, and project management teams looking to bring Atlassian productivity directly into their AI-powered workflows.
Prerequisites:
  • An active Atlassian Cloud site with access to Jira and/or Confluence is required.
  • OAuth 2.1 authorization must be completed for the connecting user; if using API token authentication instead, an Atlassian organization admin must first enable this option in the Atlassian Rovo MCP Server settings.
  • Users must have the appropriate Atlassian product licenses and permissions for the Jira projects and Confluence spaces they intend to access.
Important API details:
  • All actions are scoped to the authenticated user’s existing Atlassian permissions — agents cannot access data or perform actions the user is not authorized for.
  • Authentication is via OAuth 2.1 by default; API token authentication is also supported, but must be explicitly enabled by an Atlassian organization admin in the Rovo MCP Server settings.
  • The server operates against Atlassian Cloud sites only — on-premise or Data Center Atlassian instances are not supported.
  • Jira and Confluence searches support their respective native query languages: JQL (Jira Query Language) for Jira issues and CQL (Confluence Query Language) for Confluence content.

​
Server Details

PropertyValue
TransportStreamable HTTP
HostingRemote (externally hosted)
CategoriesCicd, Development & DevOps

​
Authentication

This server supports the following authentication method:

​
OAuth

During the server onboarding flow, you will be prompted to complete the OAuth flow to grant access. See the Atlassian Authentication guide for step-by-step credential configuration.

​
Getting Started

1

Add the server

Navigate to the Server Library and click on the New Server button. Find Atlassian in the Caylex Catalog.
2

Server Onboarding flow

Go through the server onboarding flow.
3

Use in a project

Add the server to a project by configuring project connections. Its tools are now available to any agents connected to that project.

​
Available Tools

This server provides 31 tools:

​
Jira - Read

Get issue details
Get projects
Get issue types
Get field metadata
Get transitions
Get available Jira issue link types (e.g. Blocks, Duplicate, Clones, Relates). For createIssueLink: inwardIssue = blocker, outwardIssue = blocked (e.g. “A is blocked by B” → inwardIssue: B, outwardIssue: A).

​
Jira - Write

Create issue
Update issue
Transition issue status
Add comment
Add or update a worklog on a Jira issue. When worklogId is provided, updates that worklog;
Search issues with JQL
Lookup user IDs

​
Confluence - Read

Get a Confluence page or blog post by ID, including body content.
Get spaces
Get pages or blog posts in a space
Get child pages of specified page
Get footer comments for a page or blog post
Get inline comments for a page or blog post
Get reply(child) comments for a comment

​
Confluence - Write

Create a Confluence page or blog post
Update a Confluence page or blog post
Create a footer comment on a page or blog post
Create an inline comment on specific text in a page or blog post
Search content with CQL

​
Atlassian - General

Get current user info
Get cloudId to make tool calls. When a link is provided (e.g. https://site.atlassian.net/*), try passing the site hostname (e.g. site.atlassian.net) as cloudId to other tools first; if that fails, use this tool to list accessible resources.
Search Jira and Confluence using Rovo Search, ALWAYS use this tool to search for Jira and Confluence content unless the word CQL or JQL is used in the context
Get details of a Jira issue or Confluence page by ARI (Atlassian Resource Identifier), if the id is not an ARI, then use a different tool to fetch the content
https://d338mlbnszozgc.cloudfront.net/logos/linear.svg

Linear

https://d338mlbnszozgc.cloudfront.net/logos/github.svg

Github

​
References

https://support.atlassian.com/rovo/docs/getting-started-with-the-atlassian-remote-mcp-server/

https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/