# aashari/mcp-server-atlassian-confluence [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/aashari/mcp-server-atlassian-confluence  
**GitHub Stars:** 63  
**npm Downloads (last month):** 37305  
**Views:** 8  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aashari-mcp-server-atlassian-confluence

## Description
Atlassian Confluence Cloud integration. Enables AI systems to interact with Confluence spaces, pages, and content with automatic ADF to Markdown conversion.

## Tools
Capabilities this server exposes over MCP:

- **conf_get** — Read any Confluence data. Returns TOON format by default (30-60% fewer tokens than JSON).

**IMPORTANT - Cost Optimization:**
- ALWAYS use `jq` param to filter response fields. Unfiltered responses are very expensive!
- Use `limit` query param to restrict result count (e.g., `limit: "5"`)
- If unsure about available fields, first fetch ONE item with `limit: "1"` and NO jq filter to explore the schema, then use jq in subsequent calls

**Schema Discovery Pattern:**
1. First call: `path: "/wiki/api/v2/spaces", queryParams: {"limit": "1"}` (no jq) - explore available fields
2. Then use: `jq: "results[*].{id: id, key: key, name: name}"` - extract only what you need

**Output format:** TOON (default, token-efficient) or JSON (`outputFormat: "json"`)

**Common paths:**
- `/wiki/api/v2/spaces` - list spaces
- `/wiki/api/v2/pages` - list pages (use `space-id` query param)
- `/wiki/api/v2/pages/{id}` - get page details
- `/wiki/api/v2/pages/{id}/body` - get page body (`body-format`: storage, atlas_doc_format, view)
- `/wiki/rest/api/search` - search content (`cql` query param)

**JQ examples:** `results[*].id`, `results[0]`, `results[*].{id: id, title: title}`

API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/
- **conf_post** — Create Confluence resources. Returns TOON format by default (token-efficient).

**IMPORTANT - Cost Optimization:**
- Use `jq` param to extract only needed fields from response (e.g., `jq: "{id: id, title: title}"`)
- Unfiltered responses include all metadata and are expensive!

**Output format:** TOON (default) or JSON (`outputFormat: "json"`)

**Common operations:**

1. **Create page:** `/wiki/api/v2/pages`
   body: `{"spaceId": "123456", "status": "current", "title": "Page Title", "parentId": "789", "body": {"representation": "storage", "value": "<p>Content</p>"}}`

2. **Create blog post:** `/wiki/api/v2/blogposts`
   body: `{"spaceId": "123456", "status": "current", "title": "Blog Title", "body": {"representation": "storage", "value": "<p>Content</p>"}}`

3. **Add label:** `/wiki/api/v2/pages/{id}/labels` - body: `{"name": "label-name"}`

4. **Add comment:** `/wiki/api/v2/pages/{id}/footer-comments`

API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/
- **conf_put** — Replace Confluence resources (full update). Returns TOON format by default.

**IMPORTANT - Cost Optimization:**
- Use `jq` param to extract only needed fields from response
- Example: `jq: "{id: id, version: version.number}"`

**Output format:** TOON (default) or JSON (`outputFormat: "json"`)

**Common operations:**

1. **Update page:** `/wiki/api/v2/pages/{id}`
   body: `{"id": "123", "status": "current", "title": "Updated Title", "spaceId": "456", "body": {"representation": "storage", "value": "<p>Content</p>"}, "version": {"number": 2}}`
   Note: version.number must be incremented

2. **Update blog post:** `/wiki/api/v2/blogposts/{id}`

Note: PUT replaces entire resource. Version number must be incremented.

API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/
- **conf_patch** — Partially update Confluence resources. Returns TOON format by default.

**IMPORTANT - Cost Optimization:** Use `jq` param to filter response fields.

**Output format:** TOON (default) or JSON (`outputFormat: "json"`)

**Common operations:**

1. **Update space:** `/wiki/api/v2/spaces/{id}`
   body: `{"name": "New Name", "description": {"plain": {"value": "Desc", "representation": "plain"}}}`

2. **Update comment:** `/wiki/api/v2/footer-comments/{id}`

Note: Confluence v2 API primarily uses PUT for updates.

API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/
- **conf_delete** — Delete Confluence resources. Returns TOON format by default.

**Output format:** TOON (default) or JSON (`outputFormat: "json"`)

**Common operations:**
- `/wiki/api/v2/pages/{id}` - Delete page
- `/wiki/api/v2/blogposts/{id}` - Delete blog post
- `/wiki/api/v2/pages/{id}/labels/{label-id}` - Remove label
- `/wiki/api/v2/footer-comments/{id}` - Delete comment
- `/wiki/api/v2/attachments/{id}` - Delete attachment

Note: Most DELETE endpoints return 204 No Content on success.

API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-server-atlassian-confluence": {
    "command": "npx",
    "args": ["-y","@aashari/mcp-server-atlassian-confluence"],
    "env": {
      "ATLASSIAN_SITE_NAME": "",
      "ATLASSIAN_USER_EMAIL": "",
      "ATLASSIAN_API_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `ATLASSIAN_SITE_NAME`, `ATLASSIAN_USER_EMAIL`, `ATLASSIAN_API_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What aashari/mcp-server-atlassian-confluence MCP server does

The aashari/mcp-server-atlassian-confluence MCP server exposes Confluence Cloud through a small set of generic tools rather than separate tools for every resource type. It can work with spaces, pages, page bodies, blog posts, labels, comments, attachments, and other endpoints available through the Confluence API.

The read operation supports common Confluence paths such as `/wiki/api/v2/spaces`, `/wiki/api/v2/pages`, page body endpoints, and `/wiki/rest/api/search` with CQL. Write operations can create pages and blog posts, add labels or comments, and update or remove resources. Page content can be converted from Atlassian Document Format to Markdown.

This fits the Workplace & Productivity category for assistants that need access to team documentation, project knowledge, policies, specifications, or support material.

## How it works

The server provides five MCP tools:

- `conf_get` sends GET requests to Confluence.
- `conf_post` creates resources with POST requests.
- `conf_put` replaces resources with PUT requests.
- `conf_patch` applies partial updates with PATCH requests.
- `conf_delete` removes resources with DELETE requests.

Each tool accepts an endpoint `path`. Optional `queryParams` pass parameters such as `limit`, `space-id`, `body-format`, or `cql`. Write tools also require a JSON `body`.

Responses are TOON by default, which the project describes as using 30–60% fewer tokens than JSON. Set `outputFormat` to `json` when standard JSON is more useful. Use the `jq` parameter to select only required fields. A practical discovery pattern is to request one result without filtering, inspect its fields, and then add a focused expression such as `results[*].{id: id, title: title}`. Limiting result counts and filtering fields helps avoid unnecessarily large responses.

## Setup and configuration

The aashari/mcp-server-atlassian-confluence MCP server uses an Atlassian site name, user email, and API token. The site name is the subdomain in an address such as `your-company.atlassian.net`.

Run it with `npx -y @aashari/mcp-server-atlassian-confluence`, or install the package globally with npm. The resulting `mcp-atlassian-confluence` binary can be configured for an assistant using STDIO transport. Claude Desktop configuration is documented using the `command`, `args`, and `env` fields.

Credentials may come from environment variables, a `.env` file in the current directory, or `~/.mcp/configs.json`. The supported credential variables are `ATLASSIAN_SITE_NAME`, `ATLASSIAN_USER_EMAIL`, and `ATLASSIAN_API_TOKEN`.

## Tools and capabilities

The aashari/mcp-server-atlassian-confluence MCP server can list and inspect spaces, retrieve pages and page bodies, find child pages and labels, search content with CQL, and access blog posts. It can also create pages or blog posts, add labels and comments, replace pages or blog posts, partially update spaces or comments, and delete pages, blog posts, labels, comments, or attachments where the relevant endpoint is available.

Confluence v2 updates generally require the complete resource for PUT requests, and page updates require an incremented version number. Most DELETE endpoints return no content on success.

## Limitations and notes

The tools map closely to Confluence API paths, so callers need the correct endpoint, parameters, request body, and resource identifiers. Unfiltered responses may contain substantial metadata and increase token use. PUT replaces the full resource rather than changing only selected fields.

_Full upstream README: https://allmcps.com/mcp/aashari-mcp-server-atlassian-confluence/readme_

