An unofficial Model Context Protocol (MCP) server for Jira Cloud and Confluence Cloud: issues, search, comments, links, attachments, agile boards, and Confluence pages with private drafts.
Install
No framework information available.
README
Atlassian MCP Server
A Model Context Protocol (MCP) server that lets AI assistants such as Claude Code and GitHub Copilot work with Jira Cloud and Confluence Cloud. It runs on your machine, talks to your site with your own API token, and needs no Rovo credits.
This is an unofficial, community project. It is not affiliated with or endorsed by Atlassian.
Getting started
Create an API token at https://id.atlassian.com/manage-profile/security/api-tokens.
Add the server to your AI assistant. Follow the guide for your assistant:
If the server does not start, see Troubleshooting.
Try it. Ask your assistant, for example:
- "Show me my open Jira issues in project PROJ."
- "Create a bug in PROJ for the login timeout, with steps to reproduce."
- "Draft a Confluence page in my personal space summarizing PROJ-123." Then open the link it returns to preview the draft.
Features
Jira
- Issues: get, create, update, delete, assign, transition, labels, watchers, votes, and change history.
- Custom fields: set any field, including custom fields, and discover a project's required fields and allowed values before creating an issue.
- Markdown everywhere: descriptions, comments, worklog comments, and multi-line custom fields are written in Markdown and converted to Atlassian Document Format; rich text is read back as Markdown. Mention a user, notifying them, with
@[Display Name](resolved by a user search; an ambiguous name is refused, listing the matches) or@[Display Name](accountid:ID). In Jira, embed a file already attached to the issue within a paragraph of its own: images and videos are shown inline, other files as file cards. Embedded files are read back the same way. - Search: JQL search with paging, approximate totals, JQL validation, and value suggestions.
- Comments, links, and attachments: read and write comments, link issues by link type name or phrase (such as "is blocked by"), and upload, download, or delete attachments.
- Projects and people: projects, components, versions, users, groups, and permissions.
- Time tracking: worklogs and estimates.
- Filters: saved filters and favorites.
- Agile: boards, backlogs, sprints, epics, ranking, and sprint report, burndown, and velocity data.
Confluence
- Private drafts: new pages and changes to existing pages are saved as drafts by default, so you can preview them in Confluence before anything is published.
- Safe editing: edit one section of a page and keep everything else, including macros and smart links; edits that would lose content Markdown cannot represent are refused.
- Pages: read pages as Markdown or ADF, create, update, publish, move, and delete them, and browse children and version history.
- Search: CQL search across spaces.
- Spaces, comments, attachments, and labels: upload, list, and delete attachments (deleting moves an attachment to the space's trash, and needs the opt-in
confluence-admintoolset).
Tools are grouped into toolsets so you can enable only what you need. See the full list of tools.
System requirements
- Windows, macOS, or Linux.
- The .NET 10 SDK or later, which provides the
dnxanddotnet toolcommands used to run the server. - An MCP client, such as Claude Code, GitHub Copilot in Visual Studio Code or Visual Studio, or the GitHub Copilot CLI.
Atlassian requirements
- A Jira Cloud site, a Confluence Cloud site, or both, such as
https://example.atlassian.net. - An Atlassian account on that site.
- An API token for that account. See Manage API tokens for your Atlassian account.
The server acts as you: it can see and change only what your account can, and every change appears in Jira and Confluence history under your name.
Configuration
The server is configured with environment variables, which each guide shows how to set.
| Variable | Required | Description |
|---|---|---|
ATLASSIAN_SITE_URL |
Yes | Your site URL, such as https://example.atlassian.net. |
ATLASSIAN_EMAIL |
Yes | The email address of your Atlassian account. |
ATLASSIAN_API_TOKEN |
Yes | Your API token. |
ATLASSIAN_TOOLSETS |
No | Comma-separated toolsets to enable. Defaults to all. |
ATLASSIAN_ENABLED_TOOLS |
No | Comma-separated tool names to enable, to narrow the toolsets further. |
ATLASSIAN_READ_ONLY |
No | true to enable only tools that do not change anything. |
ATLASSIAN_ATTACHMENT_FOLDERS |
No | Full paths of the folders whose files the attachment tools may upload by path without asking, separated by ; on Windows and : elsewhere, like PATH. See Uploading files by path. |
| Toolset | Tools for |
|---|---|
jira-issues |
Issues, transitions, labels, watchers, votes, and history |
jira-search |
JQL search, validation, and suggestions |
jira-comments |
Issue comments |
jira-links |
Issue links and link types |
jira-attachments |
Issue attachments |
jira-projects |
Projects, components, versions, and roles |
jira-users |
Users, groups, and permissions |
jira-worklogs |
Worklogs and time tracking |
jira-filters |
Saved filters |
jira-agile |
Boards, sprints, epics, ranking, and reports |
jira-fields |
Fields, issue types, priorities, statuses, resolutions, and connection checks |
jira-admin |
Creating, updating, and deleting projects, and group membership |
confluence |
Pages, drafts, search, spaces, comments, attachments, and labels |
confluence-admin |
Deleting pages and attachments. Not included in all; enable it explicitly. |
Some clients limit how many tools they send to the model; GitHub Copilot allows about 128. The guides show a toolset selection that stays under that limit.
More information
License
Changes from Previous Version
Adoption Assessment
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.