Atlassian Confluence
STDIOMCP server for Atlassian Confluence integration with AI assistants
MCP server for Atlassian Confluence integration with AI assistants
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.
Get up and running in 2 minutes:
Generate a Confluence API Token:
# Set your credentials export ATLASSIAN_SITE_NAME="your-company" # for your-company.atlassian.net export ATLASSIAN_USER_EMAIL="[email protected]" export ATLASSIAN_API_TOKEN="your_api_token" # List your Confluence spaces npx -y @aashari/mcp-server-atlassian-confluence get --path "/wiki/api/v2/spaces" # Get details about a specific space npx -y @aashari/mcp-server-atlassian-confluence get --path "/wiki/api/v2/spaces/123456" # Get a page with JMESPath filtering npx -y @aashari/mcp-server-atlassian-confluence get --path "/wiki/api/v2/pages/789" --jq "{id: id, title: title, status: status}"
Add this to your Claude configuration file (~/.claude/claude_desktop_config.json):
{ "mcpServers": { "confluence": { "command": "npx", "args": ["-y", "@aashari/mcp-server-atlassian-confluence"], "env": { "ATLASSIAN_SITE_NAME": "your-company", "ATLASSIAN_USER_EMAIL": "[email protected]", "ATLASSIAN_API_TOKEN": "your_api_token" } } } }
Restart Claude Desktop, and you'll see the confluence server in the status bar.
Most AI assistants support MCP. Install the server globally:
npm install -g @aashari/mcp-server-atlassian-confluence
Then configure your AI assistant to use the MCP server with STDIO transport.
Create ~/.mcp/configs.json for system-wide configuration:
{ "confluence": { "environments": { "ATLASSIAN_SITE_NAME": "your-company", "ATLASSIAN_USER_EMAIL": "[email protected]", "ATLASSIAN_API_TOKEN": "your_api_token" } } }
Alternative config keys: The system also accepts "atlassian-confluence", "@aashari/mcp-server-atlassian-confluence", or "mcp-server-atlassian-confluence" instead of "confluence".
This MCP server provides 5 generic tools that can access any Confluence API endpoint:
| Tool | Description |
|---|---|
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 any endpoint (partial updates) |
conf_delete | DELETE any endpoint (remove resources) |
Spaces:
/wiki/api/v2/spaces - List all spaces/wiki/api/v2/spaces/{id} - Get space detailsPages:
/wiki/api/v2/pages - List pages (use space-id query param to filter)/wiki/api/v2/pages/{id} - Get page details/wiki/api/v2/pages/{id}/body - Get page body (use body-format param)/wiki/api/v2/pages/{id}/children - Get child pages/wiki/api/v2/pages/{id}/labels - Get page labelsComments:
/wiki/api/v2/pages/{id}/footer-comments - List/add footer comments/wiki/api/v2/pages/{id}/inline-comments - List/add inline comments/wiki/api/v2/footer-comments/{comment-id} - Get/update/delete commentBlog Posts:
/wiki/api/v2/blogposts - List blog posts/wiki/api/v2/blogposts/{id} - Get blog postSearch:
/wiki/rest/api/search - Search content (use cql query param)All tools support optional JMESPath (jq) filtering to extract specific data:
# Get just space names and keys npx -y @aashari/mcp-server-atlassian-confluence get \ --path "/wiki/api/v2/spaces" \ --jq "results[].{id: id, key: key, name: name}" # Get page title and status npx -y @aashari/mcp-server-atlassian-confluence get \ --path "/wiki/api/v2/pages/123456" \ --jq "{id: id, title: title, status: status}"
Ask your AI assistant:
Ask your AI assistant:
Ask your AI assistant:
Ask your AI assistant:
The CLI mirrors the MCP tools for direct terminal access:
# GET request npx -y @aashari/mcp-server-atlassian-confluence get --path "/wiki/api/v2/spaces" # GET with query parameters npx -y @aashari/mcp-server-atlassian-confluence get \ --path "/wiki/api/v2/pages" \ --query-params '{"space-id": "123456", "limit": "10"}' # POST request (create a page) npx -y @aashari/mcp-server-atlassian-confluence post \ --path "/wiki/api/v2/pages" \ --body '{"spaceId": "123456", "status": "current", "title": "New Page", "body": {"representation": "storage", "value": "<p>Content here</p>"}}' # POST request (add a comment) npx -y @aashari/mcp-server-atlassian-confluence post \ --path "/wiki/api/v2/pages/789/footer-comments" \ --body '{"body": {"representation": "storage", "value": "<p>My comment</p>"}}' # PUT request (update page - requires version increment) npx -y @aashari/mcp-server-atlassian-confluence put \ --path "/wiki/api/v2/pages/789" \ --body '{"id": "789", "status": "current", "title": "Updated Title", "spaceId": "123456", "body": {"representation": "storage", "value": "<p>Updated content</p>"}, "version": {"number": 2}}' # DELETE request npx -y @aashari/mcp-server-atlassian-confluence delete \ --path "/wiki/api/v2/pages/789"
Check your API Token permissions:
Verify your site name format:
https://mycompany.atlassian.netmycompanyTest your credentials:
npx -y @aashari/mcp-server-atlassian-confluence get --path "/wiki/api/v2/spaces?limit=1"
Check the API path:
Verify access permissions:
Try different search terms:
Check CQL syntax:
~/.claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonIf you're still having issues:
Your Atlassian account needs:
Currently, this tool only supports Confluence Cloud. Confluence Server/Data Center support may be added in future versions.
Your site name is the first part of your Confluence URL:
https://mycompany.atlassian.net -> Site name: mycompanyhttps://acme-corp.atlassian.net -> Site name: acme-corpAny AI assistant that supports the Model Context Protocol (MCP):
Yes! This tool:
Yes! Use CQL queries for cross-space searches. For example:
npx -y @aashari/mcp-server-atlassian-confluence get \ --path "/wiki/rest/api/search" \ --query-params '{"cql": "type=page AND text~\"API documentation\""}'
Version 3.0 replaces 8+ specific tools with 5 generic HTTP method tools. If you're upgrading from v2.x:
Before (v2.x):
conf_ls_spaces, conf_get_space, conf_ls_pages, conf_get_page,
conf_search, conf_ls_comments, conf_add_comment, ...
After (v3.0):
conf_get, conf_post, conf_put, conf_patch, conf_delete
Migration examples:
conf_ls_spaces -> conf_get with path /wiki/api/v2/spacesconf_get_space -> conf_get with path /wiki/api/v2/spaces/{id}conf_ls_pages -> conf_get with path /wiki/api/v2/pages?space-id={id}conf_get_page -> conf_get with path /wiki/api/v2/pages/{id}conf_search -> conf_get with path /wiki/rest/api/search?cql=...conf_add_comment -> conf_post with path /wiki/api/v2/pages/{id}/footer-commentsNeed help? Here's how to get assistance:
Made with care for teams who want to bring AI into their knowledge management workflow.