Best for
- Developers who use Jira and Confluence daily with Cline
- Individuals wanting to integrate Atlassian into AI workflows without context switching
- MCP-compatible client users seeking quick Atlassian integration
M
MCP Atlassian Server
Community
MCP server connecting AI assistants to Jira and Confluence
GitHub source repository ↗
54FMRS · D
A feature-rich third-party MCP server (48 features) covering major Jira and Confluence read/write operations, notably optimized for Cline with thorough install docs; not officially maintained, so token permissions must be managed carefully.
MCP Atlassian Server (by phuc-nt) is a Model Context Protocol server that connects AI agents such as Cline, Claude Desktop, or Cursor to Atlassian Jira and Confluence, letting them query data and perform actions through a standardized interface. Version 2.0.1 expanded features from 21 to 48, using Jira API v3 and Confluence API v2, with full Agile/Scrum workflow support, page version management, attachments, and comments. The server distinguishes read-only Resources from action Tools. It is primarily optimized for Cline, designed local-first, and released under the MIT license.
Setup
Follow the llms-install.md guide in the repository (formatted for AI assistants to parse); you need a Node.js environment and an Atlassian API token. Alternatively install via Smithery: npx -y @smithery/cli install @phuc-nt/mcp-atlassian-server --client claude. Cline users can simply ask Cline to install this server.
Fit and risk
Not for
- Teams requiring enterprise-grade official support or Atlassian-maintained assurance
- Users without an MCP-compatible client
- High-compliance environments needing strict centralized token governance
Required permissions
- Requires an Atlassian API token that inherits all permissions of its creator
- Tools can perform create, update, and delete mutations on Jira and Confluence data
- Runs locally and needs access to Atlassian cloud APIs
Risks and side effects
- The API token inherits all of the creator's permissions, so a leak is high-impact
- Never ask LLMs to analyze config files containing your token
- Third-party, non-official project; Atlassian API changes may require maintenance
- AI-driven mutations (deleting pages, transitioning issues) risk unintended changes
Troubleshooting
- Check that the Atlassian API token is correctly configured and not expired
- Confirm your Node.js environment meets system requirements
- Verify the Cline client configuration step by step against llms-install.md
- Confirm your account has access to the target Jira site and Confluence spaces
Use cases
Have an AI assistant query and filter issues assigned to you in Jira
Create, update, and transition Jira issues via natural language
Create, update, and delete Confluence pages
View and manage Jira boards, sprints, and filters
Manage Confluence page comments and attachments
Supported clients
ClineFull support
Claude DesktopPartial support
CursorPartial support