MCP server for Atlassian tools (Confluence, Jira)
Model Context Protocol (MCP) server for Atlassian Cloud products (Confluence and Jira). This integration is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments.
Note: The MCP server filters resources to only show Confluence spaces and Jira projects that the user is actively interacting with, based on their contributions and assignments. This makes the integration more efficient and focused on relevant content.
confluence://{space_key}
: Access Confluence spacesjira://{project_key}
: Access Jira projectsconfluence_search
query
(string): CQL query stringlimit
(number, optional): Results limit (1-50, default: 10)confluence_get_page
page_id
(string): Confluence page IDinclude_metadata
(boolean, optional): Include page metadata (default: true)confluence_get_comments
page_id
(string): Confluence page IDconfluence_create_page
space_key
(string): The key of the space to create the page intitle
(string): The title of the pagecontent
(string): The content of the page in Markdown formatparent_id
(string, optional): Optional parent page IDconfluence_update_page
page_id
(string): The ID of the page to updatetitle
(string): The new title of the pagecontent
(string): The new content of the page in Markdown formatminor_edit
(boolean, optional): Whether this is a minor edit (default: false)version_comment
(string, optional): Optional comment for this version (default: “”)jira_get_issue
issue_key
(string): Jira issue key (e.g., ‘PROJ-123’)expand
(string, optional): Fields to expandcomment_limit
(integer, optional): Maximum number of comments to include (0 or null for no comments)jira_search
jql
(string): JQL query stringfields
(string, optional): Comma-separated fields (default: “*all”)limit
(number, optional): Results limit (1-50, default: 10)jira_get_project_issues
project_key
(string): Project keylimit
(number, optional): Results limit (1-50, default: 10)jira_create_issue
project_key
(string): The JIRA project key (e.g. ‘PROJ’)summary
(string): Summary/title of the issueissue_type
(string): Issue type (e.g. ‘Task’, ‘Bug’, ‘Story’)description
(string, optional): Issue descriptionadditional_fields
(string, optional): JSON string of additional fieldsjira_update_issue
issue_key
(string): Jira issue keyfields
(string): JSON object of fields to updateadditional_fields
(string, optional): JSON string of additional fieldsjira_delete_issue
issue_key
(string): Jira issue key (e.g. PROJ-123)On macOS:
brew install uv
When using uv
, no specific installation is needed. We will use uvx
to directly run mcp-atlassian.
uvx mcp-atlassian
Alternatively you can install mcp-atlassian via pip:
pip install mcp-atlassian
To install Atlassian Integration for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install mcp-atlassian --client claude
The MCP Atlassian integration supports using either Confluence, Jira, or both services. You only need to provide the environment variables for the service(s) you want to use.
Get API tokens from: https://id.atlassian.com/manage-profile/security/api-tokens
Add to your claude_desktop_config.json
using one of the following methods:
Note: For all configuration methods, include only the environment variables needed for your services:
- For Confluence only: Include
CONFLUENCE_URL
,CONFLUENCE_USERNAME
, andCONFLUENCE_API_TOKEN
- For Jira only: Include
JIRA_URL
,JIRA_USERNAME
, andJIRA_API_TOKEN
- For both services: Include all six variables
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": ["mcp-atlassian"],
"env": {
"CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "[email protected]",
"CONFLUENCE_API_TOKEN": "your_api_token",
"JIRA_URL": "https://your-domain.atlassian.net",
"JIRA_USERNAME": "[email protected]",
"JIRA_API_TOKEN": "your_api_token"
}
}
}
}
{
"mcpServers": {
"mcp-atlassian": {
"command": "python",
"args": ["-m", "mcp-atlassian"],
"env": {
"CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "[email protected]",
"CONFLUENCE_API_TOKEN": "your_api_token",
"JIRA_URL": "https://your-domain.atlassian.net",
"JIRA_USERNAME": "[email protected]",
"JIRA_API_TOKEN": "your_api_token"
}
}
}
}
There are two ways to configure the Docker environment:
{
"mcpServers": {
"mcp-atlassian": {
"command": "docker",
"args": ["run", "--rm", "-i", "mcp/atlassian"],
"env": {
"CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "[email protected]",
"CONFLUENCE_API_TOKEN": "your_api_token",
"JIRA_URL": "https://your-domain.atlassian.net",
"JIRA_USERNAME": "[email protected]",
"JIRA_API_TOKEN": "your_api_token"
}
}
}
}
{
"mcpServers": {
"mcp-atlassian": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--env-file",
"/path/to/your/.env",
"mcp/atlassian"
]
}
}
}
The .env file should contain:
CONFLUENCE_URL=https://your-domain.atlassian.net/wiki
[email protected]
CONFLUENCE_API_TOKEN=your_api_token
JIRA_URL=https://your-domain.atlassian.net
[email protected]
JIRA_API_TOKEN=your_api_token
To integrate the MCP server with Cursor IDE:
Configure the server:
Features
> MCP Servers
Add new MCP server
name: mcp-atlassian
type: command
command: uvx mcp-atlassian --confluence-url=https://your-domain.atlassian.net/wiki [email protected] --confluence-token=your_api_token --jira-url=https://your-domain.atlassian.net [email protected] --jira-token=your_api_token
If you’ve cloned the repository and want to run a local version of mcp-atlassian
:
Configure in Claude Desktop:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uv",
"args": [
"--directory", "/path/to/your/mcp-atlassian",
"run", "mcp-atlassian",
"--confluence-url=https://your-domain.atlassian.net",
"[email protected]",
"--confluence-token=your_api_token",
"--jira-url=https://your-domain.atlassian.net",
"[email protected]",
"--jira-token=your_api_token"
]
}
}
}
You can use the MCP inspector to debug the server:
npx @modelcontextprotocol/inspector uvx mcp-atlassian
For development installations:
cd path/to/mcp-atlassian
npx @modelcontextprotocol/inspector uv run mcp-atlassian
View logs with:
tail -n 20 -f ~/Library/Logs/Claude/mcp*.log
For local development testing:
Docker build:
docker build -t mcp/atlassian .
Licensed under MIT - see LICENSE{:target=“_blank”} file. This is not an official Atlassian product.
Mcp Llms Txt Explorer
MCP to explore websites with llms.txt files
Mcp Codex Keeper
An intelligent MCP server that serves as a guardian of development knowledge, providing Cline assistants with curated access to latest documentation and best practices across the software development landscape
Mcp Command Proxy