Facilitates integration with Confluence and Jira by providing functionalities to execute queries and manage content.
Confluence Communication MCP server exists for a simple reason — assistants are far more useful when they can act on Confluence Communication directly instead of describing what you should do. Facilitates integration with Confluence and Jira by providing functionalities to execute queries and manage content.
This server implements the Model Context Protocol (MCP) for Confluence integration. This version addresses and fixes bugs found in the existing Confluence server, providing a more stable and reliable experience. It provides functionalities to execute CQL queries and retrieve page content from Confluence.
Once Confluence Communication is connected, these are the calls the assistant has available:
execute_cql_search — Executes a CQL query on Confluence to search pagesDescription — Executes a CQL query on the Confluence instance to search for pagesget_page_content — Retrieves the content of a specific Confluence pagecreate_page — Creates a new Confluence pageupdate_page — Updates an existing Confluence pageexecute_jql_search — Executes a JQL query on Jira to search issuescreate_jira_issue — Creates a new Jira issueupdate_jira_issue — Updates an existing Jira issuetransition_jira_issue — Changes the status of a Jira issueget_board_sprints — Get all sprints from a Jira boardget_sprint_issues — Get all issues from a sprintget_current_sprint — Get current active sprint from a board with its issuesYou will need 5 environment variables: CONFLUENCE_URL, JIRA_URL, CONFLUENCE_API_MAIL, CONFLUENCE_API_KEY, CONFLUENCE_IS_CLOUD. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Confluence Communication's toolset — execute_cql_search, Description, get_page_content and 11 more — is a fair guide to whether it matches your workflow. It is maintained by zereight; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| execute_cql_search | Executes a CQL query on Confluence to search pages. |
| Description | Executes a CQL query on the Confluence instance to search for pages. |
| get_page_content | Retrieves the content of a specific Confluence page. |
| create_page | Creates a new Confluence page. |
| update_page | Updates an existing Confluence page. |
| execute_jql_search | Executes a JQL query on Jira to search issues. |
| create_jira_issue | Creates a new Jira issue. |
| update_jira_issue | Updates an existing Jira issue. |
| transition_jira_issue | Changes the status of a Jira issue. |
| get_board_sprints | Get all sprints from a Jira board. |
| get_sprint_issues | Get all issues from a sprint. |
| get_current_sprint | Get current active sprint from a board with its issues. |
| get_epic_issues | Get all issues belonging to an epic. |
| get_user_issues | Get all issues assigned to or reported by a specific user in a board. |
{
"mcpServers": {
"Confluence communication server": {
"command": "npx",
"args": ["-y", "@zereight/mcp-confluence"],
"env": {
"CONFLUENCE_URL": "https://XXXXXXXX.atlassian.net",
"JIRA_URL": "https://XXXXXXXX.atlassian.net",
"CONFLUENCE_API_MAIL": "Your email",
"CONFLUENCE_API_KEY": "KEY_FROM: https://id.atlassian.com/manage-profile/security/api-tokens",
"CONFLUENCE_IS_CLOUD": "true" // Set to "false" for Server/Data Center
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CONFLUENCE_URL | Endpoint or connection string the server talks to. | Yes |
| JIRA_URL | Endpoint or connection string the server talks to. | Yes |
| CONFLUENCE_API_MAIL | Configuration value read at startup. | Optional |
| CONFLUENCE_API_KEY | Credential the server authenticates with. | Yes |
| CONFLUENCE_IS_CLOUD | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.