← Back to directory

MCP Atlassian

Community

Model Context Protocol server for Confluence and Jira

GitHub source repository ↗

★ 5.8k Stars Category · Collaboration Very popular Source revision 5118f265d8ae

56FMRS · C

Reliability

7/20

Security and permissions

9/20

Maintenance

14/20

Documentation

14/20

Setup experience

12/20

MCP Atlassian is a fairly comprehensive community MCP server offering roughly 98 tools for working with Jira and Confluence across Cloud and Server/Data Center deployments, with core tools covering search, CRUD on issues/pages, and status transitions — but it requires users to carefully manage the security of their own Atlassian API credentials.

Read the FMRS scoring method →

MCP Atlassian is a community-maintained Model Context Protocol server that lets AI assistants interact directly with Atlassian's Jira and Confluence products. It supports both Atlassian Cloud and Server/Data Center deployments (Confluence 6.0+, Jira 8.14+), exposing 98 tools in total covering search, create, update, transition, and comment operations. The README highlights key tools such as JQL-based Jira search, issue retrieval, issue creation/update/transition, plus CQL-based Confluence search and page retrieval/creation/update/commenting. Authentication supports API tokens (Cloud), Personal Access Tokens (Server/Data Center), and OAuth 2.0 per the full documentation.

Tools

jira_search

Search Jira issues using JQL (Jira Query Language)

jira_get_issue

Get details for a specific Jira issue

jira_create_issue

Create a new Jira issue

jira_update_issue

Update fields on an existing Jira issue

jira_transition_issue

Change the workflow status of a Jira issue

confluence_search

Search Confluence content using CQL (Confluence Query Language)

confluence_get_page

Get the content of a specific Confluence page

confluence_create_page

Create a new Confluence page

confluence_update_page

Update the content of an existing Confluence page

confluence_add_comment

Add a comment to a Confluence page

Setup

Go to https://id.atlassian.com/manage-profile/security/api-tokens and create an API token (Server/Data Center users should use a Personal Access Token instead).
Add an mcp-atlassian entry to your Claude Desktop or Cursor MCP configuration, setting command to uvx, args to ["mcp-atlassian"], and env variables JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN (Server/Data Center deployments use JIRA_PERSONAL_TOKEN instead of username + API token).
Alternatively, configure the same uvx-based server through Autohand Code using autohand mcp add mcp-atlassian env ....
Restart your client after saving the configuration so the AI assistant can search, create, or update Jira issues and Confluence pages.

claude_desktop_config.json

{"mcpServers": {"mcp-atlassian": {"command": "uvx", "args": ["mcp-atlassian"], "env": {"JIRA_URL": "https://your-company.atlassian.net", "JIRA_USERNAME": "[email protected]", "JIRA_API_TOKEN": "your_api_token", "CONFLUENCE_URL": "https://your-company.atlassian.net/wiki", "CONFLUENCE_USERNAME": "[email protected]", "CONFLUENCE_API_TOKEN": "your_api_token"}}}}

Generate and validate client config

Fit and risk

Best for

Teams that want an AI assistant to read and write Jira issues and Confluence pages directly
Organizations running both Atlassian Cloud and Server/Data Center environments
Developers who want JQL/CQL search, issue creation, and status transitions inside their IDE or chat client

Not for

Users without an Atlassian Jira or Confluence account/instance
Scenarios requiring official Atlassian support guarantees (this is not an official Atlassian product)
Environments that cannot securely store or rotate API tokens/.env files

Required permissions

URL(s) of the Jira and/or Confluence instance
Atlassian account email + API token (Cloud), or a Personal Access Token (Server/Data Center)
Whatever read/write permissions that account actually holds in Jira/Confluence (creating/updating issues, creating/updating pages, and adding comments require write access)

Risks and side effects

A leaked API token or PAT can be used to read and write Jira/Confluence data as that account
The README explicitly warns to keep .env files secure to avoid credential exposure
Creating, updating, and transitioning issues, and creating/updating pages, are write operations — misconfigured automation could cause unintended data changes
Not officially maintained by Atlassian, so updates and security response depend on the community repository maintainers

Troubleshooting

Verify JIRA_URL / CONFLUENCE_URL are correct (Cloud is typically https://your-company.atlassian.net and its /wiki path)
Cloud deployments need email + API token; Server/Data Center deployments should use JIRA_PERSONAL_TOKEN instead of username + token
Check whether the API token has expired or lacks sufficient permissions; regenerate it from Atlassian account security settings if needed
Consult the Troubleshooting page at mcp-atlassian.soomiles.com for further debugging steps

Use cases

Find issues assigned to me in the PROJ project

Search Confluence for onboarding docs

Create a bug ticket for a login issue

Update the status of PROJ-123 to Done

Supported clients

Claude DesktopFull support

CursorFull support

Autohand CodeFull support

Related MCP servers

Compare with other MCP servers