copilot-jira-mcp
v1.0.0
Published
Official MCP Server for Jira integration with GitHub Copilot CLI
Maintainers
Readme
🎫 Copilot Jira MCP Server
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
🚀 Quick Start
Prerequisites
- Node.js 18 or higher (Download)
- GitHub Copilot CLI (Setup Guide)
- Jira Account with API access
Installation
Option 1: NPM (Recommended)
# Install globally
npm install -g copilot-jira-mcp
# Run interactive setup
jira-mcp setup
# Register with Copilot
jira-mcp registerOption 2: From Source
# Clone repository
git clone https://github.com/gdanise/copilot-jira-mcp.git
cd copilot-jira-mcp
# Install dependencies
npm install
# Run setup wizard
npm run setup
# Register with Copilot
npm run registerConfiguration
The setup wizard will guide you through:
- Jira URL - Your Jira instance URL (e.g.,
https://your-company.atlassian.net) - Email - Your Jira account email
- API Token - Generate at Atlassian API Tokens
Credentials are stored securely in environment variables:
JIRA_URLJIRA_EMAILJIRA_API_TOKEN
📖 Usage
Once installed, simply open Copilot and use natural language:
copilotExample Queries
Get your tickets:
> Show me my assigned Jira ticketsSearch issues:
> Search Jira for open bugs in project IIAB
> Find all high priority tickets in sprint 23
> Show me tickets updated in the last weekGet ticket details:
> Get details for IIAB-12345
> Show me comments on ticket PROJ-789
> List subtasks for IIAB-456Advanced 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
.envfiles - Use different tokens for different machines
See SECURITY.md for complete security guidelines.
📚 Documentation
- Installation Guide - Detailed setup instructions
- Configuration - Advanced configuration options
- Usage Examples - More query examples
- Troubleshooting - Common issues and solutions
- Contributing - How to contribute
🔧 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", "[email protected]", "User")
[Environment]::SetEnvironmentVariable("JIRA_API_TOKEN", "your-token-here", "User")
# Restart terminalMac/Linux (Bash/Zsh)
# Add to ~/.bashrc or ~/.zshrc
export JIRA_URL="https://your-company.atlassian.net"
export JIRA_EMAIL="[email protected]"
export JIRA_API_TOKEN="your-token-here"
# Reload shell
source ~/.bashrc # or ~/.zshrcRegister 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 registerFor 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
- Built with Model Context Protocol SDK
- Inspired by the awesome GitHub Copilot CLI
- Thanks to the Jira REST API team
⭐ Support
If this project helps you, please give it a ⭐ on GitHub!
Issues? Report them here
Questions? Start a discussion
🔗 Links
Made with ❤️ for developers who love automation
