# Atlassian MCP Server

> Connect Jira and Confluence to AI tools — Atlassian's official bridge that lets AI tools read and act on Jira, Confluence and the rest of the platform.

- Page: https://tesign.com/en/item/atlassian-mcp-server/
- JSON: https://tesign.com/en/item/atlassian-mcp-server/index.json
- Korean Markdown: https://tesign.com/item/atlassian-mcp-server/index.md
- Generated: 2026-09-18 21:08 UTC

## Numbers

- 1,111 stars — checked on GitHub 2026-09-16 05:46 UTC
- 7-day +11 observed via GH Archive (as of 2026-09-18 15:00 UTC)
- Star total = the value last checked on GitHub (stars_checked_at) + increases observed via GH Archive since. The 24h · 7d · 30d gains are GH Archive hourly events summed to the reference time (as_of). No score of ours.

## AT A GLANCE

- LICENSE: Apache-2.0 (permissive) — https://spdx.org/licenses/Apache-2.0.html
- USAGE: Commercial use, redistribution OK. Keep notices; mark changes.
- OPEN SOURCE: YES
- LANGUAGE: JavaScript
- PLATFORM: web
- CATEGORY: PRODUCTIVITY · DEV TOOLS
- Tags: 지라 · 컨플루언스 · mcp · 업무 자동화
- How to start: Install to use
- SOURCES: GitHub https://github.com/atlassian/atlassian-mcp-server
- INSTALL: https://atlassian.com/platform/rovo-mcp

## ACTIVITY

- Last commit: 2026-09-15 19:26 UTC
- Latest release: [unconfirmed]
- Contributors: [unconfirmed]
- Open issues (incl. PRs): [unconfirmed]
- Made by: [unconfirmed]
- Checked on GitHub: 2026-09-16 05:46 UTC

## TESIGN TAKE

Unofficial connectors existed before; what changes here is an official path where access and security are the vendor's responsibility — which matters when the data is your company's work.

## WHY IT MATTERS

The work lives in Jira and Confluence, but AI tools cannot see inside them. This server bridges the two, so a request like "summarise what's left in this sprint" is answered from the real data. It is built and hosted by Atlassian itself.

## BUILD FROM THIS

- Apache-2.0, cloud-hosted by Atlassian, covering Jira, Confluence, Jira Service Management, Bitbucket, Compass, Loom and wider platform data through the Teamwork Graph.

## WHO IT'S FOR

- Teams on Jira or Confluence who want AI tools in the loop, and managers who have been copying ticket status by hand.

## START IN 5 MINUTES

```
# Open the getting-started guide at atlassian.com/platform/rovo-mcp to connect it to your AI tool, and check first whether your admin has to approve it.
```

## CAVEATS

- Atlassian Cloud only. Company accounts may need admin approval, and since the connected AI tool can read work data, check the permission scope first.

## RECEIPT

- FIRST SEEN BY TESIGN: 2026-09-16 04:46 UTC
- AT SOURCE: 2025-08-01 22:31 UTC
- KEPT: 2026-09-18 21:07 UTC
- Published on TESIGN: 2026-09-18 21:07 UTC
- Text last updated: 2026-09-18 21:07 UTC

## How to read this

- This file was produced by the same build, from the same data, as the tesign.com item page. The text is editorial; the numbers are stored observations.
- null in the JSON means not observed — never zero. The Markdown writes [unconfirmed] for it.
- Star total = the value last checked on GitHub (stars_checked_at) + increases observed via GH Archive since. The 24h · 7d · 30d gains are GH Archive hourly events summed to the reference time (as_of). No score of ours.
- A summary, not legal advice.

[Image] https://tesign.com/img/atlassian-mcp-server-723a66a19b.png