Skip to main content
Glama
GiDanis

copilot-jira-mcp

by GiDanis

๐ŸŽซ Copilot Jira MCP Server

npm version License: MIT Node.js Version

Official MCP (Model Context Protocol) server for seamless Jira integration with GitHub Copilot CLI

Interact with Jira issues, search tickets, and manage your workflow directly from GitHub Copilot CLI using natural language!


โœจ Features

  • ๐Ÿ” Smart Search - Search Jira tickets using JQL or natural language

  • ๐Ÿ“ Issue Details - Get comprehensive information about any ticket

  • ๐Ÿ’ฌ Comments - Read and analyze issue comments

  • ๐Ÿ”— Subtasks & Links - Navigate issue hierarchies

  • ๐Ÿ“Ž Attachments - List and access issue attachments

  • ๐Ÿ‘ค My Issues - Quick access to your assigned tickets

  • ๐Ÿš€ Fast & Lightweight - Minimal dependencies, maximum performance

  • ๐Ÿ” Secure - Credentials stored safely in environment variables

  • ๐ŸŒ Universal - Works with any Jira instance (Cloud or Server)

  • ๐ŸŽฏ AI-Powered - Let Copilot understand and query your Jira naturally


Related MCP server: Work Integrations MCP

๐Ÿš€ Quick Start

Prerequisites

Installation

# Install globally from GitHub
npm install -g git+https://github.com/GiDanis/copilot-jira-mcp.git

# Run interactive setup
npx jira-mcp setup

Option 2: Clone and Install

# Clone repository
git clone https://github.com/GiDanis/copilot-jira-mcp.git
cd copilot-jira-mcp

# Install dependencies
npm install

# Run setup wizard
npm run setup

# Register with Copilot
npm run register

Option 3: NPM Package

# Install from NPM
npm install -g copilot-jira-mcp

Configuration

The setup wizard will guide you through:

  1. Jira URL - Your Jira instance URL (e.g., https://your-company.atlassian.net)

  2. Email - Your Jira account email

  3. API Token - Generate at Atlassian API Tokens

Credentials are stored securely in environment variables:

  • JIRA_URL

  • JIRA_EMAIL

  • JIRA_API_TOKEN


๐Ÿ“– Usage

Once installed, simply open Copilot and use natural language:

copilot

Example Queries

Get your tickets:

> Show me my assigned Jira tickets

Search issues:

> Search Jira for open bugs in project IIAB
> Find all high priority tickets in sprint 23
> Show me tickets updated in the last week

Get ticket details:

> Get details for IIAB-12345
> Show me comments on ticket PROJ-789
> List subtasks for IIAB-456

Advanced JQL:

> Search Jira with JQL: project = IIAB AND status = "In Progress"

๐Ÿ› ๏ธ Available Tools

The MCP server exposes these tools to Copilot:

Tool

Description

jira_search

Search issues using JQL

jira_get_issue

Get detailed ticket information

jira_get_comments

Retrieve all comments

jira_get_subtasks

List all subtasks

jira_get_attachments

List attachments

jira_get_my_issues

Get your assigned tickets


๐Ÿ” Security

Your credentials are NEVER committed or shared!

โœ… Stored in environment variables
โœ… .gitignore prevents accidental commits
โœ… No plaintext storage
โœ… API tokens can be revoked anytime

Best Practices:

  • Generate dedicated API tokens (don't reuse)

  • Revoke tokens when not needed

  • Never share .env files

  • Use different tokens for different machines

See SECURITY.md for complete security guidelines.


๐Ÿ“š Documentation


๐Ÿ”ง Manual Configuration

If you prefer manual setup:

Windows (PowerShell)

# Set environment variables
[Environment]::SetEnvironmentVariable("JIRA_URL", "https://your-company.atlassian.net", "User")
[Environment]::SetEnvironmentVariable("JIRA_EMAIL", "your.email@company.com", "User")
[Environment]::SetEnvironmentVariable("JIRA_API_TOKEN", "your-token-here", "User")

# Restart terminal

Mac/Linux (Bash/Zsh)

# Add to ~/.bashrc or ~/.zshrc
export JIRA_URL="https://your-company.atlassian.net"
export JIRA_EMAIL="your.email@company.com"
export JIRA_API_TOKEN="your-token-here"

# Reload shell
source ~/.bashrc  # or ~/.zshrc

Register MCP Server

Edit ~/.copilot/mcp.json:

{
  "mcpServers": {
    "jira": {
      "command": "node",
      "args": ["/path/to/copilot-jira-mcp/src/index.js"],
      "env": {
        "JIRA_URL": "${JIRA_URL}",
        "JIRA_EMAIL": "${JIRA_EMAIL}",
        "JIRA_API_TOKEN": "${JIRA_API_TOKEN}"
      }
    }
  }
}

๐Ÿ› Troubleshooting

"Missing Jira configuration" Error

Solution: Run the setup wizard:

npm run setup

"Authentication failed" Error

Causes:

  • Invalid API token

  • Incorrect email

  • Wrong Jira URL

Solution: Regenerate API token and run setup again.

MCP Server Not Found

Solution: Re-register the server:

npm run register

For more help, see Troubleshooting Guide.


๐Ÿค Contributing

Contributions are welcome! Please see CONTRIBUTING.md for guidelines.

Areas we'd love help with:

  • ๐ŸŒ Internationalization

  • ๐Ÿ“ฑ Additional Jira features (transitions, creating tickets, etc.)

  • ๐Ÿงช Test coverage

  • ๐Ÿ“– Documentation improvements

  • ๐Ÿ› Bug fixes


๐Ÿ“œ License

MIT ยฉ 2026 Giuseppe Danise

See LICENSE for details.


๐Ÿ™ Acknowledgments


โญ Support

If this project helps you, please give it a โญ on GitHub!

Issues? Report them here
Questions? Start a discussion



Made with โค๏ธ for developers who love automation

A
license - permissive license
-
quality - not tested
D
maintenance

Maintenance

โ€“Maintainers
โ€“Response time
โ€“Release cycle
โ€“Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GiDanis/copilot-jira-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server