Jira MCP Server
Enables comprehensive interaction with self-hosted Jira instances using Personal Access Token authentication, supporting issue management, JQL searches, comments, transitions, projects, and custom fields through 27 specialized tools.
README
Jira MCP Server
<!-- Add these badges once published to GitHub/npm -->
<!-- -->
<!--
-->
<!--
-->
<!--
-->
<!--
-->
<!--
-->
A Model Context Protocol (MCP) server for self-hosted Jira instances using Personal Access Token (PAT) authentication.
✨ Features
- Issue Management: Get, create, update, delete, and assign issues
- Search: Search issues using JQL
- Comments: Get, add, update, and delete comments
- Transitions: Get available transitions and transition issues
- Projects: List and get project details
- Users: Search users and get current user
- Watchers: Add watchers to issues
- Issue Links: Link issues together
📋 Prerequisites
- Node.js 18+
- Self-hosted Jira instance (tested with v9.12.12)
- Personal Access Token (PAT) for authentication
🚀 Installation
npm install
npm run build
⚙️ Configuration
Create a .env file in the project root:
JIRA_BASE_URL=https://your-jira-instance.com/
PAT=your-personal-access-token
Getting a Personal Access Token
- Log in to your Jira instance
- Go to Profile → Personal Access Tokens
- Create a new token with appropriate permissions
- Copy the token to your
.envfile
📖 Usage
Running the Server
npm start
Development Mode
npm run dev
Using with npx (Recommended)
No installation required! Add the following to your MCP configuration:
{
"mcpServers": {
"jira": {
"command": "npx",
"args": ["-y", "jira-mcp-server-pro"],
"env": {
"JIRA_BASE_URL": "https://your-jira-instance.com/",
"PAT": "your-personal-access-token"
}
}
}
}
Global Installation
npm install -g jira-mcp-server-pro
Then add to your MCP configuration:
{
"mcpServers": {
"jira": {
"command": "jira-mcp-server-pro",
"env": {
"JIRA_BASE_URL": "https://your-jira-instance.com/",
"PAT": "your-personal-access-token"
}
}
}
}
Local Development
If running from source, add the following to your MCP configuration:
{
"mcpServers": {
"jira": {
"command": "node",
"args": ["/path/to/jiraMCP/dist/index.js"],
"env": {
"JIRA_BASE_URL": "https://your-jira-instance.com/",
"PAT": "your-personal-access-token"
}
}
}
}
🛠️ Available Tools (27 total)
Issue Operations
| Tool | Description |
|---|---|
jira_get_issue |
Get details of a Jira issue by its key |
jira_search_issues |
Search for issues using JQL |
jira_create_issue |
Create a new issue (basic fields) |
jira_create_issue_advanced |
Create issue with full field support (fixVersions, components, custom fields) |
jira_update_issue |
Update an existing issue (basic fields) |
jira_update_issue_advanced |
Update issue with full field support |
jira_delete_issue |
Delete an issue |
jira_assign_issue |
Assign or unassign an issue |
jira_get_transitions |
Get available transitions for an issue |
jira_transition_issue |
Transition an issue to a new status |
jira_link_issues |
Link two issues |
jira_add_watcher |
Add a watcher to an issue |
Comments
| Tool | Description |
|---|---|
jira_get_comments |
Get comments on an issue |
jira_add_comment |
Add a comment to an issue |
Projects
| Tool | Description |
|---|---|
jira_get_projects |
Get all projects |
jira_get_project |
Get details of a specific project |
jira_get_project_versions |
Get all versions for a project (for fixVersions) |
jira_get_project_components |
Get all components for a project |
Metadata & Field Discovery
| Tool | Description |
|---|---|
jira_get_create_meta |
IMPORTANT: Get required fields and allowed values for creating issues |
jira_get_edit_meta |
Get editable fields and allowed values for an existing issue |
jira_get_fields |
Get all available fields including custom fields |
jira_get_field_options |
Get allowed values for a specific field |
jira_get_priorities |
Get all available priorities |
jira_get_statuses |
Get all available statuses |
jira_get_issue_link_types |
Get all available issue link types |
Users
| Tool | Description |
|---|---|
jira_search_users |
Search for users |
jira_get_current_user |
Get the current authenticated user |
📝 Workflow: Creating Issues with Required Fields
-
First, call
jira_get_create_metato discover required fields and allowed values:jira_get_create_meta(projectKey: "PROJ", issueType: "Bug")This returns all fields with their requirements and dropdown options.
-
Then, use
jira_create_issue_advancedwith the correct values:jira_create_issue_advanced( projectKey: "PROJ", summary: "Issue title", issueType: "Bug", fixVersions: ["1.0.0"], components: ["Backend"], customFields: {"customfield_10001": "value"} )
📚 Resources
The server exposes MCP Resources for quick access to Jira data without tool calls:
| Resource URI | Description |
|---|---|
jira://config |
Server configuration and connection info |
jira://current-user |
Currently authenticated user details |
jira://priorities |
All available issue priorities |
jira://statuses |
All available issue statuses |
jira://fields |
All fields (system + custom) grouped by type |
jira://link-types |
Available issue link types |
jira://projects |
List of all projects (key, name, type) |
jira://project/{KEY} |
Project details with versions, components, issue types |
jira://my-issues |
Issues assigned to current user |
Using Resources
Resources provide context without explicit tool calls. For example, reading jira://project/MSSP returns:
{
"key": "MSSP",
"name": "MSSP",
"versions": [{"name": "1.0.0", "released": true}, ...],
"components": [{"name": "LOGIN"}, {"name": "MSSP-FO"}, ...],
"issueTypes": [{"id": "1", "name": "Bug"}, {"id": "3", "name": "Task"}, ...]
}
🔍 Example JQL Queries
# Issues assigned to me
assignee = currentUser()
# Open bugs in a project
project = PROJ AND issuetype = Bug AND status != Done
# Issues created in the last 7 days
created >= -7d
# High priority issues
priority in (Highest, High)
🤝 Contributing
Contributions are welcome! Here's how you can help:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
Development Setup
# Clone your fork
git clone https://github.com/YOUR_USERNAME/jira-mcp-server.git
cd jira-mcp-server
# Install dependencies
npm install
# Run in development mode
npm run dev
Reporting Issues
- Use the GitHub Issues to report bugs
- Include your Node.js version, Jira version, and steps to reproduce
- Check existing issues before creating a new one
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
🙏 Acknowledgments
- Model Context Protocol for the MCP specification
- Atlassian for Jira REST API documentation
<p align="center"> Made with ❤️ for the MCP community </p>
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
E2B
Using MCP to run code via e2b.