Exposing Confluence's query language rather than a simplified search box means an assistant can ask for pages in one space, modified since a date, by a given author — which is how you find the right document in a wiki that has thousands. Writing is included, and it is a whole-body replacement, so treat `update_page_content` as the last step of a read-edit-write sequence rather than a way to add a line.
A small MCP server for Confluence Cloud. Search runs through CQL, Confluence's own query language, so the filtering happens on the server rather than by pulling pages down and reading them; content can then be fetched by page id and written back.
- Pages found with a CQL query, with a result limit that defaults to 10 — `execute_cql_search`
- The content of a page fetched by its page id — `get_page_content`
- A page's content replaced, optionally with a new title — `update_page_content`
An Atlassian account with access to the wiki, plus an API token created from the Atlassian security settings. Three values are needed: `CONFLUENCE_URL` for the wiki base URL, `CONFLUENCE_API_MAIL` for the account email, and `CONFLUENCE_API_KEY` for the token. The npm package name is `jira_communication_server` (0.2.0) and it is marked private, so build from a clone with `npm install` and `npm run build`, or use the Smithery installer. `update_page_content` replaces a page's body, so read the current content first if you mean to append rather than overwrite.
One command plus a key — npx -y @smithery/cli install @KS-GEN-AI/confluence-mcp-server --client claude, then supply credentials