Provides comprehensive tools for managing Jira issues, including creating, updating, searching, and deleting issues, managing comments, transitions, watchers, issue links, and accessing project metadata through both tools and resources for self-hosted Jira instances using Personal Access Token authentication.
Jira MCP Server
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
βοΈ Configuration
Create a .env file in the project root:
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
Development Mode
Using with npx (Recommended)
No installation required! Add the following to your MCP configuration:
Global Installation
Then add to your MCP configuration:
Local Development
If running from source, add the following to your MCP configuration:
π οΈ Available Tools (27 total)
Issue Operations
Tool | Description |
| Get details of a Jira issue by its key |
| Search for issues using JQL |
| Create a new issue (basic fields) |
| Create issue with full field support (fixVersions, components, custom fields) |
| Update an existing issue (basic fields) |
| Update issue with full field support |
| Delete an issue |
| Assign or unassign an issue |
| Get available transitions for an issue |
| Transition an issue to a new status |
| Link two issues |
| Add a watcher to an issue |
Comments
Tool | Description |
| Get comments on an issue |
| Add a comment to an issue |
Projects
Tool | Description |
| Get all projects |
| Get details of a specific project |
| Get all versions for a project (for fixVersions) |
| Get all components for a project |
Metadata & Field Discovery
Tool | Description |
| IMPORTANT : Get required fields and allowed values for creating issues |
| Get editable fields and allowed values for an existing issue |
| Get all available fields including custom fields |
| Get allowed values for a specific field |
| Get all available priorities |
| Get all available statuses |
| Get all available issue link types |
Users
Tool | Description |
| Search for users |
| 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 |
| Server configuration and connection info |
| Currently authenticated user details |
| All available issue priorities |
| All available issue statuses |
| All fields (system + custom) grouped by type |
| Available issue link types |
| List of all projects (key, name, type) |
| Project details with versions, components, issue types |
| Issues assigned to current user |
Using Resources
Resources provide context without explicit tool calls. For example, reading jira://project/MSSP returns:
π Example JQL Queries
π€ 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
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