# mcp-jira-cloud

Source: https://glimind.com/server/npm%2Fmcp-jira-cloud
Registry id: `npm/mcp-jira-cloud`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "mcp-jira-cloud": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-jira-cloud"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add mcp-jira-cloud -- npx -y mcp-jira-cloud
```

## Tools (80)

- `jira_add_comment`: Use when the user asks to add a comment to a specific ticket; confirm intent before posting.
- `jira_add_dashboard_gadget`: Add a gadget to a dashboard. Provide either moduleKey or uri to specify the gadget type.
- `jira_add_labels`: Add, set, or remove labels on an issue. Use 'add' to append, 'set' to replace all, or 'remove' to delete specific labels.
- `jira_add_watcher`: Add a user to watch an issue.
- `jira_assign_issue`: Assign or unassign a Jira issue to a user.
- `jira_auth_status`: Check the current authentication status and type.
- `jira_autocomplete_jql`: Get autocomplete suggestions for JQL field values. Useful for building JQL queries interactively.
- `jira_bulk_edit_issues`: Edit multiple issues at once. Supports bulk editing of labels, assignee, priority, components, and fix versions. Returns a taskId to track progress.
- `jira_bulk_unwatch_issues`: Remove watchers from multiple issues at once. Returns a taskId to track progress.
- `jira_bulk_watch_issues`: Add watchers to multiple issues at once. Returns a taskId to track progress.
- `jira_clear_auth`: Use when the user asks to remove or reset stored Jira credentials.
- `jira_complete_sprint`: Complete an active sprint. Optionally move incomplete issues to another sprint or backlog.
- `jira_create_filter`: Create a new saved filter.
- `jira_create_issue`: Create a new Jira issue. Requires project key, issue type, and summary at minimum.
- `jira_create_issue_link`: Create a link between two issues.
- `jira_create_sprint`: Create a new sprint on a board.
- `jira_get_all_labels`: Get all labels used across all issues in the Jira instance.
- `jira_get_attachment_content`: Get the content/download URL for an attachment. Returns the redirect URL or content depending on redirect setting.
- `jira_get_attachment_metadata`: Get metadata for a specific attachment by ID.
- `jira_get_attachments`: Get all attachments for an issue.
- `jira_get_backlog_issues`: Get issues in the backlog (not in any active sprint) for a board.
- `jira_get_board`: Get details of a specific board including configuration.
- `jira_get_board_configuration`: Get the configuration of a board including columns, estimation, and ranking.
- `jira_get_boards`: Get all Scrum and Kanban boards, optionally filtered by project or type.
- `jira_get_bulk_operation_progress`: Check the progress of an async bulk operation using its taskId.
- `jira_get_changelog`: Get the history of changes for an issue.
- `jira_get_components`: Get components for a specific project.
- `jira_get_create_metadata`: Get metadata for creating issues in a project, including available issue types and their fields. Uses the modern non-deprecated API endpoints.
- `jira_get_dashboard`: Get details of a specific dashboard by ID.
- `jira_get_dashboard_gadgets`: Get all gadgets on a dashboard.
- `jira_get_dashboards`: Get a list of dashboards. Can filter by favourite or owned dashboards.
- `jira_get_edit_metadata`: Get metadata for editing a specific issue, including editable fields.
- `jira_get_epic_issues`: Get all issues belonging to an epic.
- `jira_get_epics`: Get epics for a board.
- `jira_get_favourite_filters`: Get filters marked as favourite by the current user.
- `jira_get_fields`: Get all available fields including custom fields.
- `jira_get_filter`: Get details of a specific filter.
- `jira_get_filters`: Get saved filters, optionally filtered by name.
- `jira_get_issue`: Get FULL details of a specific issue by key (e.g., PROJ-123).
- `jira_get_issue_comments`: Use when the user asks for the discussion or comments on a specific ticket; returns a clean list.
- `jira_get_issue_links`: Get all linked issues for a specific issue.
- `jira_get_issue_summary`: Get just the summary, description, and acceptance criteria for an issue.
- `jira_get_issue_types`: Get available issue types, optionally filtered by project.
- `jira_get_link_types`: Get available link types for linking issues.
- `jira_get_my_filters`: Get filters owned by the current user.
- `jira_get_my_open_issues`: Get issues assigned to the CURRENT USER that are not done.
- `jira_get_priorities`: Get available priority levels for issues.
- `jira_get_project`: Use when the user mentions a project key and asks for project details or metadata.
- `jira_get_sprint`: Get details of a specific sprint.
- `jira_get_sprint_issues`: Get all issues in a sprint.
- `jira_get_sprints`: Get sprints for a board, optionally filtered by state.
- `jira_get_statuses`: Get available statuses, optionally filtered by project.
- `jira_get_transitions`: Get available workflow transitions for an issue. Use before transitioning to see valid options.
- `jira_get_versions`: Get versions for a specific project.
- `jira_get_watchers`: Get the list of users watching an issue.
- `jira_list_projects`: Use when the user asks which Jira projects they can access or wants a list of projects.
- `jira_move_issues_to_backlog`: Move issues from a sprint back to the backlog.
- `jira_move_issues_to_epic`: Move issues to an epic.
- `jira_move_issues_to_sprint`: Move issues to a sprint.
- `jira_oauth_exchange_code`: Exchange the authorization code for access tokens after the user has completed the OAuth flow.
- `jira_oauth_get_auth_url`: Generate the OAuth 2.0 authorization URL that the user should visit to grant access. Returns the URL and required state parameter.
- `jira_oauth_list_sites`: List all Jira sites accessible with the current OAuth token.
- `jira_oauth_refresh`: Manually refresh the OAuth access token using the refresh token.
- `jira_oauth_set_tokens`: Set OAuth tokens directly if you already have them (e.g., from a previous session or external OAuth flow).
- `jira_parse_jql`: Parse JQL queries and return their abstract syntax tree (AST) structure. Useful for understanding query structure.
- `jira_rank_issues`: Change the rank of issues on a board by placing them before or after another issue.
- `jira_remove_issues_from_epic`: Remove issues from their epic (move to no epic).
- `jira_resolve`: Primary routing tool. Use this tool first when the user intent is clear (get issue, search, or my issues) but the exact Jira tool to call is uncertain.
- `jira_search_dashboards`: Search for dashboards by name, owner, or other criteria.
- `jira_search_issues`: Search for issues using JQL with FULL field details.
- `jira_search_issues_summary`: Search for issues using JQL returning only key, summary, and status.
- `jira_search_users`: Search for Jira users by name, email, or username.
- `jira_start_sprint`: Start a sprint that is in 'future' state.
- `jira_transition_issue`: Move a Jira issue to a different status by executing a workflow transition.
- `jira_update_filter`: Update an existing filter.
- `jira_update_issue`: Update an existing Jira issue. Only provided fields will be modified.
- `jira_update_sprint`: Update sprint details including name, dates, and goal.
- `jira_upload_attachment`: Upload a file attachment to an issue. Requires the file path on the local filesystem.
- `jira_validate_jql`: Validate one or more JQL queries for syntax and semantic correctness.
- `jira_whoami`: Use when the user asks who they are in Jira or wants to verify the Jira account in use.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
