--- title: "Atlassian MCP server · Connect AI agents to Jira and Confluence" description: "Connect inference.eu agents to Atlassian's official MCP server for Jira, Confluence and more. Search, read and update issues and pages within user permissions." canonical: "https://inference.eu/connect/atlassian/" language: "en" --- MCP servers · Developer tools # Atlassian MCP server: connect AI agents to Jira and Confluence from the EU Atlassian runs an official remote MCP server for its cloud products, covering Jira, Confluence, Jira Service Management, Bitbucket, Compass and Loom. It respects each user's existing permissions. inference.eu agents connect to it with OAuth or an API token to search, summarise and update work across your Atlassian sites. [Contact sales](https://inference.eu/contact/)[What agents can do with it](#tools) 1. 01Authentication: OAuth 2. 02Official server 3. 03EU data centres ## What agents can do with it - 1 ### Jira issues Search issues with JQL, read an issue with comments and transitions, create and edit issues, add comments, transition status and log work, within the projects the user can access. - 2 ### Confluence pages Search Confluence with CQL, read pages and their comments, list spaces, create new pages and update existing ones, so agents can document decisions where your team already looks. - 3 ### Cross-product search and more Search across Jira and Confluence together, look up users and accessible sites, and discover further tools for Jira Service Management, Bitbucket, Compass and Loom as they are needed. ## What Atlassian and its MCP server are Atlassian, headquartered in Sydney, makes Jira for issue and project tracking and Confluence for team documentation, along with Jira Service Management, Bitbucket, Compass and Loom. Many European companies run their planning and knowledge base on Atlassian Cloud. Atlassian's official remote MCP server, sometimes called the Rovo MCP server, runs at `https://mcp.atlassian.com/v2/mcp`. It exposes a set of primary tools and further tools that clients can discover when needed, such as `getJiraIssue`. Every call runs with the permissions the user already has in Jira or Confluence, so the agent sees nothing that person could not. ## What agents can do with Jira and Confluence A delivery agent can answer "what is left in this sprint and who is blocked?" with a JQL search and a short summary per assignee. After a planning meeting, it can create Jira issues from the notes and link them to a Confluence page that records the decisions. Service teams can have an agent read a Jira Service Management ticket, search Confluence for the relevant runbook and draft a reply for an agent to send. Writers can ask an agent to update a release page with the issues fixed in the latest version. ## Setup and authentication Add the Atlassian connector on inference.eu and sign in with your Atlassian account through OAuth 2.1, choosing which site the agent may use. For automated agents, an API token can be used instead, where your organisation allows it. Organisation admins control whether MCP access is allowed, and can restrict which sites and products it reaches. Tokens are stored encrypted in the EU and used only by the agents you allow. Because access follows the user's own permissions, a dedicated account with limited project and space access is a good way to narrow what an agent sees. ## Data protection and where the data goes Issues and pages are fetched from Atlassian's own MCP server and cloud APIs, so data stays with Atlassian as it does for your other Atlassian integrations. Atlassian Cloud offers data residency, including EU regions, for eligible plans; check where your sites are pinned. On inference.eu, the model that reads and writes your issues and pages runs in EU data centres, and your Atlassian credentials are stored encrypted in the EU. Jira tickets and Confluence pages can contain customer data and internal plans, so connect agents only to the projects and spaces they need. ## Approvals and safe use Updating Jira and Confluence affects how teams plan and what they read. A wrong transition can trigger automation rules, and comments notify watchers. Edits to a widely read Confluence page are visible at once. On inference.eu you can let searches and reads run on their own and require a person's approval for creating or editing issues, transitions, comments and page changes. The approval shows the issue key or page and the change. Confluence page history and the Jira issue history let you see and undo what an agent did. ## Atlassian (Jira and Confluence) Vendor Atlassian Corporation Vendor based in Australia Category Developer tools Authentication OAuth Transport Remote (HTTP) Server [Official server](https://github.com/atlassian/atlassian-mcp-server) Documentation [developer.atlassian.com](https://developer.atlassian.com/cloud/rovo-mcp/) ## Atlassian (Jira and Confluence): common questions The questions buyers, developers and legal teams ask us most. Something missing? Ask us directly. Yes. Atlassian runs an official remote MCP server, documented at developer.atlassian.com and on GitHub at atlassian/atlassian-mcp-server. It covers Jira, Confluence, Jira Service Management, Bitbucket, Compass and Loom on Atlassian Cloud. Jira is covered by Atlassian's official MCP server. Agents can search issues with JQL, read and create issues, add comments, transition status and log work, all within the projects the signed-in user can already access. Confluence is covered by the same official Atlassian MCP server. Agents can search with CQL, read pages and comments, list spaces and create or update pages, with the permissions of the connected user. Add the Atlassian connector on inference.eu, sign in with your Atlassian account and choose the site. Your organisation admin may first need to allow MCP access. Tokens are stored encrypted in the EU and used only by the agents you allow. The official remote server is for Atlassian Cloud. Self-managed Jira and Confluence Data Center installations are not covered by it; community servers exist for those, but they need their own review before you rely on them. Yes. Organisation admins decide whether MCP access is allowed and can limit it to particular sites and products. Users can only reach what their existing Jira and Confluence permissions allow, and connections can be revoked. Atlassian serves issues and pages from its own cloud, in the region your sites are pinned to if you use data residency. The model on inference.eu that reads them runs in EU data centres, and credentials are stored encrypted in the EU. Only if you allow it. On inference.eu you can require a person's approval for creating and editing issues, transitions and comments, while searches run freely. This matters because transitions can trigger Jira automation rules and notify watchers. [Ask a question](https://inference.eu/contact/) ## Related [All MCP servers](https://inference.eu/connect/#directory) - [LinearConnect inference.eu agents to Linear's official MCP server to find, create and update issues, projects and comments, with a read-only option.Developer tools](https://inference.eu/connect/linear/) - [GitHubConnect inference.eu agents to GitHub's official MCP server. Read code, triage issues, review pull requests and check Actions runs, with read-only mode available.Developer tools](https://inference.eu/connect/github/) - [NotionConnect inference.eu agents to Notion's official MCP server to search, read, create and update pages and databases in your workspace, with approvals.Productivity](https://inference.eu/connect/notion/) - [SlackConnect inference.eu agents to Slack's official MCP server. Search messages and files, read channels and threads, post updates and edit canvases with admin approval.Communication](https://inference.eu/connect/slack/) ## Move your AI workloads to EU infrastructure Tell us which models you use and roughly how much traffic you have. We reply within one working day with pricing and next steps. - Reply within one working day - Pricing for your volume - DPA ready to sign