Atlassian Sprint MCP server

The MCP Atlassian server integrates Atlassian products (Confluence and Jira) with AI tools using the Model Context Protocol (MCP). It supports both Atlassian Cloud and Server/Data Center deployments, allowing seamless interaction with your Atlassian content through AI assistants.

Authentication Setup

For Atlassian Cloud

1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
2. Click Create API token, name it
3. Copy the token immediately

For Server/Data Center

1. Go to your profile (avatar) → Profile → Personal Access Tokens
2. Click Create token, name it, set expiry
3. Copy the token immediately

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 .

Configuration and Usage

Configure the MCP server using command line arguments. You can use either Confluence, Jira, or both services - include only the arguments needed for your use case.

Required Arguments

For Atlassian Cloud:

uvx mcp-atlassian \
  --confluence-url https://your-company.atlassian.net/wiki \
  --confluence-username [email protected] \
  --confluence-token your_api_token \
  --jira-url https://your-company.atlassian.net \
  --jira-username [email protected] \
  --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

You can configure just Confluence, just Jira, or both services by including only the arguments for the services you want to use.

Optional Arguments

• --transport: Choose transport type (stdio [default] or sse)
• --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
• --verbose: Increase logging verbosity (can be used multiple times)
• --read-only: Run in read-only mode (disables all write operations)

All configuration options can also be set via 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",
        "[email protected]",
        "--confluence-token=your_api_token",
        "--jira-url=https://your-company.atlassian.net",
        "[email protected]",
        "--jira-token=your_api_token"
      ]
    }
  }
}

Cursor IDE Setup

1. Open Cursor Settings
2. Navigate to Features > MCP Servers
3. Click Add new MCP server

For stdio transport:

name: mcp-atlassian
type: command
command: uvx mcp-atlassian --confluence-url=https://your-company.atlassian.net/wiki [email protected] --confluence-token=your_api_token --jira-url=https://your-company.atlassian.net [email protected] --jira-token=your_api_token

For SSE transport, first start the server:

uvx mcp-atlassian ... --transport sse --port 8000

Then configure in Cursor:

name: mcp-atlassian
type: sse
Server URL: http://localhost:8000/sse

Available Resources

The MCP server filters resources to only show Confluence spaces and Jira projects that the user is actively interacting with:

• confluence://{space_key}: Access Confluence spaces
• jira://{project_key}: Access Jira projects

Available Tools

Confluence Tools

• confluence_search: Search Confluence content using CQL
• confluence_get_page: Get content of a specific page
• confluence_get_page_children: Get child pages
• confluence_get_page_ancestors: Get parent pages
• confluence_get_comments: Get comments for a page
• confluence_create_page: Create a new page
• confluence_update_page: Update an existing page
• confluence_delete_page: Delete a page

Jira Tools

• jira_get_issue: Get details of a specific issue
• jira_search: Search issues using JQL
• jira_get_project_issues: Get all issues for a project
• jira_create_issue: Create a new issue
• jira_update_issue: Update an existing issue
• jira_delete_issue: Delete an issue
• jira_get_transitions: Get available status transitions
• jira_transition_issue: Change an issue's status
• jira_add_worklog: Add a worklog entry
• jira_get_worklog: Get worklog entries
• jira_link_to_epic: Link an issue to an Epic
• jira_get_epic_issues: Get all issues linked to an Epic

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.