Atlassian Confluence MCP Server

Atlassian Confluence MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content formatted as Markdown) and search via CQL. Connects AI seamlessly to Confluence knowledge bases using the.

What you get

Transform how you access and interact with your team's knowledge by connecting Claude, Cursor AI, and other AI assistants directly to your Confluence spaces, pages, and documentation. Get instant answers from your knowledge base, search across all your spaces, and streamline your documentation workflow.

• Generic HTTP method tools — - Access any Confluence API endpoint
• TOON output format — - 30-60% token reduction vs JSON
• JMESPath filtering — - Extract only needed data
• Response truncation — - Automatic handling of large responses
• Raw response logging — - Full responses saved to /tmp/mcp/
• Dual transport — - STDIO (for Claude Desktop) and HTTP (for web integrations)

Setting it up

The server ships on npm as @aashari/mcp-server-atlassian-confluence, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Atlassian Confluence is connected, these are the calls the assistant has available:

• get — GET any Confluence endpoint
• post — POST to any endpoint
• put — PUT to any endpoint
• patch — PATCH any endpoint
• delete — DELETE from any endpoint
• conf_get — GET any Confluence API endpoint (read data)
• conf_post — POST to any endpoint (create resources)
• conf_put — PUT to any endpoint (replace resources)
• conf_patch — PATCH to any endpoint (partial updates)
• conf_delete — DELETE from any endpoint (remove resources)
• Examples — The Examples tool exposed by this server
• Requirements — The Requirements tool exposed by this server

Configuration and credentials

You will need 4 environment variables: ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, ATLASSIAN_API_TOKEN, DEBUG. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js: 18.0.0 or higher - MCP SDK: 1.23.0 (uses modern registerTool API) - Confluence: Cloud only (Server/Data Center not supported)

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Atlassian Confluence.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the atlassian confluence mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Atlassian Confluence's toolset — get, post, put and 11 more — is a fair guide to whether it matches your workflow. It is maintained by aashari; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.