Jira MCP

1## Jira MCP
2 
3An opinionated Jira MCP server built from years of real-world software development experience.
4 
5Unlike generic Jira integrations, this MCP is crafted from the daily workflows of engineers and automation QC teams. You'll find sophisticated tools designed for actual development needs—like retrieving all pull requests linked to an issue, managing complex sprint transitions, or tracking development information across your entire workflow.
6 
7This isn't just another API wrapper. It's a reflection of how professionals actually use Jira: managing sprints, tracking development work, coordinating releases, and maintaining visibility across teams. Every tool is designed to solve real problems that arise in modern software development.
8 
9## Available tools
10 
11### Issue Management
12- **jira_get_issue** - Retrieve detailed information about a specific issue including status, assignee, description, subtasks, and available transitions
13- **jira_create_issue** - Create a new issue with specified details (returns key, ID, and URL)
14- **jira_create_child_issue** - Create a child issue (sub-task) linked to a parent issue
15- **jira_update_issue** - Modify an existing issue's details (supports partial updates)
16- **jira_list_issue_types** - List all available issue types in a project with their IDs, names, and descriptions
17 
18### Search
19- **jira_search_issue** - Search for issues using JQL (Jira Query Language) with customizable fields and expand options
20 
21### Sprint Management
22- **jira_list_sprints** - List all active and future sprints for a specific board or project
23- **jira_get_sprint** - Retrieve detailed information about a specific sprint by its ID
24- **jira_get_active_sprint** - Get the currently active sprint for a given board or project
25- **jira_search_sprint_by_name** - Search for sprints by name with exact or partial matching
26 
27### Status & Transitions
28- **jira_list_statuses** - Retrieve all available issue status IDs and their names for a project
29- **jira_transition_issue** - Transition an issue through its workflow using a valid transition ID
30 
31### Comments
32- **jira_add_comment** - Add a comment to an issue (uses Atlassian Document Format)
33- **jira_get_comments** - Retrieve all comments from an issue
34 
35### Worklogs
36- **jira_add_worklog** - Add a worklog entry to track time spent on an issue
37 
38### History & Audit
39- **jira_get_issue_history** - Retrieve the complete change history of an issue
40 
41### Issue Relationships
42- **jira_get_related_issues** - Retrieve issues that have a relationship (blocks, is blocked by, relates to, etc.)
43- **jira_link_issues** - Create a link between two issues, defining their relationship
44 
45### Version Management
46- **jira_get_version** - Retrieve detailed information about a specific project version
47- **jira_list_project_versions** - List all versions in a project with their details
48 
49### Development Information
50- **jira_get_development_information** - Retrieve branches, pull requests, and commits linked to an issue via development tool integrations (GitHub, GitLab, Bitbucket)
51 
52 
53 
54## Installation
55 
56Copy this prompt to your AI assistant:
57 
58```
59Install the Jira MCP server (https://github.com/nguyenvanduocit/jira-mcp) for my Claude Desktop or Cursor IDE. Read the MCP documentation carefully and guide me through the installation step by step.
60```
61 
62If your AI assistant cannot help with this installation, it indicates either a misconfiguration or an ineffective AI tool. A capable AI assistant should be able to guide you through MCP installation.
63 
64## License
65MIT — see `LICENSE`.
66 
67## FOR AI
68 
69> THIS SECTION IS FOR AI ONLY
70 
71When working with this codebase, read these files to understand the project structure:
72 
731. **CLAUDE.md** - Comprehensive project documentation including architecture, development commands, and coding conventions
742. **main.go** - Entry point that shows how the MCP server is initialized and tools are registered
753. **services/jira_client.go** - Singleton Jira client initialization and authentication
764. **tools/** - Individual tool implementations following consistent patterns
775. **docs/** - Detailed documentation (see structure below)
78 
79Key concepts:
80- This is a Go-based MCP server that connects AI assistants to Jira
81- Each tool follows a registration + handler pattern with typed input validation
82- Tools are organized by category (issues, sprints, comments, worklogs, etc.)
83- All Jira operations use the `github.com/ctreminiom/go-atlassian` client library
84- Development principles documented in `.specify/memory/constitution.md`
85 
86Before making changes, review:
87- **CLAUDE.md** for architecture patterns and development commands
88- **.specify/memory/constitution.md** for governance principles
89 
90 
91## Quick start
92 
93### 1) Get an API token
94Create one at `https://id.atlassian.com/manage-profile/security/api-tokens`.
95 
96### 2) Add to Cursor
97Use Docker or a local binary (STDIO; no ports needed).
98 
99#### Docker
100```json
101{
102  "mcpServers": {
103    "jira": {
104      "command": "docker",
105      "args": [
106        "run", "--rm", "-i",
107        "-e", "ATLASSIAN_HOST=https://your-company.atlassian.net",
108        "-e", "ATLASSIAN_EMAIL=your-email@company.com",
109        "-e", "ATLASSIAN_TOKEN=your-api-token",
110        "ghcr.io/nguyenvanduocit/jira-mcp:latest"
111      ]
112    }
113  }
114}
115```
116 
117#### Binary
118```json
119{
120  "mcpServers": {
121    "jira": {
122      "command": "/usr/local/bin/jira-mcp",
123      "env": {
124        "ATLASSIAN_HOST": "https://your-company.atlassian.net",
125        "ATLASSIAN_EMAIL": "your-email@company.com",
126        "ATLASSIAN_TOKEN": "your-api-token"
127      }
128    }
129  }
130}
131```
132 
133### 3) Try it in Cursor
134- “Show my issues assigned to me”
135- “What’s in the current sprint for ABC?”
136- “Create a bug in ABC: Login fails on Safari”
137 
138## Configuration
139- **ATLASSIAN_HOST**: `https://your-company.atlassian.net`
140- **ATLASSIAN_EMAIL**: your Atlassian email
141- **ATLASSIAN_TOKEN**: API token
142 
143Optional `.env` (if running locally):
144```bash
145ATLASSIAN_HOST=https://your-company.atlassian.net
146ATLASSIAN_EMAIL=your-email@company.com
147ATLASSIAN_TOKEN=your-api-token
148```
149 
150HTTP mode (optional, for debugging):
151```bash
152jira-mcp -env .env -http_port 3000
153```
154Cursor config (HTTP mode):
155```json
156{ "mcpServers": { "jira": { "url": "http://localhost:3000/mcp" } } }
157```