
Confluence and JIRA
Connects to Confluence and JIRA APIs to query documentation, pages, and project issues using CQL queries. This is a bug-fixed version providing more stable integration than existing servers.
Integrates with Confluence and JIRA APIs to enable querying and management of Atlassian project data, documentation, and issues.
What it does
- Execute CQL queries against Confluence
- Retrieve page content from Confluence
- Access JIRA project data and issues
- Query Atlassian workspace documentation
- Manage Confluence pages and content
Best for
About Confluence and JIRA
Confluence and JIRA is a community-built MCP server published by zereight that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate Jira for project management and product management tasks with seamless access to Atlassian Confluence and JIRA It is categorized under productivity.
How to install
You can install Confluence and JIRA in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
Confluence and JIRA is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Better Confluence Communication Server
Overview
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.
This server follows the MCP client-server architecture:
- Acts as an MCP server providing Confluence functionalities
- Connects to Confluence as a data source
- Communicates with MCP clients through a standardized protocol
How to use
Using with Claude App, Cline, Roo Code
When using with the Claude App, you need to set up your API key and URLs directly.
{
"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
}
}
}
}
Using with Cursor
Installing via Smithery
To install Confluence communication server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @zereight/confluence-mcp --client claude
When using with Cursor, you can set up environment variables and run the server as follows:
env [email protected] CONFLUENCE_API_KEY=your-key CONFLUENCE_URL=your-confluence-url JIRA_URL=your-jira-url npx -y @zereight/mcp-confluence
CONFLUENCE_API_MAIL: Your email address for the Confluence API.CONFLUENCE_API_KEY: Your Confluence API key.CONFLUENCE_URL: Your Confluence URL.JIRA_URL: Your JIRA URL.CONFLUENCE_IS_CLOUD: Determines Confluence version (Cloud or Server)- Default: true (Cloud version)
- Set to 'false' explicitly for Server/Data Center version
- Affects API endpoint paths:
- Cloud:
/wiki/rest/api - Server:
/rest/api
- Cloud:
Confluence Tools
-
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.
- Input Schema:
{ "type": "object", "properties": { "cql": { "type": "string", "description": "CQL query string" }, "limit": { "type": "integer", "description": "Number of results to return", "default": 10 } }, "required": ["cql"] }
-
get_page_content: Retrieves the content of a specific Confluence page.
- Description: Gets the content of a Confluence page using the page ID.
- Input Schema:
{ "type": "object", "properties": { "pageId": { "type": "string", "description": "Confluence Page ID" } }, "required": ["pageId"] }
-
create_page: Creates a new Confluence page.
- Description: Creates a new page in the specified Confluence space.
- Input Schema:
{ "type": "object", "properties": { "spaceKey": { "type": "string", "description": "Space key where the page will be created" }, "title": { "type": "string", "description": "Page title" }, "content": { "type": "string", "description": "Page content in storage format" }, "parentId": { "type": "string", "description": "Parent page ID (optional)" } }, "required": ["spaceKey", "title", "content"] }
-
update_page: Updates an existing Confluence page.
- Description: Updates the content of an existing Confluence page.
- Input Schema:
{ "type": "object", "properties": { "pageId": { "type": "string", "description": "ID of the page to update" }, "content": { "type": "string", "description": "New page content in storage format" }, "title": { "type": "string", "description": "New page title (optional)" } }, "required": ["pageId", "content"] }
Jira Tools
-
execute_jql_search: Executes a JQL query on Jira to search issues.
- Description: Executes a JQL query on the Jira instance to search for issues.
- Input Schema:
{ "type": "object", "properties": { "jql": { "type": "string", "description": "JQL query string" }, "limit": { "type": "integer", "description": "Number of results to return", "default": 10 } }, "required": ["jql"] }
-
create_jira_issue: Creates a new Jira issue.
- Description: Creates a new issue in the specified Jira project.
- Input Schema:
{ "type": "object", "properties": { "project": { "type": "string", "description": "Project key" }, "summary": { "type": "string", "description": "Issue summary" }, "description": { "type": "string", "description": "Issue description" }, "issuetype": { "type": "string", "description": "Issue type name" }, "assignee": { "type": "string", "description": "Assignee account ID" }, "priority": { "type": "string", "description": "Priority ID" } }, "required": ["project", "summary", "issuetype"] }
-
update_jira_issue: Updates an existing Jira issue.
- Description: Updates fields of an existing Jira issue.
- Input Schema:
{ "type": "object", "properties": { "issueKey": { "type": "string", "description": "Issue key (e.g., PROJ-123)" }, "summary": { "type": "string", "description": "New issue summary" }, "description": { "type": "string", "description": "New issue description" }, "assignee": { "type": "string", "description": "New assignee account ID" }, "priority": { "type": "string", "description": "New priority ID" } }, "required": ["issueKey"] }
-
transition_jira_issue: Changes the status of a Jira issue.
- Description: Changes the status of a Jira issue using transition ID.
- Input Schema:
{ "type": "object", "properties": { "issueKey": { "type": "string", "description": "Issue key (e.g. PROJ-123)" }, "transitionId": { "type": "string", "description": "Transition ID to change the issue status" } }, "required": ["issueKey", "transitionId"] }
-
get_board_sprints: Get all sprints from a Jira board.
- Description: Retrieves all sprints from a specified Jira board.
- Input Schema:
{ "type": "object", "properties": { "boardId": { "type": "string", "description": "Jira board ID" }, "state": { "type": "string", "description": "Filter sprints by state (active, future, closed)", "enum": ["active", "future", "closed"] } }, "required": ["boardId"] }
-
get_sprint_issues: Get all issues from a sprint.
- Description: Retrieves all issues from a specified sprint.
- Input Schema:
{ "type": "object", "properties": { "sprintId": { "type": "string", "description": "Sprint ID" }, "fields": { "type": "array", "items": { "type": "string" }, "description": "List of fields to return for each issue" } }, "required": ["sprintId"] }
-
get_current_sprint: Get current active sprint from a board with its issues.
- Description: Retrieves the current active sprint and its issues from a specified board.
- Input Schema:
{ "type": "object", "properties": { "boardId": { "type": "string", "description": "Jira board ID" }, "includeIssues": { "type": "boolean", "description": "Whether to include sprint issues in the response", "default": true } }, "required": ["boardId"] }
-
get_epic_issues: Get all issues belonging to an epic.
- Description: Retrieves all issues that belong to a specified epic.
- Input Schema:
{ "type": "object", "properties": { "epicKey": { "type": "string", "description": "Epic issue key (e.g. CONNECT-1234)" }, "fields": { "type": "array", "items": { "type": "string" }, "description": "List of fields to return for each issue" } }, "required": ["epicKey"] }
-
get_user_issues: Get all issues assigned to or reported by a specific user in a board.
- Description: Retrieves all issues
README truncated. View full README on GitHub.
Alternatives
Related Skills
Browse all skillsUse Atlassian MCP server to interact with Confluence (pages, spaces, search, comments). Load this when you need to perform Confluence operations. NOT for Jira - use acli for Jira.
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When Claude needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
Search across company knowledge bases (Confluence, Jira, internal docs) to find and explain internal concepts, processes, and technical details. When Claude needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture, or technical concepts, (2) Search internal documentation, knowledge base, company docs, or our docs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple sources. Searches in parallel and provides cited answers.
CLI tool for interacting with Atlassian Jira and Confluence
Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations.
Create JIRA tickets following AG project conventions. Guides you through bug reports, feature requests, and tech-debt tickets with proper formatting and required fields. Use when user asks to "create a JIRA", "file a bug", or "write up a ticket".