jira-cli-mcp
Provides tools for interacting with Jira, including creating, listing, and updating tickets, adding comments, assigning tickets, moving tickets between statuses, and more.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@jira-cli-mcplist my open Jira issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Jira CLI MCP Server
MCP (Model Context Protocol) server that wraps the jira-cli command-line tool to enable AI assistants to interact
with Jira.
Why jira-cli-mcp?
If you're looking for a Jira MCP server, here's what makes jira-cli-mcp unique:
ð Leverage Existing Tools - Works seamlessly with your existing jira-cli setup and authentication
ð Security-First - No API tokens in config files; authentication handled by jira-cli
ðŠķ Lightweight - Just a Bun process, no Docker or containers required
When to use mcp-atlassian instead?
Choose mcp-atlassian if you:
Need Confluence support (we're Jira-only)
Prefer Docker deployment
Want a self-contained solution without CLI dependencies
Need direct API integration rather than CLI wrapping
Features
create_ticket - Create new Jira tickets with customizable fields
list_tickets - Search and list Jira tickets using JQL queries
get_ticket - Get detailed ticket information including comments
update_ticket_description - Update ticket descriptions with rich text formatting
add_comment - Add comments to tickets with Markdown support
assign_to_me - Assign tickets to the current user
move_ticket - Move tickets between different statuses
open_ticket_in_browser - Open a Jira ticket in the default web browser
Quick Start
Install and configure jira-cli (Installation guide):
# Install jira-cli (macOS) brew install ankitpokhrel/jira-cli/jira-cli # Configure jira-cli with your Jira instance jira initInstall jira-cli-mcp:
brew tap choplin/jira-cli-mcp brew install jira-cli-mcpAdd to Claude Desktop config (see Setup below)
Prerequisites
jira-cli installed and authenticated
Bun runtime (only needed for development or if installing from source)
Installation
Option 1: Install via Homebrew (macOS/Linux)
brew tap choplin/jira-cli-mcp
brew install jira-cli-mcpOption 2: Install via npm
# Install globally with npm
npm install -g @choplin/jira-cli-mcp
# Or with Bun
bun install -g @choplin/jira-cli-mcpOption 3: Download Binary
Download the pre-compiled binary for your platform from the releases page:
macOS (Apple Silicon):
jira-cli-mcp-darwin-arm64.tar.gzmacOS (Intel):
jira-cli-mcp-darwin-x64.tar.gzLinux (x64):
jira-cli-mcp-linux-x64.tar.gzLinux (ARM64):
jira-cli-mcp-linux-arm64.tar.gz
# Example for macOS (Apple Silicon)
tar -xzf jira-cli-mcp-darwin-arm64.tar.gz
chmod +x jira-cli-mcp-darwin-arm64
sudo mv jira-cli-mcp-darwin-arm64 /usr/local/bin/jira-cli-mcpOption 4: Build from Source
git clone https://github.com/choplin/jira-cli-mcp.git
cd jira-cli-mcp
bun install
bun run build:prodSetup for Claude Desktop
Option 1: Using Homebrew Installation (Recommended)
If you installed via Homebrew (as shown in Quick Start), add to your claude_desktop_config.json:
{
"mcpServers": {
"jira-cli": {
"command": "jira-cli-mcp"
}
}
}Option 2: Using npm Package
Add to your claude_desktop_config.json:
{
"mcpServers": {
"jira-cli": {
"command": "npx",
"args": ["@choplin/jira-cli-mcp"]
}
}
}Or if installed globally:
{
"mcpServers": {
"jira-cli": {
"command": "jira-cli-mcp"
}
}
}Option 3: Using Pre-compiled Binary (No Dependencies)
Download the binary for your platform from releases
Extract and move to your PATH:
tar -xzf jira-cli-mcp-darwin-arm64.tar.gz
sudo mv jira-cli-mcp-darwin-arm64 /usr/local/bin/jira-cli-mcpAdd to config:
{
"mcpServers": {
"jira-cli": {
"command": "jira-cli-mcp"
}
}
}Option 4: Build from Source
Clone and run directly:
git clone https://github.com/choplin/jira-cli-mcp.git
cd jira-cli-mcp
bun installAdd to config:
{
"mcpServers": {
"jira-cli": {
"command": "bun",
"args": ["run", "/path/to/jira-cli-mcp/src/index.ts"]
}
}
}Configuration Location
The config file is typically located at:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Verification
After setup, restart Claude Desktop and check if the MCP server is loaded by asking Claude about available Jira tools.
Setup for Other AI Assistants
Claude Code
Claude Code has built-in support for MCP servers. To use jira-cli-mcp in your project:
First install jira-cli-mcp using one of the methods in the Installation section
Create a
.claude/mcp.jsonfile in your project root:
{
"servers": {
"jira-cli": {
"command": "jira-cli-mcp"
}
}
}Restart Claude Code and the MCP server will be automatically loaded
You can then use Jira commands directly in your conversation, such as:
"List my open Jira tickets"
"Show me details for PROJ-123"
"Add a comment to PROJ-456"
GitHub Copilot (VS Code)
GitHub Copilot supports MCP servers in Visual Studio Code (version 1.99+):
First install jira-cli-mcp using one of the methods in the Installation section
Create
.vscode/mcp.jsonin your repository:
{
"servers": {
"jira-cli": {
"command": "jira-cli-mcp"
}
}
}Open the
.vscode/mcp.jsonfile in VS Code and click the [Start] button to activate the serverIn Copilot Chat:
Open Copilot Chat panel
Select "Agent" from the popup menu
Click the tools icon to see available MCP servers
Note: MCP support in GitHub Copilot is currently in public preview.
Development
Running Tests
# Run unit tests only
bun test
# Run all tests including integration tests
bun run test:integration
# Run integration tests with a specific test ticket
JIRA_CLI_MCP_TEST_TICKET=PROJ-123 bun run test:integrationEnvironment Variables
JIRA_CLI_PATH- Custom path to jira-cli executable (default: "jira")
Development Environment Variables
JIRA_CLI_MCP_TEST_TICKET- Ticket key for integration tests (required for non-listing integration tests)INTEGRATION_TEST=true- Enable integration tests
Type Checking
bun run typecheckLinting and Formatting
bun run lint
bun run formatArchitecture
src/tools/- MCP tool implementationssrc/utils/- Shared utilities and typestests/- Unit tests with mocked jira-clitests/integration/- Integration tests with real jira-cli
Notes
The server uses Atlassian Document Format (ADF) for rich text handling
Markdown input is automatically converted to ADF by jira-cli
All integration tests require proper jira-cli authentication
Troubleshooting
Common Issues
"jira-cli not found" error
Ensure jira-cli is installed:
which jiraIf using a custom path, set
JIRA_CLI_PATHenvironment variable
Authentication errors
Run
jira meto verify authenticationRe-authenticate with
jira initif needed
MCP server not showing in Claude Desktop
Verify the config file path is correct
Ensure the path in config uses absolute paths, not relative
Restart Claude Desktop after config changes
Permission errors on macOS
Grant terminal/Claude Desktop full disk access in System Preferences
Ensure jira-cli has necessary permissions
Debug Mode
To see detailed logs, you can run the server manually:
cd /path/to/jira-cli-mcp
bun run src/index.tsLicense
This project is licensed under the MIT License - see the LICENSE file for details.
This server cannot be installed
Maintenance
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/choplin/jira-cli-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server