MCP Atlassian
An MCP server for Jira and Confluence, cloud and self-hosted: search, create and edit issues and pages
- 6,061 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Creates and edits issues and pages in an external system
- Holds API tokens with user-level rights
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-atlassianDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates and edits issues and pages in an external system
- Holds API tokens with user-level rights
This is third-party code. Review the repository files before installing.
What it does
The server connects the agent to Jira and Confluence. The agent searches issues with JQL and pages with CQL, reads, creates and updates them, transitions statuses and adds comments. It supports Atlassian Cloud and Server/Data Center: Confluence 6.0+ and Jira 8.14+. Auth is via API token, personal access token or OAuth 2.0, and an HTTP mode serves multiple users.
Who it is for. For teams that track work in Jira and document in Confluence.
Good fit when
- You need your issues or a project report from Jira
- You need to file a bug from a chat description
- You need to find or update a Confluence page
Not a fit when
- The team uses Yandex Tracker or another tracker
- The token grants more rights than the agent should have and cannot be scoped
Example request
Find issues assigned to me in PROJ and move PROJ-123 to DoneMCP
- Transport
- stdio, sse, http
- Authentication
- key is optional
Environment variables
JIRA_URL- Jira URL
JIRA_USERNAME- Jira Cloud user email
JIRA_API_TOKENsecret- Jira Cloud API token
JIRA_PERSONAL_TOKENsecret- Personal access token for Jira Server/Data Center
CONFLUENCE_URL- Confluence URL
CONFLUENCE_USERNAME- Confluence Cloud user email
CONFLUENCE_API_TOKENsecret- Confluence Cloud API token
Limitations
Requires an Atlassian API token or a personal access token for Server/Data Center. Atlassian Cloud restricted service for users in Russia, so cloud instances may be unreachable; a self-hosted Jira or Confluence in your network works. Not an official Atlassian product.
How to disable. Remove the mcp-atlassian block from the MCP config and revoke the API token in Atlassian settings.
FAQ
Does it work with self-hosted Jira?
Yes, Server and Data Center are supported with personal access tokens.
Can I connect only Jira?
Yes, set only the Jira variables.
Discussion
No questions or reviews yet.
Related
MCP serversAtlassian's official cloud MCP server for Jira, Confluence, Jira Service Management, Bitbucket, Compass and Loom, with skills
Jira MCP in Go: an agent searches issues by JQL, runs sprints, comments and worklogs and sees an issue's branches and pull requests on Cloud and Server
The official Todoist MCP server: the agent finds, creates and updates tasks and projects in your account
Trello MCP server with 57 tools: cards, lists, checklists, attachments, comments, custom fields and workspaces, plus acceptance-criteria extraction
An MCP server for Linear: issues, projects, cycles, milestones, documents and project updates via the GraphQL API
An MCP server for Kaiten: cards, comments, spaces and boards with control over response verbosity
README in short
The README is a quick start: get a token, add a config with uvx and environment variables, start asking. Details live on the docs site: install via uvx, Docker and pip, auth options, HTTP transport and the tool reference. It includes a compatibility table and the key Jira and Confluence tools. MIT licensed.