Ranked roundup · Confluence
Best MCP Server for Confluence
The best MCP server for Confluence is, for most teams, the one Atlassian ships itself. Atlassian's official remote MCP server covers Confluence alongside Jira and Bitbucket, runs on Atlassian's infrastructure, and authenticates with OAuth 2.1 — nothing to host, no token files. It is also Cloud-only, which is where the community steps in: sooperset's mcp-atlassian (5,820 GitHub stars at verification) supports Confluence Server and Data Center as well as Cloud, and remains the default answer for self-hosted Atlassian estates. Beyond those two the field thins out fast — mostly small Cloud-only wrappers around the REST API, plus managed platforms like Composio that handle OAuth for you. We ranked the four options that actually exist and are maintained rather than padding the list. Rankings come from verifiable criteria — official status, maintenance recency, auth model, and documented coverage — not paid placement. Every repo stat below was checked against the GitHub API on the date shown.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Official · Atlassian
Confluence Cloud teams who want the vendor-supported, zero-hosting path
Search Confluence via CQL, read and summarize pages, create and update pages, navigate spaces. The same server also covers Jira, Jira Service Management, Bitbucket, and Compass. Works with Claude, ChatGPT, Cursor, Copilot CLI, Gemini, and other MCP clients.
Remote server hosted by Atlassian — you add the endpoint to your MCP client, nothing runs locally · OAuth 2.1 browser flow (primary); API tokens for headless setups, which require admin enablement · Apache-2.0 · 1,008★
- Cloud-only — no Confluence Server or Data Center support
- Actions execute with the authenticated user's full existing permissions; Atlassian's own docs recommend least-privilege accounts and audit-log monitoring
- API-token auth for headless use requires an admin to enable it
- The GitHub repo is docs and issue tracking for a hosted service, so its 1,008 stars understate actual usage
- Community
Server/Data Center users, and teams that must keep the whole pipeline self-hosted
CQL search, get/create/update pages, and comments on Confluence, with roughly 98 tools across Confluence and Jira combined. Supports Confluence Cloud and Server/Data Center 6.0+.
Self-hosted — Docker, uvx, or pip; runs locally or on your own infrastructure · API token (Cloud), Personal Access Token (Server/Data Center), or OAuth 2.0 · MIT · 5,820★
- Not an official Atlassian product — MIT-licensed community project
- You host it and manage the credentials yourself
- Bundles Jira and Confluence together rather than shipping a Confluence-only server
- OAuth 2.0 setup is considerably more involved than plain token auth
- Community
Teams already routing several SaaS integrations through one managed MCP platform
62 Confluence tools plus 23 triggers per Composio's own docs, spanning page creation, space management, and content search, with per-user auth handling.
Hosted by Composio — remote MCP and REST endpoints, no server to run · Managed Atlassian OAuth — Composio stores and refreshes tokens; you can supply your own OAuth app for production
- A third party sits in the data path — your Confluence tokens and content transit Composio's infrastructure (SOC 2 Type 2 per their docs)
- Free to start, but usage beyond the free tier is paid
- The 62-tool/23-trigger count is vendor-reported; we did not independently verify each tool
- Not an Atlassian product
Developers who want a thin, full-API passthrough for Confluence Cloud
Five generic HTTP tools (conf_get, conf_post, conf_put, conf_patch, conf_delete) that can call any Confluence Cloud REST endpoint — full read/write reach, but as raw API passthrough rather than curated tools.
Local via npx (Node.js/TypeScript); no hosted option · API token — site name, account email, and Atlassian API token · 61★
- No LICENSE file in the repository, which legally defaults to all rights reserved
- No pushes since 2026-02-22 — about six months without activity at verification
- Cloud-only; the README says Server/Data Center support 'may be added' later
- Generic passthrough design means the model must know Confluence REST endpoints itself
- Small adoption: 61 stars at verification
Confluence MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Atlassian Remote MCP Server | Atlassian | Remote server hosted by Atlassian — you add the endpoint to your MCP client, nothing runs locally | OAuth 2.1 browser flow (primary); API tokens for headless setups, which require admin enablement | Apache-2.0 |
| mcp-atlassian (sooperset) | Community | Self-hosted — Docker, uvx, or pip; runs locally or on your own infrastructure | API token (Cloud), Personal Access Token (Server/Data Center), or OAuth 2.0 | MIT |
| Composio Confluence MCP | Community | Hosted by Composio — remote MCP and REST endpoints, no server to run | Managed Atlassian OAuth — Composio stores and refreshes tokens; you can supply your own OAuth app for production | — |
| mcp-server-atlassian-confluence (aashari) | Community | Local via npx (Node.js/TypeScript); no hosted option | API token — site name, account email, and Atlassian API token | — |
How to choose
Pick Atlassian's official server if you are on Confluence Cloud and want the least setup with a vendor-supported auth path — OAuth 2.1, nothing to run. Pick sooperset/mcp-atlassian if you run Confluence Server or Data Center, which the official server does not touch, or if everything must stay self-hosted behind your own firewall. Pick Composio if you are wiring one agent into many SaaS tools and want OAuth managed for you — accepting a third party in the data path. The aashari server is a thin Cloud-only fallback for developers, not a first choice.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Is there an official MCP server for Confluence?
- Yes. Atlassian's Remote MCP Server (github.com/atlassian/atlassian-mcp-server, Apache-2.0) is generally available and covers Confluence alongside Jira, Jira Service Management, Bitbucket, and Compass. It is a hosted remote server for Atlassian Cloud sites only — it does not support Server or Data Center.
- What does setup and authentication actually look like?
- The official server is the easy path: add Atlassian's remote endpoint to your MCP client and approve access through a browser-based OAuth 2.1 flow, with API tokens available for headless setups if an admin enables them. Self-hosted options like sooperset/mcp-atlassian run via Docker or uvx and take an API token (Cloud) or a personal access token (Server/Data Center); its OAuth 2.0 route works but is the fiddliest option.
- Can I connect an MCP server to Confluence Data Center or Server?
- Not the official one — it is Cloud-only. sooperset/mcp-atlassian supports Confluence Server/Data Center 6.0+ using personal access tokens, and at 5,820 GitHub stars (verified 2026-09-01) it is the most-adopted option largely for that reason.
- Can these servers write to Confluence, or only read?
- The official server and sooperset/mcp-atlassian both create and update pages in addition to searching and reading; sooperset also adds comments. Writes run with the full permissions of the authenticated account, so use a least-privilege account — Atlassian's own docs recommend exactly that plus audit-log monitoring.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.