by zereight
Integrate Jira for project management and product management tasks with seamless access to Atlassian 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.
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.
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.
MIT
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Confluence and JIRA is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Confluence and JIRA has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We evaluated Confluence and JIRA against two servers with overlapping tools; this profile had the clearer scope statement.
We wired Confluence and JIRA into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Confluence and JIRA is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Confluence and JIRA has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Strong directory entry: Confluence and JIRA surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, Confluence and JIRA benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Confluence and JIRA into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated Confluence and JIRA against two servers with overlapping tools; this profile had the clearer scope statement.
showing 1-10 of 72
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:
<a href="https://glama.ai/mcp/servers/p7fnmpaukj"><img width="380" height="200" src="https://glama.ai/mcp/servers/p7fnmpaukj/badge" alt="confluence-mcp MCP server" /></a>
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
}
}
}
}
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)
/wiki/rest/api/rest/apiexecute_cql_search: Executes a CQL query on Confluence to search pages.
{
"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.
{
"type": "object",
"properties": {
"pageId": {
"type": "string",
"description": "Confluence Page ID"
}
},
"required": ["pageId"]
}
create_page: Creates a new Confluence page.
{
"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.
{
"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"]
}
execute_jql_search: Executes a JQL query on Jira to search issues.
{
"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.
{
"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.
{
"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.
{
"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.
{
"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.
{
"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.
{
"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.
{
"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.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.