Community MCP server for Jira and Confluence that supports Atlassian Cloud and Server/Data Center deployments with search, create, update, transition, comments, attachments, pages, and agile tools.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
4 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": ["mcp-atlassian"],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "YOUR_EMAIL",
"JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "YOUR_EMAIL",
"CONFLUENCE_API_TOKEN": "YOUR_CONFLUENCE_API_TOKEN"
}
}
}
}MCP Atlassian is a community MCP server for Jira and Confluence. It supports Atlassian Cloud and Server/Data Center deployments and exposes tools for Jira issues, Confluence pages, search, comments, attachments, agile workflows, service desk data, fields, versions, links, and metrics.
The project documents uvx, Docker, pip, and source installations plus stdio, SSE, and streamable HTTP transport options.
These sources were reviewed on 2026-06-05. Prefer the live docs for current authentication options, tool list, Cloud versus Server/Data Center compatibility, HTTP transport guidance, and troubleshooting.
For a Cloud API-token setup:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": ["mcp-atlassian"],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "YOUR_EMAIL",
"JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "YOUR_EMAIL",
"CONFLUENCE_API_TOKEN": "YOUR_CONFLUENCE_API_TOKEN"
}
}
}
}
Server/Data Center deployments use personal access tokens instead of Cloud email and API-token pairs. See the authentication docs for OAuth and deployment details.
Atlassian tools often hold operational and customer-sensitive data. Use least-privilege tokens, limit projects and spaces, and require approval before an agent changes issue state, page content, comments, attachments, or service desk records.
Treat issue contents, Confluence pages, attachments, comments, project metadata, and API tokens as sensitive. Do not expose production Atlassian content to model providers without organizational approval.
content/mcp/jira-mcp-server.mdx covers Atlassian's official Jira and
Confluence MCP integration. This entry covers the separate
sooperset/mcp-atlassian community server with Cloud and Server/Data Center
self-hosted deployment options.
Show that MCP Atlassian Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/mcp-atlassian-server)MCP Atlassian Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
| Field | Community MCP server for Jira and Confluence that supports Atlassian Cloud and Server/Data Center deployments with search, create, update, transition, comments, attachments, pages, and agile tools. Open dossier | Manage Jira tickets and Confluence documentation Open dossier | MCP server for remote project memory-bank management, with multi-project directories, file listing, read/write/update tools, and path isolation. Open dossier | Third-party MCP server for searching Apple Developer Documentation, framework APIs, Swift and Objective-C references, sample code, platform compatibility, documentation updates, and WWDC session data. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trustDiffers | Package not verified | Package verified | Package not verified | Package not verified |
| Source provenanceDiffers | Source-backed | No submission link | Source-backed | Source-backed |
| SubmitterDiffers | oktofeesh1 | — | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | ||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | First-party | Source-backed | Source-backed |
| Author | sooperset | Atlassian | Aliosh Pimenta | kimsungwhee |
| Added | 2026-06-05 | 2025-09-18 | 2026-06-06 | 2026-06-05 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓mcp-atlassian can search, create, update, transition, comment on, and delete Jira issues or Confluence pages depending on configured permissions. Tools can modify project status, issue fields, worklogs, comments, page content, attachments, labels, versions, components, and service desk data. Require human approval before creating or transitioning issues, changing permissions-sensitive fields, updating Confluence pages, deleting content, or posting comments. Protect API tokens, PATs, OAuth credentials, and environment files. | ✓Scope Atlassian access and review issue or page writes because updates can notify teams and change project records. | ✓Memory Bank MCP can read, create, and update files inside the configured memory-bank root. Do not point `MEMORY_BANK_ROOT` at a home directory, source repository root, cloud-sync folder, or any directory containing secrets. Avoid auto-approving write and update tools until the expected file structure and naming rules are established. The path validator rejects path traversal and slash-containing file/project names, but users should still keep the root directory narrow and dedicated. Docker mode requires a bind mount for the memory bank; review the host path and container path before granting write access. | ✓This is a third-party MCP server, not an official Apple project. The server retrieves public documentation and metadata, but user queries can still reveal private project context to the MCP client, model provider, logs, and network services. Documentation answers should be checked against the live Apple documentation before shipping platform-specific, beta, deprecated, or compatibility-sensitive code. Use `@latest` intentionally when you want the newest package; pin a version when reproducible builds or locked team tooling are required. |
| Privacy notes | ✓Jira issue content, Confluence pages, comments, attachments, user profiles, service desk data, agile metadata, internal links, and credentials may be exposed to the MCP client and model. Atlassian project data can contain customer incidents, security vulnerabilities, roadmap plans, HR data, legal notes, or internal runbooks. Review workspace permissions and model-provider retention before connecting production Atlassian instances. | ✓Jira tickets, Confluence pages, comments, attachments, user metadata, and organization details may be sent through tool calls. | ✓Memory-bank files can contain project plans, architecture notes, decisions, credentials accidentally pasted into notes, customer context, meeting details, or personal information. Tool calls may expose project names, file names, memory contents, root-path assumptions, and update text to the MCP client and model provider. Multi-project listing can reveal all projects stored under the memory-bank root. Auto-approved memory tools can persist model-generated statements as project memory without human review. Back up important memory-bank directories and review retention expectations before sharing them across clients or machines. | ✓Prompts and tool calls may include framework names, API choices, platform targets, WWDC interests, sample-code requests, app architecture details, feature plans, and compatibility constraints. MCP client logs and model transcripts can retain documentation queries and returned API text outside Apple's documentation site. Avoid sending proprietary source code, unreleased product names, customer requirements, private bundle identifiers, or internal roadmap details when a public documentation lookup is enough. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Manage Jira tickets and Confluence documentation
Manage Cline-style project memory banks through MCP with project listing, file listing, read, write, update, validation, and isolated storage roots.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.