Connecting AI Assistants to Jira and Confluence

Overview

The AMRIT Atlassian MCP Server enables AI assistants to securely access Jira and Confluence using your own credentials.

Once connected, the AI assistant can:


Prerequisites

Before connecting your AI assistant, ensure you have:


Generate Your Personal Access Tokens

Jira

  1. Log in to Jira.

  2. Open your account settings.

  3. Navigate to API Tokens / Personal Access Tokens.

  4. Create a new token.

  5. Copy and securely store the token.

Confluence

  1. Log in to Confluence.

  2. Open your account settings.

  3. Navigate to Personal Access Tokens.

  4. Create a new token.

  5. Copy and securely store the token.

Important: Treat these tokens like passwords. Do not share them with anyone.


MCP Endpoint

Use the following AMRIT Atlassian MCP endpoint:

https://amrittools.piramalswasthya.org/atlassian/mcp

Configuration

Finding the Claude Desktop Configuration File

To configure MCP servers, you need to edit the Claude Desktop configuration file.

Windows

Open File Explorer and navigate to:

%APPDATA%\Claude\claude_desktop_config.json (Win+R)

Or directly:

C:\Users\<YourUsername>\AppData\Roaming\Claude\claude_desktop_config.json

macOS

Open Finder and navigate to:

~/Library/Application Support/Claude/claude_desktop_config.json

Linux

Navigate to:

~/.config/Claude/claude_desktop_config.json

Opening the Configuration File

You can open the file using any text editor such as:


Add the following MCP configuration to your AI Client if you are using Claude code. 

{
  "mcpServers": {
    "mcp-atlassian": {
      "type": "http",
      "url": "https://amrittools.piramalswasthya.org/atlassian/mcp",
      "headers": {
        "X-Atlassian-Jira-Url": "https://support.piramalfoundation.org/jira",
        "X-Atlassian-Jira-Personal-Token": "<YOUR_JIRA_TOKEN>",
        "X-Atlassian-Confluence-Url": "https://pmp.piramalswasthya.org/confluence",
        "X-Atlassian-Confluence-Personal-Token": "<YOUR_CONFLUENCE_TOKEN>"
      }
    }
  }
}

Claude Desktop MCP Configuration

If you are using Claude Desktop use this configuration.



Open the Claude Desktop configuration file and add the following content inside the file.


{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "npx.cmd",
      "args": [
        "-y",
        "mcp-remote",
        "https://amrittools.piramalswasthya.org/atlassian/mcp",
        "--header",
        "X-Atlassian-Jira-Url: https://support.piramalfoundation.org/jira",
        "--header",
        "X-Atlassian-Jira-Personal-Token: <YOUR_JIRA_TOKEN>",
        "--header",
        "X-Atlassian-Confluence-Url: https://pmp.piramalswasthya.org/confluence",
        "--header",
        "X-Atlassian-Confluence-Personal-Token: <YOUR_CONFLUENCE_TOKEN>"
      ]
    }
  }
}

Replace:


with your own credentials(which you just created from Jira and Confluence).

After updating the configuration, completely close(Verify that Claude Desktop is no longer running in Task Manager) and reopen Claude Desktop for the changes to take effect.


Jira Capabilities Available Through the Atlassian MCP Server

The Atlassian MCP Server provides access to Jira project data, issue tracking, agile boards, service management, reporting, and collaboration features through natural language interactions.


Jira Issues

Used for managing Jira work items.

Capabilities include:

Typical use cases:


Jira Search & Fields

Used for discovering and querying Jira metadata.

Capabilities include:

Typical use cases:


Jira Agile

Used for Agile project management.

Capabilities include:

Typical use cases:


Jira Links & Versions

Used for dependency and release management.

Capabilities include:

Typical use cases:


Jira Comments & Worklogs

Used for collaboration and effort tracking.

Capabilities include:

Typical use cases:


Jira Attachments

Used for managing files associated with issues.

Capabilities include:

Typical use cases:


Jira Service Management

Used for support and service desk operations.

Capabilities include:

Typical use cases:


Jira Forms & Metrics

Used for reporting and project analytics.

Capabilities include:

Typical use cases:


Confluence Capabilities Available Through the Atlassian MCP Server

The Atlassian MCP Server provides access to Confluence knowledge bases, project documentation, attachments, comments, and enterprise search capabilities through natural language interactions.


Confluence Pages

Used for creating, reading, updating, and managing Confluence pages.

Capabilities include:

Typical use cases:


Confluence Search

Used for discovering information across Confluence spaces.

Capabilities include:

Typical use cases:


Confluence Attachments

Used for managing files stored within Confluence pages.

Capabilities include:

Typical use cases:


Confluence Comments

Used for collaboration and discussion around documentation.

Capabilities include:

Typical use cases:


Common Business Use Cases

Business Analysts (BSA)

Project Managers

Scrum Masters

Product Owners

Technical Teams


Security Model

All Confluence operations are performed using the user's own credentials.

Users can only access:

The MCP server does not grant additional permissions beyond those already assigned within Confluence.


Example Prompts

After connecting successfully, you can ask:

Jira

Confluence


Security Considerations


Troubleshooting

Authentication Errors

Verify:

Unable to Access Tickets or Pages

Verify:

Connection Issues

Verify:


Support

For issues related to MCP connectivity or access, contact the AMRIT Agentic AI Framework team and provide: