// the find
sooperset/mcp-atlassian
MCP server for Atlassian tools (Confluence, Jira)
An MCP server that exposes Jira and Confluence to AI assistants as about 98 tools, covering search, issue and page CRUD, comments, attachments, agile boards and page restrictions. It is for developers and teams who already work in Atlassian and want an assistant to read and write there, on Cloud or Server/Data Center.
Cloud and Server/Data Center are both covered, with PAT auth for DC and stated version floors (Confluence 6.0+, Jira 8.14+) instead of a vague compatibility note. The tool reference is generated from per-tool YAML files and Jinja templates in the repo, so it has a build step rather than being hand-maintained. Testing is layered: unit tests per product, auth matrix tests for both deployment types, and a docker-compose environment for end-to-end runs against a local Data Center instance. HTTP transports (SSE and streamable-http), a Helm chart and OAuth 2.0 for multi-user deployments go beyond the usual stdio-only community server.
98 tools means 98 tool definitions loaded into the model's context, and the quick start config enables all of them with no mention of narrowing the set. The tree has toolsets and tools utilities, but the front page does not say how to use them. Write tools such as jira_create_issue, jira_transition_issue and confluence_set_page_restrictions run on the same token as the reads, the README does not mention a read-only mode, and security is a single line pointing at SECURITY.md. The DC version floors are a claim rather than a visible test matrix, since the README does not say which DC versions the e2e suite runs against. Data Center setup detail lives on an external docs site, and the install section gives a full block to one third-party CLI, so the README alone will not get a DC user to a working config.