← Back to directory
A

Atlassian Confluence MCP Server

Community
Connect AI assistants directly to your Confluence knowledge base
GitHub source repository ↗
★ 61 Stars Category · Collaboration Popular Source revision 13f3b4fdf75d
37FMRS · D
Reliability
6/20
Security and permissions
8/20
Maintenance
8/20
Documentation
8/20
Setup experience
7/20

This server provides a flexible way to connect AI assistants to Confluence with comprehensive access via generic API methods. TOON format and JMESPath filtering help control token costs. However, it requires careful credential management and recommends always using filtering to avoid unexpected large responses.

Read the FMRS scoring method →

This MCP server allows AI assistants (such as Claude, Cursor AI, etc.) to interact with Atlassian Confluence through the standard MCP interface. It provides five generic tools (conf_get, conf_post, conf_put, conf_patch, conf_delete) that can access any Confluence API endpoint, enabling AI to read, search, create, update, and delete spaces, pages, comments, and blog posts. Output defaults to TOON format for 30-60% token reduction and supports JMESPath filtering to extract only needed fields.

Tools

conf_get
Send a GET request to any Confluence API endpoint to read data.
conf_post
Send a POST request to create resources (e.g., pages, comments).
conf_put
Send a PUT request to replace resources (e.g., update a page).
conf_patch
Send a PATCH request to partially update resources (e.g., rename a space).
conf_delete
Send a DELETE request to delete resources.

Setup

  1. Generate an API token in your Atlassian account (https://id.atlassian.com/manage-profile/security/api-tokens).
  2. Set environment variables: ATLASSIAN_SITE_NAME (e.g., your-company), ATLASSIAN_USER_EMAIL, ATLASSIAN_API_TOKEN.
  3. For Claude Desktop, edit ~/.claude/claude_desktop_config.json and add the mcpServers configuration above.
  4. Restart Claude Desktop or configure other MCP-compatible assistants (e.g., Cursor, Continue.dev).
  5. Alternatively, run directly with npx -y @aashari/mcp-server-atlassian-confluence for CLI commands.
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"
      }
    }
  }
}

Fit and risk

Best for

  • Developers who need quick access to technical documentation and API guides
  • Product managers searching for requirements, specs, and project updates
  • HR teams accessing policy documents and employee resources quickly
  • Support teams finding troubleshooting guides and knowledge base articles
  • Anyone who wants to interact with Confluence using natural language

Not for

  • Users on Confluence Server or Data Center (on-premise), as this tool supports only Confluence Cloud.
  • Legacy users expecting specific domain tools (like conf_ls_spaces), but v3.0 migrated to generic HTTP method tools.

Required permissions

  • Requires an Atlassian account with access to Confluence and the spaces you want to query.
  • Requires an API token (permissions granted automatically upon creation).
  • The server uses your own credentials and runs locally.

Risks and side effects

  • Token leakage risk: If your API token is compromised, others may access your Confluence data. Store it securely.
  • Data access scope: AI assistants can read and modify all content you have permission to access, including create, update, delete.
  • Large responses can lead to high token costs: always use jq filtering and limit parameters to avoid unexpected costs.
  • Response truncation: Responses exceeding ~40,000 characters are truncated, and the full raw data is saved to a temporary file.

Troubleshooting

  1. Authentication failed or 403: Check that the API token is still active, site name format is correct (e.g., 'mycompany' not 'https://mycompany.atlassian.net'), and verify credentials.
  2. Resource not found (404): Check path case sensitivity, use numeric IDs (not keys), and ensure you have permissions.
  3. No results when searching: Try different search terms, use proper CQL syntax, and validate in Confluence.
  4. Claude Desktop integration issues: Restart Claude, check config file path (macOS: ~/.claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json).
  5. Enable debugging with DEBUG=true for detailed logs, stored at ~/.mcp/data/@aashari-mcp-server-atlassian-confluence.[session-id].log.

Use cases

Ask AI about documentation: "What's our API authentication process?"
Search across all spaces: "Find all pages about security best practices"
Get instant answers: "Show me the latest release notes from the Product space"
Access team knowledge: "What are our HR policies for remote work?"
Review page comments: "Show me the discussion on the architecture document"
Create and update content: "Create a new page in the DEV space"

Supported clients

Claude DesktopFull support
Cursor AIFull support
Continue.devFull support