Jira MCP server for Claude, ChatGPT, Claude Code and Cursor

Creates a new issue in a specified Jira project. This includes setting parameters such as the issue type, summary, and assignee details. Note: Some projects may have custom required fields - use JIRA_GET_FIELDS to discover them if needed.

Updates a specified Jira issue by changing its fields or adding new information. This action allows users to modify attributes such as the summary, description, and assignee of the issue.

This action deletes a specified Jira issue. It can also delete any associated subtasks if requested.

This action creates a new Jira project with the necessary configurations. It requires information such as the project key, name, type, and template to successfully set up a project in Jira.

This action adds a specified user as a watcher to a Jira issue. A watcher receives notifications about updates to the issue.

This action deletes a specific worklog entry from a Jira issue. It provides options to notify users and adjust the issue's remaining estimate as needed.

This action adds a rich comment to a specific Jira issue, allowing Markdown formatting. Users can specify visibility restrictions for the comment if needed.

This action updates an existing comment on a Jira issue. Users can modify the comment text and adjust visibility settings as needed.

This action deletes a specified comment from a Jira issue. It requires the issue ID or key along with the comment ID to perform the delete operation.

This action allows users to upload a file and attach it to a specific Jira issue. It supports various file formats and ensures that the attachment is associated with the correct issue key.

This action assigns a specified Jira issue to the designated user or the project's default assignee. It also allows for unassigning the issue by not providing an account ID and supports lookup by username or email.

This action creates multiple Jira issues in a single API call. It allows for bulk creation of issues with various attributes, such as assignee and priority, streamlining the issue management process.

This action links two Jira issues based on the specified relationship type. It allows users to track dependencies and relationships between issues within their projects.

This action allows the creation of a new sprint within a specified Jira board. Users can set optional start and end dates, as well as define a primary goal for the sprint.

This action creates a new version within a specified Jira project, allowing users to manage project milestones effectively. It includes attributes such as name, description, and release dates that provide context to the version being created.

This action allows you to search for Jira users using various parameters like email or display name. It returns a list of users that match the search criteria for further operations.

Retrieves a list of all projects that the user has visibility over. This action allows filtering, sorting, and pagination of project results based on specified criteria.

This action retrieves a list of all users from the Jira instance. If no pagination parameters are provided, the action automatically iterates through all pages to return all available users. It also supports manual pagination using the provided parameters.

This action retrieves detailed information about the currently authenticated Jira user. It provides data such as the user's display name, email address, groups, and application roles.

This action retrieves a specific Jira issue using its ID or key. Users can customize the fields and additional data included in the response to suit their specific needs.

Retrieves a list of all available Jira issue types for the user. This action allows access to Jira's issue type details that can be utilized within the application.

This action retrieves the available workflow transitions for a specified Jira issue. It can return details about the transitions, including their IDs and names, as well as whether they are currently available for use.

Retrieves a list of Jira boards based on specified criteria. Supports pagination via start_at and max_results. The response also includes convenience fields nextStartAt, hasNextPage, and nextPageToken to help iterate through pages.

This action fetches paginated comments associated with a specific Jira issue. It allows users to retrieve details such as the comment content and the authorship information.

Retrieves and lists sprints associated with a specified Jira board. Users can filter results based on the state of the sprints, allowing for better management and visibility.

This action takes multiple issues and moves them to a specified sprint in Jira. It ensures that the issues are successfully added to the targeted sprint based on the provided sprint ID.

This action retrieves Jira issues based on a specified JQL query. It allows for pagination as well as selection of specific fields to include in the result.

This action performs the enhanced JQL issue search that supports eventual consistency and token-based pagination. Use it when you need stable results immediately after creating or updating issues, or when paginating large result sets. IMPORTANT: This action only works with Jira Cloud. For Jira Server or Data Center instances, use JIRA_SEARCH_FOR_ISSUES_USING_JQL_GET instead.

This action performs advanced searches for Jira issues using either structured filters or raw JQL queries. It supports various search criteria including project, assignee, status, priority, and date ranges.

This action transitions a specified Jira issue to a different status based on the selected workflow transition. It supports optional comments and assignee information. Note: Only fields configured on the transition screen can be set during the transition.

This action deletes a specified version in Jira. It can also optionally move issues associated with the deleted version to another specified version.

This action retrieves a list of all issue type schemes from Jira. It allows for optional filtering based on specific IDs and supports pagination for large sets of data.

This action retrieves issue statuses that are associated with workflows in Jira. It provides detailed information about each status including name, description, and category. Note: This may not include statuses from team-managed (Next-Gen) projects or unused statuses.

This action fetches a specific comment from a Jira issue by its ID. You can specify optional parameters to expand additional information in the response.

This action retrieves all issue link types configured in the Jira instance. It provides a comprehensive list of the relationships available for issues in your project.

This action retrieves a specific property associated with a Jira issue using its ID or key. It allows users to access custom information stored in Jira properties.

This action fetches all issue resolutions available in Jira. It retrieves resolution types such as 'Done' or 'Fixed' that can be applied to issues.

This action retrieves a specific Jira issue type scheme based on its unique ID and includes all related issue types. It helps users obtain details about the organization of issue types within a scheme.

This action retrieves the list of users watching a specific Jira issue. It allows clients to understand who is interested in updates for that issue.

Retrieves all worklogs associated with a specific Jira issue. This includes filtering options such as start dates and pagination for large sets of worklogs.

This action retrieves all versions associated with a specific Jira project. It can include additional properties for each version based on the request parameters.

This action retrieves remote issue links associated with a specified Jira issue. You can filter the links by providing an optional global ID for a specific link retrieval.

This action retrieves the voting information associated with a specific Jira issue. It provides details such as the total number of votes and whether the user has voted on that issue.

Retrieves the worklog entries for a specified Jira issue. This action provides detailed information on time spent by users on the issue, allowing for effective tracking and reporting of work activity.

This action allows you to remove a specified user from the watchers list of a given issue. You need to provide the issue identification and the user's account ID for the operation to succeed.

This action sends a customized email notification related to a specific Jira issue. It includes customizable fields for the subject, message content, and recipients, ensuring tailored communication for issue updates.