Atlassian Jira MCP server

Read from the package source without running it. The installed server may list more.

• add_field_option

  Add a new option to a Connect app's select list issue field. Each field supports up to 10,000 options, and requires Jira administrator permissions.

• add_filter_to_favorites

  Mark a filter as a favorite for the current user. You can only favorite filters you own, filters shared with your groups or projects, or publicly shared filters.

• add_user_to_group

  Adds a user to a group in Jira. Requires site administration permissions to perform this operation.

• archive_issues

  Archive up to 1000 issues by their ID or key in a single request. Returns details of successfully archived issues and any errors encountered. Requires Jira admin permissions and a Premium or Enterprise license.

• archive_issues_by_jql

  Asynchronously archive up to 100,000 issues matching a JQL query. Returns a task URL to monitor the archival progress. Requires Jira admin permissions and a Premium or Enterprise license.

• bulk_edit_issues

  Simultaneously edit multiple issues across projects by specifying field values and target issues. Supports up to 1000 issues and 200 fields per request, with optional bulk notification to affected users.

• create_componentwrite action

  Create a new component in a project to serve as a container for organizing and grouping related issues. Requires project administration permissions.

• create_custom_field_optionswrite action

  Create options for a custom select field within a specific context. Supports cascading options for cascading select fields, with a maximum of 1000 options per request and 10000 total options per field.

• create_dashboardwrite action

  Creates a new dashboard with specified name, description, and access permissions. The dashboard will be configured with edit and share permissions to control who can modify and access it.

• create_filterwrite action

  Creates a new filter with a JQL query and optional sharing settings. The filter is shared according to default scope settings and is not automatically marked as a favorite.

• create_groupwrite action

  Creates a new group in Jira. Requires site administration permissions to perform this action.

• create_issuewrite action

  Create a new issue or subtask in a Jira project. Define the issue content using fields and optional workflow transitions, with field availability determined by the project's create issue metadata.

• create_issues_bulkwrite action

  Create up to 50 issues and subtasks in bulk with optional workflow transitions and property assignments. Use the Get create issue metadata endpoint to determine available fields for your project.

• delete_attachmentwrite action

  Removes an attachment from an issue. Requires either permission to delete your own attachments or permission to delete any attachment in the project.

• delete_comment_propertywrite action

  Removes a custom property from a comment. Requires either Edit All Comments permission or Edit Own Comments permission if you created the comment.

• delete_componentwrite action

  Deletes a component from a project. Optionally specify a replacement component to reassign any issues currently associated with the deleted component.

• delete_custom_fieldwrite action

  Permanently deletes a custom field from Jira, whether it's in the trash or active. This is an asynchronous operation; use the location link in the response to track the deletion task status.

• delete_custom_field_optionwrite action

  Deletes a custom field option from a specific context. Options with cascading options cannot be deleted until their cascading options are removed first.

• delete_dashboardwrite action

  Permanently deletes a dashboard. You must be the owner of the dashboard to delete it.

• delete_filterwrite action

  Permanently delete a filter from Jira. Only the filter creator or users with Administer Jira permission can delete filters.

• delete_groupwrite action

  Permanently deletes a group from the system. Optionally transfer group restrictions to another group to preserve access to comments and worklogs; otherwise, these items become inaccessible after deletion.

• delete_issues_bulkwrite action

  Submit a bulk delete request to remove multiple issues across projects in a single operation. You can delete up to 1,000 issues at once, with optional notification to affected users.

• download_attachment

  Download the full content of an attachment file. Supports partial downloads using HTTP Range headers to retrieve specific byte ranges. This operation can be accessed anonymously if you have the required project and issue permissions.

• duplicate_dashboardwrite action

  Creates a copy of an existing dashboard with customizable name, description, and permissions. The source dashboard must be owned by or shared with the requesting user.

• evaluate_jira_expression

  Evaluates a Jira expression and returns its computed value using the enhanced search API for better performance and scalability. Supports flexible data retrieval with access to issues, projects, sprints, boards, and custom context variables.

• fetch_issue_changelogs

  Retrieve change history for multiple issues in a paginated list, optionally filtered by specific fields. Results are sorted chronologically by changelog date and issue ID, starting from the oldest entries.

• fetch_issues

  Retrieve details for multiple issues by their IDs or keys in a single request. Supports up to 100 issues per request with case-insensitive matching and automatic detection of moved issues.

• get_archive_contents_metadata

  Retrieve metadata for the contents of an archive attachment, such as files within a ZIP archive. Use this operation when processing attachment data programmatically without user presentation.

• get_attachment

  Retrieve metadata for an attachment, including details like filename, size, and creation date. The attachment content itself is not returned by this operation.

• get_attachment_metadata_with_contents

  Retrieve complete metadata for an attachment and its contents if it's an archive. Returns information about the attachment itself (ID, name) plus details about any files within supported archive formats like ZIP.

• get_attachment_thumbnail

  Retrieves a thumbnail image for an attachment. Supports optional scaling and fallback behavior when thumbnails are unavailable.

• get_bulk_operation_progress

  Retrieve the current progress and status of a bulk issue operation. Returns real-time progress metrics while running, or final results upon completion. Task progress data is available for up to 14 days after creation.

• get_comment_property

  Retrieves the value of a specific property attached to a comment. Requires appropriate project and issue permissions, and respects any visibility restrictions on the comment.

• get_component

  Retrieve detailed information about a specific component by its ID. Requires Browse projects permission for the project containing the component.

• get_component_issue_counts

  Retrieves the count of issues assigned to a specific component. This provides a summary of issue distribution for component management and reporting purposes.

• get_custom_field_option

  Retrieve a custom field option by ID, such as an option from a select list. This operation works only with options created in Jira or via the Issue custom field options API, and can be accessed anonymously with appropriate permissions.

• get_dashboard

  Retrieve a dashboard by its ID. The dashboard must be shared with the user, owned by the user, or the user must have Jira administration permissions to access it.

• get_dashboard_item_property

  Retrieve a specific property value stored for a dashboard item. Dashboard items are gadgets that apps use to display user-specific information on dashboards, and properties store the item's content or configuration details.

• get_default_share_scope

  Retrieves the default sharing settings that apply to new filters and dashboards created by the authenticated user in Jira.

• get_field_option

  Retrieve a specific option from a Connect app-provided select list issue field. This operation only works with field options added by Connect apps, not those created directly in Jira.

• get_filter

  Retrieve a filter by its ID. The filter is only returned if you have access to it through ownership, group sharing, project sharing, or public sharing.

• get_filter_share_permission

  Retrieves a specific share permission for a filter. Returns details about how a filter is shared with groups, projects, all logged-in users, or the public. This operation can be accessed anonymously, but only returns permissions for filters you own, are shared with your groups, or are in projects you can access.

• get_issue_creation_fields

  Retrieve the available fields and their metadata for creating issues of a specific type in a project. Use this information to populate requests when creating single or bulk issues.

• grant_filter_share_permission

  Grant share permission for a filter to a user, group, project, or project role. Global or authenticated permissions will override all existing share permissions for the filter.

• list_bulk_editable_fields

  Retrieve a list of fields that are editable in bulk operations for the specified issues. Returns up to 50 fields per page, optionally filtered by search text.

• list_classification_levels

  Retrieves all available classification levels, optionally filtered by status and sorted by rank. No permissions are required to access this endpoint.

• list_comment_property_keys

  Retrieves all property keys associated with a specific comment. Useful for discovering what custom properties have been set on a comment.

• list_comments

  Retrieve a paginated list of comments by their IDs. Returns comments where you have appropriate project browse permissions and any required issue-level security or visibility group/role permissions.

• list_components

  Retrieve a paginated list of all components in specified projects, including global Compass components when applicable. Requires Browse Projects permission for the target project(s).

• list_custom_field_context_issue_type_mappings

  Retrieve a paginated list of issue type mappings for a custom field across specified contexts. Results are ordered by context ID first, then by issue type ID.

• list_custom_field_options

  Retrieve a paginated list of custom field options for a specific context, including both regular and cascading options in display order. Requires Jira administration or workflow edit permissions.

• list_dashboard_gadgets

  Retrieves a list of all available gadgets that can be added to dashboards. No authentication required.

• list_dashboard_item_property_keys

  Retrieves all property keys associated with a specific dashboard item. This operation allows you to discover what custom properties are available for a dashboard item without retrieving their values.

• list_dashboards

  Retrieve a list of dashboards owned by or shared with the user. Results can be filtered to show only favorite or owned dashboards, with support for pagination.

• list_events

  Retrieve all issue events from your Jira instance. Requires Administer Jira global permission to access.

• list_favorite_filters

  Retrieves all visible favorite filters for the authenticated user. A filter is visible only if it's owned by the user, shared with a group they belong to, shared with a private project they can browse, shared with a public project, or shared publicly.

• list_field_option_suggestions

  Retrieve a paginated list of selectable options for a Connect app custom issue field that the user can view and select. This operation only works with field options added by Connect apps, not those created natively in Jira.

• list_field_options

  Retrieve a paginated list of all options available for a Connect app-provided select list issue field. This operation only works with field options added by Connect apps, not those created directly in Jira.

• list_field_screens

  Retrieve a paginated list of all screens where a specific field is used. Requires Jira administrator permissions.

• list_fields

  Retrieve all available issue fields in Jira, including system and custom fields. Returns fields based on global settings, screen configuration, and your project access permissions.

• list_fields_search

  Retrieve a paginated list of Jira fields, optionally filtered by field IDs, search query, or project IDs. Supports sorting by various field attributes and can be restricted to custom fields only.

• list_filter_columns

  Retrieves the columns configured for a filter, which are used when viewing filter results in List View with Columns set to Filter. Column details are only returned for filters you own, filters shared with your groups, or filters shared with projects you have access to.

• list_filter_permissions

  Retrieve all share permissions for a filter, including access granted to groups, projects, all logged-in users, or the public. Only returns permissions visible to the requesting user based on their access level.

• list_group_members

  Retrieve a paginated list of all users in a group. Users are ordered by username but usernames are not included in results for privacy reasons.

• list_groups

  Retrieve a paginated list of groups from your Jira instance. Filter by group names, access level, or product application to find specific groups.

• list_issue_limit_violations

  Retrieve all issues that are breaching or approaching per-issue limits in Jira. Requires Browse projects permission for the relevant projects or Administer Jira global permission for complete results.

• list_issue_transitions

  Retrieve available transitions for specified issues that can be used in bulk transition operations. Returns transitions organized by workflow, including only those common across all specified issues that don't require additional field updates.

• list_issue_types_for_creation

  Retrieve issue type metadata for a project to determine which issue types can be created and what fields are required. Use this information to populate requests when creating issues.

• list_my_filters

  Retrieve filters owned by the authenticated user, with optional inclusion of their favorite filters. Favorite filters are only visible if they are owned by the user, shared with a group the user belongs to, shared with a private project the user can browse, shared with a public project, or shared publicly.

• list_system_avatars

  Retrieves a list of system avatars filtered by type (issue type, project, user, or priority). This operation is publicly accessible and requires no authentication.

• list_trashed_fields

  Retrieve a paginated list of custom fields that have been moved to trash. Results can be filtered by field name or description, and sorted by name, trash date, or planned deletion date. Requires Administer Jira global permission.

• move_custom_field_to_trash

  Move a custom field to trash, making it unavailable for use while preserving the option to permanently delete it later. Requires Administer Jira global permission.

• move_issues_bulk

  Move multiple issues across projects in a single operation. Supports moving up to 1,000 issues (including subtasks) to a single destination project, issue type, and parent, with automatic field mapping and optional bulk notifications.

• remove_dashboard_item_propertywrite action

  Removes a custom property from a dashboard item. Requires edit permission on the dashboard.

• remove_filter_favoritewrite action

  Remove a filter from the user's favorites list. This operation only removes filters that are currently visible to the user; filters that were favorited but subsequently made private cannot be removed through this operation.

• remove_filter_share_permissionwrite action

  Removes a share permission from a filter, restricting access for the specified user or group. Requires ownership of the filter and permission to access Jira.

• remove_gadgetwrite action

  Remove a gadget from a dashboard. When removed, other gadgets in the same column automatically shift up to fill the vacant position.

• reorder_custom_field_options

  Reorder custom field options within a specific context. Rearranges the display order of custom field options or cascading options by specifying their desired sequence.

• replace_field_option

  Deselects a custom field select-list option from all issues where it is selected, optionally replacing it with a different option. This asynchronous operation works only with options added by Connect or Forge apps and can be scoped to specific issues using JQL.

• restore_custom_field

  Restore a custom field from trash back to active use. Requires Administer Jira global permission.

• search_dashboards

  Search for dashboards with optional filtering by name, project, and status. Returns a paginated list of dashboards accessible to the user based on ownership, group membership, project sharing, or public availability.

• search_field_options

  Search for visible options in a Connect app custom select list field. Returns paginated results filtered by user permissions and optionally by project.

• search_filters

  Search for filters with pagination support, returning filters based on ownership, sharing permissions, and optional search criteria. Only filters accessible to the authenticated user are returned.

• search_groups

  Search for groups by name to populate group picker suggestions. Returns matching groups with query terms highlighted in HTML, sorted alphabetically, along with a count summary. Requires Browse projects permission; anonymous users and those without permission receive empty results.

• search_issues_picker

  Search for issues matching a query string to provide auto-completion suggestions. Returns matching issues from the user's history and from a filtered set defined by JQL.

• search_users_and_groups

  Search for users and groups by name or email. Returns matching results with HTML-formatted highlights, useful for populating picker fields. Supports filtering by project, issue type, and custom field permissions.

• set_issue_properties_bulk

  Bulk set or update custom properties on multiple issues in a single transactional operation. Supports up to 10 properties and 10,000 issues, with each property value limited to 32,768 characters.

• set_issue_properties_bulk_per_issue

  Bulk set or update custom properties on multiple issues. Supports up to 100 issues with up to 10 properties each in a single asynchronous request. Updates are non-transactional, so some entities may succeed while others fail.

• transfer_filter_ownershipwrite action

  Transfer ownership of a filter to another user. The requesting user must own the filter or have Jira administrator permissions.

• transition_issues_bulk

  Transition the status of multiple issues in a single operation. Submit up to 1,000 issues with their corresponding transition IDs to move them through your workflow states.

• unwatch_issues_bulkwrite action

  Remove your watch from multiple issues in a single operation. You can unwatch up to 1,000 issues across different projects and issue types.

• update_componentwrite action

  Updates an existing component in a project, overwriting any provided fields. Use an empty string for leadAccountId to remove the component lead.

• update_custom_field_optionswrite action

  Updates the available options for a custom field within a specific context. Only options with changed values are updated; unchanged options are ignored in the response. This operation works exclusively with select list options created in Jira or via the Issue custom field options API, not with options created by Connect apps.

• update_custom_field_valuewrite action

  Updates the value of a custom field across one or more issues. Only the app that owns the custom field can perform this operation.

• update_custom_field_valueswrite action

  Update the values of one or more custom fields across one or more issues. Each custom field and issue combination must be unique within the request. Only the app that owns the custom field can perform this operation.

• update_dashboardwrite action

  Update an existing dashboard by replacing all its details with the provided information. You must own the dashboard to update it.

• update_dashboard_gadgetwrite action

  Modify a gadget's appearance and position on a dashboard by updating its title, color, and layout properties.

• update_dashboards_bulkwrite action

  Perform bulk operations on multiple dashboards such as changing ownership or modifying permissions. You can update up to 100 dashboards in a single request. You must own the dashboards or have administrator privileges to make changes.

• update_filterwrite action

  Update an existing filter's configuration including name, description, JQL query, and sharing settings. You must own the filter to make changes.

• watch_issues

  Add up to 1,000 issues to your watch list in a single bulk operation. Watched issues will appear in your notifications and dashboards.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 55% of 1,119 Developer tools servers

Tools

100

the typical Developer tools server has 7

Tools that change things

31%

typical: 5%. Fewer write tools means less an agent can break

GitHub stars

31

more than 90% of 855 Developer tools servers

Downloads a week

157

more than 67% of 436 Developer tools servers with a package

Atlassian Jira: common questions

Is Atlassian Jira MCP server safe?

Mostly: it is graded B (80/100). Read the Atlassian Jira safety report

How do I install Atlassian Jira?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Atlassian Jira need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Atlassian Jira maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.3.

What can I use instead of Atlassian Jira?

Servers from other publishers that do the same job: Atlassian Dc Jira MCP server, GitLab MCP Server and Atlassian Rovo MCP Server. Compare all Atlassian Jira alternatives.

How does Atlassian Jira compare with other Developer tools MCP servers?

safety score 80/100 (higher than 55% of 1,119 Developer tools servers); tools 100 (the typical Developer tools server has 7); tools that change things 31% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.