Atlassian

MCP to integrate with JIRA & CONFLUENCE
  • javascript

1

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "kompallik-atlassian-mcp": {
      "command": "atlassian-mcp-server",
      "args": [],
      "env": {
        "ATLASSIAN_EMAIL": "user@example.com",
        "ATLASSIAN_TOKEN": "abcd1234token",
        "ATLASSIAN_BASE_URL": "https://your-instance.atlassian.net",
        "ATLASSIAN_CONFIG_PATH": "/path/to/your/config.json"
      }
    }
  }
}

You set up and run an MCP server that plugs Atlassian JIRA and Confluence into your MCP workflow. This server lets you fetch ticket details, search and create tickets, add comments, and access Confluence pages and search content, all through MCP-compatible clients.

How to use

Start the Atlassian MCP Server and connect it to your MCP client. Once running, your MCP client can invoke tools to retrieve JIRA ticket details, search tickets with JQL, create new tickets, add comments, and access Confluence content. Use the server to streamline project work by automating common JIRA and Confluence interactions via MCP commands.

How to install

Prerequisites you need before installation include Node.js 16 or higher, an Atlassian Cloud account, and an Atlassian API token.

# Option 2: Install from npm
npm install -g atlassian-mcp-server

# Option 3: Install from source
# 1. Clone the repository
# 2. Run the install script:
./install.sh

# Or manually:
# 1. Install dependencies
npm install
# 2. Build the project
npm run build
# 3. Install globally
npm install -g .
# 4. Run the setup
atlassian-mcp-setup

Configuration

Configure the server using the setup script, a configuration file, or environment variables. The setup script can guide you to create a configuration file named config.json in the config directory. You can also provide Atlassian details directly in a manual configuration.

Environment variables you may use include Atlassian base URL, email, and token. You can also specify a custom config path if needed.

{
  "atlassian": {
    "baseUrl": "https://your-instance.atlassian.net",
    "email": "your-email@example.com",
    "token": "your-api-token-here"
  },
  "server": {
    "name": "atlassian-server",
    "version": "0.1.0"
  }
}

Getting an Atlassian API Token

Log in to your Atlassian account, navigate to the API tokens security page, create a token, and copy it for use with the MCP server.

Usage

Run the server locally and connect it to your MCP client. Use the client to call Atlassian-related tools for tickets and Confluence pages.

# Running the server (example)
atlassian-mcp-server

# If installed from source
npm start

Security considerations

Protect your Atlassian API token and limit token permissions to the minimum required for your MCP use cases. Store tokens securely and consider using environment variables or a secrets manager in production.

Troubleshooting

If you encounter authentication errors, verify your base URL, email, and token. Ensure the token has the necessary scopes for JIRA and Confluence access. Confirm your MCP client is configured to reach the running Atlassian MCP Server.

Available tools

get_jira_ticket

Retrieve details of a JIRA ticket by key.

search_jira_tickets

Search for JIRA tickets using a JQL query.

create_jira_ticket

Create a new JIRA ticket with a project key, summary, description, and type.

add_comment_to_jira_ticket

Add a comment to a JIRA ticket.

get_confluence_page

Get content of a Confluence page by its ID.

search_confluence

Search Confluence content using a query.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational