Suggest a server AI tools directory →

Confluence MCP server

Last verified: 2026-09

Read Confluence pages.

Community Chat, mail & docs Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code

What it does

Same author's generic HTTP wrapper, for Confluence (conf_get/post/put/patch/delete). Reads and writes spaces and pages the token can see.

It sits in Chat, mail & docs: These servers act as the bot or the integration you install.

Good for

  • conf_get a space you own and one page, not the company wiki root.
  • Search for a runbook you know exists.
  • Draft a page in a sandbox space, then you move it.
  • Keep conf_delete off the mental default.

Tools

  • conf_get — Read spaces, pages, search.
  • conf_post / conf_put / conf_patch — Create or edit pages.
  • conf_delete — Remove pages or spaces the token allows.

Config (Claude Desktop / Cursor / Windsurf)

Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets. Windows paths look like C:\\Users\\you\\project, not /path/to. Host-side steps →

Claude Desktop

OSConfig file
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json (usually C:\Users\<you>\AppData\Roaming\Claude\)
Linux~/.config/Claude/claude_desktop_config.json

Cursor

ScopemacOS / LinuxWindows
This project.cursor/mcp.json in the repo root
This user~/.cursor/mcp.json %USERPROFILE%\.cursor\mcp.json

Windsurf

OSConfig file
macOS / Linux~/.codeium/windsurf/mcp_config.json
Windows%USERPROFILE%\.codeium\windsurf\mcp_config.json
{
  "mcpServers": {
    "confluence": {
      "command": "npx",
      "args": [
        "-y",
        "@aashari/mcp-server-atlassian-confluence"
      ],
      "env": {
        "ATLASSIAN_SITE": "yourhost.atlassian.net",
        "ATLASSIAN_EMAIL": "[email protected]",
        "ATLASSIAN_API_TOKEN": "..."
      }
    }
  }
}

Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.

One-liner: npx -y @aashari/mcp-server-atlassian-confluence

Secrets it wants: ATLASSIAN_SITE, ATLASSIAN_EMAIL, ATLASSIAN_API_TOKEN

Source repo →

How to get started

  1. Same Atlassian email + API token as Jira, or a Confluence-only token.
  2. conf_get a space you own first. Do not point it at the company wiki root.
  3. Keep delete off the mental default.

Access risk

Wiki write/delete. Internal runbooks should not be editable by a confused model.

When to skip it

Skip it for Notion or a local vault. Pair with Jira only if you already live in Atlassian.

Instead: Notion, Jira, Google Drive.

Vs alternatives

ServerOfficial?Needs a secret?Best for
ConfluenceNoYesRead Confluence pages.
NotionNoYesSearch and update Notion pages.
JiraNoYesJira issues and JQL search.
Google DriveYesYesList and read files from a Google Drive account.

More in Chat, mail & docs

All 18 in this category →

FAQ

Same token as Jira?

Often yes (Atlassian email + API token). That means one leak is wiki + tickets. Prefer a Confluence-only token if you can.

Same generic verbs as Jira?

Yes — conf_get/post/put/patch/delete. Not a curated 'get page' wrapper.

Confluence or Notion?

Whichever wiki you already have. Do not sync both write paths.

Can it edit official runbooks?

If the token can. Invite it to a space you can afford to mess up.