Atlassian Confluence MCP Server
io.github.aashari/mcp-server-atlassian-confluence
Overview
Confluence Cloud MCP server exposing generic GET, POST, PUT, PATCH, and DELETE tools with TOON output, JMESPath filtering, STDIO default transport, and optional HTTP mode.
Documentation
Atlassian Confluence MCP Server
Node.js and TypeScript MCP server for Confluence Cloud. It connects AI assistants to Confluence by exposing five generic tools for Confluence REST API access.
Installation
Run directly with npx:
npx -y @aashari/mcp-server-atlassian-confluence
Or install globally:
npm install -g @aashari/mcp-server-atlassian-confluence
mcp-atlassian-confluence
Node.js 18.0.0 or newer is required.
Configuration
Set Confluence Cloud credentials in environment variables, a local .env file, or the global config file at ~/.mcp/configs.json. Direct environment variables take precedence, followed by .env, then the global config file.
Required credentials are ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, and ATLASSIAN_API_TOKEN. ATLASSIAN_SITE_NAME is only the site subdomain, such as mycompany for mycompany.atlassian.net. Optional DEBUG enables debug logs, TRANSPORT_MODE selects stdio or http, and PORT controls the HTTP port when TRANSPORT_MODE is http.
The documented default MCP client launch is command npx with args -y and @aashari/mcp-server-atlassian-confluence. STDIO is the default transport. HTTP mode listens at /mcp on localhost port 3000 unless PORT is set.
Capabilities
The server registers five generic Confluence tools: conf_get, conf_post, conf_put, conf_patch, and conf_delete. Each tool accepts an API path, optional query parameters, optional JMESPath filter named jq, and outputFormat set to toon or json. Write tools also accept a JSON request body.
Common paths include /wiki/api/v2/spaces, /wiki/api/v2/pages, /wiki/api/v2/pages/{id}, /wiki/api/v2/pages/{id}/body, /wiki/api/v2/pages/{id}/labels, /wiki/api/v2/blogposts, /wiki/rest/api/search, and comment endpoints. TOON output is the default for token efficiency. Large responses are truncated around 40000 characters and raw responses are saved under /tmp/mcp/mcp-server-atlassian-confluence.
Limitations
This server supports Confluence Cloud only. Confluence Server and Data Center are not supported. It uses Atlassian API token authentication and does not implement OAuth or browser login. Unfiltered Confluence responses can be large, so the README recommends jq filters and pagination. HTTP mode is intended for testing and web integrations; normal desktop MCP launch uses STDIO.
Repository: https://github.com/aashari/mcp-server-atlassian-confluence