Atlassian Integration Featured
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.
sooperset
Tools
confluence_search
Search Confluence content using simple terms or CQL
confluence_get_page
Get content of a specific Confluence page by ID
confluence_get_page_children
Get child pages of a specific Confluence page
confluence_get_page_ancestors
Get ancestor (parent) pages of a specific Confluence page
confluence_get_comments
Get comments for a specific Confluence page
confluence_create_page
Create a new Confluence page
confluence_update_page
Update an existing Confluence page
confluence_delete_page
Delete an existing Confluence page
confluence_attach_content
Attach content to a Confluence page
jira_get_issue
Get details of a specific Jira issue including its Epic links and relationship information
jira_update_issue
Update an existing Jira issue including changing status, adding Epic links, updating fields, etc.
jira_search
Search Jira issues using JQL (Jira Query Language)
jira_get_project_issues
Get all issues for a specific Jira project
jira_get_epic_issues
Get all issues linked to a specific epic
jira_get_transitions
Get available status transitions for a Jira issue
jira_get_worklog
Get worklog entries for a Jira issue
jira_download_attachments
Download attachments from a Jira issue
jira_get_agile_boards
Get jira agile boards by name, project key, or type
jira_get_board_issues
Get all issues linked to a specific board
jira_get_sprints_from_board
Get jira sprints from board by state
jira_get_sprint_issues
Get jira issues from sprint
jira_create_issue
Create a new Jira issue with optional Epic link or parent for subtasks
jira_delete_issue
Delete an existing Jira issue
jira_add_comment
Add a comment to a Jira issue
jira_add_worklog
Add a worklog entry to a Jira issue
jira_link_to_epic
Link an existing issue to an epic
jira_transition_issue
Transition a Jira issue to a new status
README
MCP Atlassian
Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). This integration supports both Confluence & Jira Cloud and Server/Data Center deployments.
Feature Demo
<details> <summary>Confluence Demo</summary>
https://github.com/user-attachments/assets/7fe9c488-ad0c-4876-9b54-120b666bb785
</details>
Compatibility
Product | Deployment Type | Support Status |
---|---|---|
Confluence | Cloud | ✅ Fully supported |
Confluence | Server/Data Center | ✅ Supported (version 6.0+) |
Jira | Cloud | ✅ Fully supported |
Jira | Server/Data Center | ✅ Supported (version 8.14+) |
Setup Guide
1. Authentication Setup
First, generate the necessary authentication tokens for Confluence & Jira:
For Cloud
- Go to https://id.atlassian.com/manage-profile/security/api-tokens
- Click Create API token, name it
- Copy the token immediately
For Server/Data Center
- Go to your profile (avatar) → Profile → Personal Access Tokens
- Click Create token, name it, set expiry
- Copy the token immediately
2. Installation
Choose one of these installation methods:
# Using uv (recommended)
brew install uv
uvx mcp-atlassian
# Using pip
pip install mcp-atlassian
# Using Docker
git clone https://github.com/sooperset/mcp-atlassian.git
cd mcp-atlassian
docker build -t mcp/atlassian .
# Using Smithery
npx -y @smithery/cli install mcp-atlassian --client claude
3. Configuration and Usage
You can configure the MCP server using command line arguments. The server supports using either Confluence, Jira, or both services - include only the arguments needed for your use case.
Required Arguments
For Cloud:
uvx mcp-atlassian \
--confluence-url https://your-company.atlassian.net/wiki \
--confluence-username your.email@company.com \
--confluence-token your_api_token \
--jira-url https://your-company.atlassian.net \
--jira-username your.email@company.com \
--jira-token your_api_token
For Server/Data Center:
uvx mcp-atlassian \
--confluence-url https://confluence.your-company.com \
--confluence-personal-token your_token \
--jira-url https://jira.your-company.com \
--jira-personal-token your_token
Note: You can configure just Confluence, just Jira, or both services. Simply include only the arguments for the service(s) you want to use. For example, to use only Confluence Cloud, you would only need
--confluence-url
,--confluence-username
, and--confluence-token
.
Optional Arguments
--transport
: Choose transport type (stdio
[default] orsse
)--port
: Port number for SSE transport (default: 8000)--[no-]confluence-ssl-verify
: Toggle SSL verification for Confluence Server/DC--[no-]jira-ssl-verify
: Toggle SSL verification for Jira Server/DC--confluence-spaces-filter
: Comma-separated list of space keys to filter Confluence search results (e.g., "DEV,TEAM,DOC")--jira-projects-filter
: Comma-separated list of project keys to filter Jira search results (e.g., "PROJ,DEV,SUPPORT")--read-only
: Run in read-only mode (disables all write operations)--verbose
: Increase logging verbosity (can be used multiple times, default is WARNING level)-v
or--verbose
: Set logging to INFO level-vv
or--verbose --verbose
: Set logging to DEBUG level
Note: All configuration options can also be set via environment variables. See the
.env.example
file in the repository for the full list of available environment variables.
IDE Integration
Claude Desktop Setup
Using uvx (recommended) - Cloud:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian",
"--confluence-url=https://your-company.atlassian.net/wiki",
"--confluence-username=your.email@company.com",
"--confluence-token=your_api_token",
"--jira-url=https://your-company.atlassian.net",
"--jira-username=your.email@company.com",
"--jira-token=your_api_token"
]
}
}
}
<details> <summary>Using uvx (recommended) - Server/Data Center </summary>
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian",
"--confluence-url=https://confluence.your-company.com",
"--confluence-personal-token=your_token",
"--jira-url=https://jira.your-company.com",
"--jira-personal-token=your_token"
]
}
}
}
</details>
<details> <summary>Using uvx - Confluence with Basic Auth (older servers)</summary>
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian",
"--confluence-url=https://confluence.your-company.com",
"--confluence-username=your.email@company.com",
"--confluence-token=your_password"
]
}
}
}
</details>
<details> <summary>Using uvx - Confluence only</summary>
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian",
"--confluence-url=https://your-company.atlassian.net/wiki",
"--confluence-username=your.email@company.com",
"--confluence-token=your_api_token"
]
}
}
}
</details>
<details> <summary>Using uvx - Jira only</summary>
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian",
"--jira-url=https://your-company.atlassian.net",
"--jira-username=your.email@company.com",
"--jira-token=your_api_token"
]
}
}
}
</details>
<details> <summary>Using pip</summary>
Note: Examples below use Cloud configuration. For Server/Data Center, use the corresponding arguments (--confluence-personal-token, --jira-personal-token) as shown in the Configuration section above.
{
"mcpServers": {
"mcp-atlassian": {
"command": "mcp-atlassian",
"args": [
"--confluence-url=https://your-company.atlassian.net/wiki",
"--confluence-username=your.email@company.com",
"--confluence-token=your_api_token",
"--jira-url=https://your-company.atlassian.net",
"--jira-username=your.email@company.com",
"--jira-token=your_api_token"
]
}
}
}
</details>
<details> <summary>Using docker</summary>
Note: Examples below use Cloud configuration. For Server/Data Center, use the corresponding arguments (--confluence-personal-token, --jira-personal-token) as shown in the Configuration section above.
There are two ways to configure the Docker environment:
- Using cli arguments directly in the config:
{
"mcpServers": {
"mcp-atlassian": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"mcp/atlassian",
"--confluence-url=https://your-company.atlassian.net/wiki",
"--confluence-username=your.email@company.com",
"--confluence-token=your_api_token",
"--jira-url=https://your-company.atlassian.net",
"--jira-username=your.email@company.com",
"--jira-token=your_api_token"
]
}
}
}
- Using an environment file:
{
"mcpServers": {
"mcp-atlassian": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--env-file",
"/path/to/your/.env",
"mcp/atlassian"
]
}
}
}
</details>
Cursor IDE Setup
- Open Cursor Settings
- Navigate to
Features
>MCP Servers
(or directly toMCP
) - Click
+ Add new global MCP server
This will create or edit the ~/.cursor/mcp.json
file with your MCP server configuration.
JSON Configuration for stdio Transport
For Cloud:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian",
"--confluence-url=https://your-company.atlassian.net/wiki",
"--confluence-username=your.email@company.com",
"--confluence-token=your_api_token",
"--jira-url=https://your-company.atlassian.net",
"--jira-username=your.email@company.com",
"--jira-token=your_api_token"
]
}
}
}
<details> <summary>Server/Data Center Configuration</summary>
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian",
"--confluence-url=https://confluence.your-company.com",
"--confluence-personal-token=your_token",
"--jira-url=https://jira.your-company.com",
"--jira-personal-token=your_token"
]
}
}
}
</details>
SSE Transport Configuration
For SSE transport, first start the server with its configuration provided via command-line arguments or server-side environment variables (e.g., from a .env
file):
# Example starting the server with Cloud configuration
uvx mcp-atlassian --transport sse --port 9000 \
--confluence-url https://your-company.atlassian.net/wiki \
--confluence-username your.email@company.com \
--confluence-token your_api_token \
--jira-url https://your-company.atlassian.net \
--jira-username your.email@company.com \
--jira-token your_api_token
Then configure only the URL in Cursor's ~/.cursor/mcp.json
:
{
"mcpServers": {
"mcp-atlassian-sse": {
"url": "http://localhost:9000/sse"
}
}
}
Resources
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.
confluence://{space_key}
: Access Confluence spacesjira://{project_key}
: Access Jira projects
Available Tools
Tool | Description |
---|---|
confluence_search |
Search Confluence content using CQL |
confluence_get_page |
Get content of a specific Confluence page |
confluence_get_page_children |
Get child pages of a specific Confluence page |
confluence_get_page_ancestors |
Get parent pages of a specific Confluence page |
confluence_get_comments |
Get comments for a specific Confluence page |
confluence_create_page |
Create a new Confluence page |
confluence_update_page |
Update an existing Confluence page |
confluence_delete_page |
Delete an existing Confluence page |
confluence_attach_content |
Attach content to a Confluence page |
jira_get_issue |
Get details of a specific Jira issue |
jira_search |
Search Jira issues using JQL |
jira_get_project_issues |
Get all issues for a specific Jira project |
jira_get_epic_issues |
Get all issues linked to a specific Epic |
jira_create_issue |
Create a new issue in Jira |
jira_update_issue |
Update an existing Jira issue |
jira_delete_issue |
Delete an existing Jira issue |
jira_get_transitions |
Get available status transitions for a Jira issue |
jira_transition_issue |
Transition a Jira issue to a new status |
jira_add_comment |
Add a comment to a Jira issue |
jira_add_worklog |
Add a worklog entry to a Jira issue |
jira_get_worklog |
Get worklog entries for a Jira issue |
jira_download_attachments |
Download attachments from a Jira issue |
jira_link_to_epic |
Link an issue to an Epic |
jira_get_agile_boards |
Get Jira agile boards by name, project key, or type |
jira_get_board_issues |
Get all issues linked to a specific board |
jira_get_sprints_from_board |
Get Jira sprints from board by state |
jira_get_sprint_issues |
Get Jira issues from sprint |
Development & Debugging
Local Development Setup
If you've cloned the repository and want to run a local version:
For Cloud:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uv",
"args": [
"--directory", "/path/to/your/mcp-atlassian",
"run", "mcp-atlassian",
"--confluence-url=https://your-domain.atlassian.net/wiki",
"--confluence-username=your.email@domain.com",
"--confluence-token=your_api_token",
"--jira-url=https://your-domain.atlassian.net",
"--jira-username=your.email@domain.com",
"--jira-token=your_api_token"
]
}
}
}
Debugging Tools
# Using MCP Inspector
# For installed package
npx @modelcontextprotocol/inspector uvx mcp-atlassian ...
# For local development version
npx @modelcontextprotocol/inspector uv --directory /path/to/your/mcp-atlassian run mcp-atlassian ...
# View logs
tail -n 20 -f ~/Library/Logs/Claude/mcp*.log
Security
- Never share API tokens
- Keep .env files secure and private
- See SECURITY.md for best practices
License
Licensed under MIT - see LICENSE file. This is not an official Atlassian product.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
AIO-MCP Server
🚀 All-in-one MCP server with AI search, RAG, and multi-service integrations (GitLab/Jira/Confluence/YouTube) for AI-enhanced development workflows. Folk from
React MCP
react-mcp integrates with Claude Desktop, enabling the creation and modification of React apps based on user prompts

Any OpenAI Compatible API Integrations
Integrate Claude with Any OpenAI SDK Compatible Chat Completion API - OpenAI, Perplexity, Groq, xAI, PyroPrompts and more.
MySQL Server
Allows AI assistants to list tables, read data, and execute SQL queries through a controlled interface, making database exploration and analysis safer and more structured.
Browser Use (used by Deploya.dev)
AI-driven browser automation server that implements the Model Context Protocol to enable natural language control of web browsers for tasks like navigation, form filling, and visual interaction.
Aindreyway Codex Keeper
Serves as a guardian of development knowledge, providing AI assistants with curated access to latest documentation and best practices.

OpenRouter MCP Server
Provides integration with OpenRouter.ai, allowing access to various AI models through a unified interface.