Atlassian Confluence MCP Server
@aashari
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 standard MCP interface.
Overview
What is Atlassian Confluence MCP Server?
A server that connects AI assistants (Claude, Cursor AI, and other MCP clients) directly to a Confluence knowledge base, enabling natural language queries to search, read, create, and update pages, spaces, comments, and blog posts.
How to use Atlassian Confluence MCP Server?
Install via npx (npx -y @aashari/mcp-server-atlassian-confluence) and set the required environment variables: ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, and ATLASSIAN_API_TOKEN. Configure the server in Claude Desktop’s config file (~/.claude/claude_desktop_config.json) or in another MCP‑compatible client. Alternatively, use the CLI commands (get, post, put, patch, delete) directly from the terminal.
Key features of Atlassian Confluence MCP Server
- Five generic tools (
conf_get,conf_post,conf_put,conf_patch,conf_delete) for any Confluence API endpoint - Optional JMESPath (
jq) filtering to extract only the needed fields and reduce token costs - TOON (Token‑Oriented Object Notation) output format, which uses 30–60% fewer tokens than JSON
- Automatic truncation of responses larger than ~40,000 characters, with a notice
- Supports all common Confluence API paths: spaces, pages, comments, blog posts, and search
Use cases of Atlassian Confluence MCP Server
- Ask AI about your documentation (e.g., “What’s our API authentication process?”)
- Search across all Confluence spaces using natural language or CQL queries
- Retrieve and display page content, labels, and child pages
- Create new pages and add comments to existing documents
- Update or delete pages, spaces, and comments via the API
FAQ from Atlassian Confluence MCP Server
How do I authenticate with Confluence?
Set the environment variables ATLASSIAN_SITE_NAME (your company’s subdomain), ATLASSIAN_USER_EMAIL, and ATLASSIAN_API_TOKEN. Generate an API token from your Atlassian account settings.
What tools are available?
The server provides five tools that mirror standard HTTP methods: conf_get, conf_post, conf_put, conf_patch, and conf_delete. Each accepts a path (the API endpoint), optional queryParams, a jq filter expression, and an outputFormat (TOON or JSON).
How can I reduce token costs?
By default responses are returned in the TOON format, which is more token‑efficient than JSON. You can further reduce costs by using the jq parameter to filter the response to only the fields you need.
