Verfy

MCP-серверы / mcp-atlassian

Изменения MCP-инструментов

mcp-atlassian

8 из последних 9 обновлений изменили то, что читает агент: переписано описаний инструментов — 61, до 0.24.3.

Пакет PyPI · последняя запись 13 ноября 2026 г. на чистой машине с подставными настройками; отправлялся только tools/list. Изменённое описание — не уязвимость. страница на PyPI · Метод и ограничения · эти данные в JSON.

Выпуск за выпуском

0.24.2 → 0.24.3

выпуск patch, 12 ноября 2026 г.

Определения инструментов не изменились.

0.24.1 → 0.24.2

выпуск patch, 12 ноября 2026 г.

jira_get_issue: изменено: схема входных данных

jira_get_transitions: изменено: схема входных данных; новые аргументы: expand_fields

jira_transition_issue: изменено: схема входных данных; новые аргументы: update_data

0.24.0 → 0.24.1

выпуск patch, 8 ноября 2026 г.

jira_remove_issue_link: изменено: схема входных данных

0.23.1 → 0.24.0

выпуск minor, 8 ноября 2026 г.

jira_add_comment: изменено: схема входных данных

jira_assign_issue: изменено: описание и схема входных данных
До (0.23.1)
Assign a Jira issue to a user using the dedicated assignment endpoint. This is more reliable than setting assignee via update_issue, which is silently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee.
После (0.24.0)
Assign a Jira issue to a user using the dedicated assignment endpoint. This is more reliable than setting assignee via update_issue, which is silently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee. On Jira Server/DC the following identifier forms are all accepted: login name, email address, display name, or JIRAUSER key. The resolution order is: key lookup → email search (with email-as-username fallback) → text search → assignable-user search scoped to the issue.

jira_create_issue: изменено: схема входных данных

jira_get_board_issues: изменено: схема входных данных

jira_get_issue: изменено: описание и схема входных данных; новые аргументы: epic_summary_children, max_epic_children
До (0.23.1)
Get details of a specific Jira issue. Includes Epic links and relationship information. Use the ``include`` parameter to inline enrichments (remote_links, transitions, watchers, changelog, comments, worklogs) so that separate tool calls are not needed.
После (0.24.0)
Get details of a specific Jira issue. Includes Epic links and relationship information. Use the ``include`` parameter to inline enrichments (remote_links, transitions, watchers, changelog, comments, worklogs, epic_summary) so that separate tool calls are not needed. The ``epic_summary`` section only applies when the issue is an Epic and adds child-issue aggregations (counts by status, assignee, and type, plus a completion percentage); it is aggregate-only unless ``epic_summary_children`` is set.

jira_get_sprint_issues: изменено: схема входных данных

jira_get_user_profile: изменено: описание и схема входных данных; новые аргументы: expand
До (0.23.1)
Retrieve profile information for a specific Jira user.
После (0.24.0)
Retrieve profile information for a Jira user. Use ``user_identifier="me"`` to return the account authenticated for the current request directly from Jira's ``/myself`` endpoint. This path does not require Browse Users permission.

jira_search: изменено: схема входных данных

jira_transition_issue: изменено: схема входных данных

jira_update_issue: изменено: описание и схема входных данных; новые аргументы: attachments_base64, comment, comment_visibility, transition, worklog, worklog_started
До (0.23.1)
Update an existing Jira issue including changing status, adding Epic links, updating fields, etc.
После (0.24.0)
Update an issue and optionally transition, comment, and log work.

0.23.0 → 0.23.1

выпуск patch, 19 августа 2026 г.

jira_get_board_issues: изменено: схема входных данных

jira_get_issue: изменено: схема входных данных

jira_get_sprint_issues: изменено: схема входных данных

jira_search: изменено: схема входных данных

0.22.1 → 0.23.0

выпуск minor, 18 июля 2026 г.

Добавлено: jira_create_customer_request, jira_get_cross_project_dependencies, jira_get_project_epic_hierarchy, jira_get_request_type_fields, jira_get_request_types

jira_add_comment: изменено: описание и схема входных данных
До (0.22.1)
Add a comment to a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. body: Comment text in Markdown. visibility: (Optional) Comment visibility as JSON string. public: (Optional) For JSM issues. True = customer-visible, False = internal/agent-only. Uses ServiceDesk API. Returns: JSON string representing the added comment object. Raises: ValueError: If in read-only mode or Jira client unavailable.
После (0.23.0)
Add a comment to a Jira issue.
jira_add_issues_to_sprint: изменено: описание и схема входных данных
До (0.22.1)
Add issues to a Jira sprint. Args: ctx: The FastMCP context. sprint_id: The ID of the sprint. issue_keys: Comma-separated issue keys. Returns: JSON string with success message. Raises: ValueError: If in read-only mode or Jira client unavailable.
После (0.23.0)
Add issues to a Jira sprint.
jira_add_watcher: изменено: описание и схема входных данных
До (0.22.1)
Add a user as a watcher to a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. user_identifier: Account ID (Cloud) or username (Server/DC). Returns: JSON string with success confirmation. Raises: ValueError: If the Jira client is not configured or available.
После (0.23.0)
Add a user as a watcher to a Jira issue.
jira_add_worklog: изменено: описание и схема входных данных
До (0.22.1)
Add a worklog entry to a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. time_spent: Time spent in Jira format. comment: Optional comment in Markdown. started: Optional start time in ISO format. original_estimate: Optional new original estimate. remaining_estimate: Optional new remaining estimate. Returns: JSON string representing the added worklog object. Raises: ValueError: If in read-only mode or Jira client unavailable.
После (0.23.0)
Add a worklog entry to a Jira issue.
jira_assign_issue: изменено: описание и схема входных данных
До (0.22.1)
Assign a Jira issue to a user using the dedicated assignment endpoint. This is more reliable than setting assignee via update_issue, which is silently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee. Args: ctx: The FastMCP context. issue_key: Jira issue key. assignee: User identifier (email, display name, or account ID), or a JSON object string from jira_search_assignable_users. Pass None or empty string to unassign. Returns: JSON string representing the updated issue object. Raises: ValueError: If in read-only mode, Jira client unavailable, or user not found.
После (0.23.0)
Assign a Jira issue to a user using the dedicated assignment endpoint. This is more reliable than setting assignee via update_issue, which is silently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee.
jira_batch_create_issues: изменено: описание и схема входных данных
До (0.22.1)
Create multiple Jira issues in a batch. Args: ctx: The FastMCP context. issues: JSON array string of issue objects. validate_only: If true, only validates without creating. Returns: JSON string indicating success and listing created issues (or validation result). Raises: ValueError: If in read-only mode, Jira client unavailable, or invalid JSON.
После (0.23.0)
Create multiple Jira issues in a batch.
jira_batch_create_versions: изменено: описание и схема входных данных
До (0.22.1)
Batch create multiple versions in a Jira project. Args: ctx: The FastMCP context. project_key: The project key. versions: JSON array string of version objects. Returns: JSON array of results, each with success flag, version or error.
После (0.23.0)
Batch create multiple versions in a Jira project.
jira_batch_get_changelogs: изменено: описание и схема входных данных
До (0.22.1)
Get changelogs for multiple Jira issues (Cloud only). Args: ctx: The FastMCP context. issue_ids_or_keys: List of issue IDs or keys. fields: List of fields to filter changelogs by. None for all fields. limit: Maximum changelogs per issue (-1 for all). Returns: JSON string representing a list of issues with their changelogs. Raises: NotImplementedError: If run on Jira Server/Data Center. ValueError: If Jira client is unavailable.
После (0.23.0)
Get changelogs for multiple Jira issues (Cloud only).
jira_create_issue: изменено: описание и схема входных данных
До (0.22.1)
Create a new Jira issue with optional Epic link or parent for subtasks. Args: ctx: The FastMCP context. project_key: The JIRA project key. summary: Summary/title of the issue. issue_type: Issue type (e.g., 'Task', 'Bug', 'Story', 'Epic', 'Subtask'). assignee: Assignee's user identifier (string): Email, display name, or account ID (e.g., 'user@example.com', 'John Doe', 'accountid:...'). description: Issue description in Markdown format. components: Comma-separated list of component names. additional_fields: JSON string of additional fields. Returns: JSON string representing the created issue object. Raises: ValueError: If in read-only mode or Jira client is unavailable.
После (0.23.0)
Create a new Jira issue with optional Epic link or parent for subtasks.
jira_create_issue_link: изменено: описание и схема входных данных
До (0.22.1)
Create a link between two Jira issues. Args: ctx: The FastMCP context. link_type: The type of link (e.g., 'Blocks'). inward_issue_key: The key of the source issue. outward_issue_key: The key of the target issue. comment: Optional comment text. comment_visibility: Optional JSON string for comment visibility. Returns: JSON string indicating success or failure. Raises: ValueError: If required fields are missing, invalid input, in read-only mode, or Jira client unavailable.
После (0.23.0)
Create a link between two Jira issues.
jira_create_remote_issue_link: изменено: описание и схема входных данных
До (0.22.1)
Create a remote issue link (web link or Confluence link) for a Jira issue. This tool allows you to add web links and Confluence links to Jira issues. The links will appear in the issue's "Links" section and can be clicked to navigate to external resources. Args: ctx: The FastMCP context. issue_key: The key of the issue to add the link to. url: The URL to link to (can be any web page or Confluence page). title: The title/name that will be displayed for the link. summary: Optional description of what the link is for. relationship: Optional relationship description. icon_url: Optional URL to a 16x16 icon for the link. Returns: JSON string indicating success or failure. Raises: ValueError: If required fields are missing, invalid input, in read-only mode, or Jira client unavailable.
После (0.23.0)
Create a remote issue link (web link or Confluence link) for a Jira issue. This tool allows you to add web links and Confluence links to Jira issues. The links will appear in the issue's "Links" section and can be clicked to navigate to external resources.
jira_create_sprint: изменено: описание и схема входных данных
До (0.22.1)
Create Jira sprint for a board. Args: ctx: The FastMCP context. board_id: Board ID. name: Sprint name. start_date: Start date (ISO format). end_date: End date (ISO format). goal: Optional sprint goal. Returns: JSON string representing the created sprint object. Raises: ValueError: If in read-only mode or Jira client unavailable.
После (0.23.0)
Create Jira sprint for a board.
jira_create_version: изменено: описание и схема входных данных
До (0.22.1)
Create a new fix version in a Jira project. Args: ctx: The FastMCP context. project_key: The project key. name: Name of the version. start_date: Start date (optional). release_date: Release date (optional). description: Description (optional). Returns: JSON string of the created version object.
После (0.23.0)
Create a new fix version in a Jira project.
jira_delete_issue: изменено: описание и схема входных данных
До (0.22.1)
Delete an existing Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: JSON string indicating success. Raises: ValueError: If in read-only mode or Jira client unavailable.
После (0.23.0)
Delete an existing Jira issue.
jira_download_attachments: изменено: описание и схема входных данных
До (0.22.1)
Download attachments from a Jira issue. Returns attachment contents as base64-encoded embedded resources so that they are available over the MCP protocol without requiring filesystem access on the server. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: A list containing a text summary and one EmbeddedResource per successfully downloaded attachment.
После (0.23.0)
Download attachments from a Jira issue. Returns attachment contents as base64-encoded content so that they are available over the MCP protocol without requiring filesystem access on the server. Image attachments are returned as ``EmbeddedResource`` blobs; all other attachments (documents, archives, etc.) are returned as ``TextContent`` carrying a base64 payload, since many MCP clients only forward ``EmbeddedResource`` blobs for recognized image MIME types and otherwise drop the attachment (#1419).
jira_edit_comment: изменено: описание и схема входных данных
До (0.22.1)
Edit an existing comment on a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. comment_id: The ID of the comment to edit. body: Updated comment text in Markdown. visibility: (Optional) Comment visibility as JSON string. Returns: JSON string representing the updated comment object. Raises: ValueError: If in read-only mode or Jira client unavailable.
После (0.23.0)
Edit an existing comment on a Jira issue.
jira_get_agile_boards: изменено: описание и схема входных данных
До (0.22.1)
Get jira agile boards by name, project key, or type. Args: ctx: The FastMCP context. board_name: Name of the board (fuzzy search). project_key: Project key. board_type: Board type ('scrum' or 'kanban'). start_at: Starting index. limit: Maximum results. Returns: JSON string representing a list of board objects.
После (0.23.0)
Get jira agile boards by name, project key, or type.
jira_get_all_projects: изменено: описание и схема входных данных
До (0.22.1)
Get all Jira projects accessible to the current user. Args: ctx: The FastMCP context. include_archived: Whether to include archived projects. Returns: JSON string representing a list of project objects accessible to the user. Project keys are always returned in uppercase. If JIRA_PROJECTS_FILTER is configured, only returns projects matching those keys. Raises: ValueError: If the Jira client is not configured or available.
После (0.23.0)
Get all Jira projects accessible to the current user.
jira_get_board_issues: изменено: описание и схема входных данных
До (0.22.1)
Get all issues linked to a specific board filtered by JQL. Args: ctx: The FastMCP context. board_id: The ID of the board. jql: JQL query string to filter issues. fields: Comma-separated fields to return. start_at: Starting index for pagination. limit: Maximum number of results. expand: Optional fields to expand. Returns: JSON string representing the search results including pagination info.
После (0.23.0)
Get all issues linked to a specific board filtered by JQL.
jira_get_create_fields: изменено: описание и схема входных данных
До (0.22.1)
Get fields available for creating an issue of a specific type. Returns all fields (required and optional) for the given project and issue type, including field names, IDs, whether they're required, and their schema. Use jira_get_field_options when a returned field needs its allowed values. Args: ctx: The FastMCP context. project_key: The project key. issue_type_id: The issue type ID. Returns: JSON string with list of field metadata (field_id, name, required, schema).
После (0.23.0)
Get fields available for creating an issue of a specific type. Returns all fields (required and optional) for the given project and issue type, including field names, IDs, whether they're required, and their schema. Use jira_get_field_options when a returned field needs its allowed values.
jira_get_field_options: изменено: описание и схема входных данных
До (0.22.1)
Get allowed option values for a custom field. Returns the list of valid options for select, multi-select, radio, checkbox, and cascading select custom fields. Cloud: Uses the Field Context Option API. If context_id is not provided, automatically resolves to the global context. Server/DC: Uses createmeta to get allowedValues. Requires project_key and issue_type parameters. Args: ctx: The FastMCP context. field_id: The custom field ID. context_id: Field context ID (Cloud only, auto-resolved if omitted). project_key: Project key (required for Server/DC). issue_type: Issue type name (required for Server/DC). contains: Case-insensitive substring filter on option values. return_limit: Cap on number of results after filtering. values_only: Return compact format with only value strings. Returns: JSON string with the list of available options.
После (0.23.0)
Get allowed option values for a custom field. Returns the list of valid options for select, multi-select, radio, checkbox, and cascading select custom fields. Cloud: Uses the Field Context Option API. If context_id is not provided, automatically resolves to the global context. Server/DC: Uses createmeta to get allowedValues. Requires project_key and issue_type parameters.
jira_get_issue: изменено: описание и схема входных данных; новые аргументы: use_display_names
До (0.22.1)
Get details of a specific Jira issue. Includes Epic links and relationship information. Use the ``include`` parameter to inline enrichments (remote_links, transitions, watchers, changelog, comments, worklogs) so that separate tool calls are not needed. Args: ctx: The FastMCP context. issue_key: Jira issue key. fields: Comma-separated fields to return. expand: Optional fields to expand. comment_limit: Maximum number of comments. properties: Issue properties to return. update_history: Whether to update issue view history. include: Comma-separated enrichment sections to inline. Returns: JSON string representing the Jira issue object. Raises: ValueError: If the Jira client is not configured.
После (0.23.0)
Get details of a specific Jira issue. Includes Epic links and relationship information. Use the ``include`` parameter to inline enrichments (remote_links, transitions, watchers, changelog, comments, worklogs) so that separate tool calls are not needed.
jira_get_issue_dates: изменено: описание и схема входных данных
До (0.22.1)
Get date information and status transition history for a Jira issue. Returns dates (created, updated, due date, resolution date) and optionally status change history with time tracking for workflow analysis. Args: ctx: The FastMCP context. issue_key: The Jira issue key. include_status_changes: Whether to include status change history. include_status_summary: Whether to include aggregated time per status. Returns: JSON string with issue dates and optional status tracking data.
После (0.23.0)
Get date information and status transition history for a Jira issue. Returns dates (created, updated, due date, resolution date) and optionally status change history with time tracking for workflow analysis.
jira_get_issue_development_info: изменено: описание и схема входных данных
До (0.22.1)
Get development information (PRs, commits, branches) linked to a Jira issue. This retrieves the development panel information that shows linked pull requests, branches, and commits from connected source control systems like Bitbucket, GitHub, or GitLab. Args: ctx: The FastMCP context. issue_key: The Jira issue key. application_type: Optional filter by source control type. data_type: Optional filter by data type (pullrequest, branch, etc.). Returns: JSON string with development information including: - pullRequests: List of linked pull requests with status, author, reviewers - branches: List of linked branches - commits: List of linked commits - repositories: List of repositories involved
После (0.23.0)
Get development information (PRs, commits, branches) linked to a Jira issue. This retrieves the development panel information that shows linked pull requests, branches, and commits from connected source control systems like Bitbucket, GitHub, or GitLab.
jira_get_issue_images: изменено: описание и схема входных данных
До (0.22.1)
Get all images attached to a Jira issue as inline image content. Filters attachments to images only (PNG, JPEG, GIF, WebP, SVG, BMP) and returns them as base64-encoded ImageContent that clients can render directly. Non-image attachments are excluded. Files with ambiguous MIME types (application/octet-stream) are detected by filename extension as a fallback. Images larger than 50 MB are skipped with an error entry in the summary. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: A list with a text summary followed by one ImageContent per successfully downloaded image.
После (0.23.0)
Get all images attached to a Jira issue as inline image content. Filters attachments to images only (PNG, JPEG, GIF, WebP, SVG, BMP) and returns them as base64-encoded ImageContent that clients can render directly. Non-image attachments are excluded. Files with ambiguous MIME types (application/octet-stream) are detected by filename extension as a fallback. Images larger than 50 MB are skipped with an error entry in the summary.
jira_get_issue_proforma_forms: изменено: описание и схема входных данных
До (0.22.1)
Get all ProForma forms associated with a Jira issue. Uses the new Jira Forms REST API. Form IDs are returned as UUIDs. Args: ctx: The FastMCP context. issue_key: The issue key to get forms for. Returns: JSON string representing the list of ProForma forms, or an error object if failed.
После (0.23.0)
Get all ProForma forms associated with a Jira issue. Uses the new Jira Forms REST API. Form IDs are returned as UUIDs.
jira_get_issue_sla: изменено: описание и схема входных данных
До (0.22.1)
Calculate SLA metrics for a Jira issue. Computes various time-based metrics including cycle time, lead time, time spent in each status, due date compliance, and more. Working hours can be configured via environment variables: - JIRA_SLA_WORKING_HOURS_ONLY: Enable working hours filtering (true/false) - JIRA_SLA_WORKING_HOURS_START: Start time (e.g., "09:00") - JIRA_SLA_WORKING_HOURS_END: End time (e.g., "17:00") - JIRA_SLA_WORKING_DAYS: Working days (e.g., "1,2,3,4,5" for Mon-Fri) - JIRA_SLA_TIMEZONE: Timezone for calculations (e.g., "America/New_York") Args: ctx: The FastMCP context. issue_key: The Jira issue key. metrics: Comma-separated list of metrics to calculate. working_hours_only: Use working hours only for calculations. include_raw_dates: Include raw date values in response. Returns: JSON string with calculated SLA metrics.
После (0.23.0)
Calculate SLA metrics for a Jira issue. Computes various time-based metrics including cycle time, lead time, time spent in each status, due date compliance, and more. Working hours can be configured via environment variables: - JIRA_SLA_WORKING_HOURS_ONLY: Enable working hours filtering (true/false) - JIRA_SLA_WORKING_HOURS_START: Start time (e.g., "09:00") - JIRA_SLA_WORKING_HOURS_END: End time (e.g., "17:00") - JIRA_SLA_WORKING_DAYS: Working days (e.g., "1,2,3,4,5" for Mon-Fri) - JIRA_SLA_TIMEZONE: Timezone for calculations (e.g., "America/New_York")
jira_get_issue_watchers: изменено: описание и схема входных данных
До (0.22.1)
Get the list of watchers for a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: JSON string with watcher count and list of watchers. Raises: ValueError: If the Jira client is not configured or available.
После (0.23.0)
Get the list of watchers for a Jira issue.
jira_get_issues_development_info: изменено: описание и схема входных данных
До (0.22.1)
Get development information for multiple Jira issues. Batch retrieves development panel information (PRs, commits, branches) for multiple issues at once. Args: ctx: The FastMCP context. issue_keys: List of Jira issue keys. application_type: Optional filter by source control type. data_type: Optional filter by data type. Returns: JSON string with list of development information for each issue.
После (0.23.0)
Get development information for multiple Jira issues. Batch retrieves development panel information (PRs, commits, branches) for multiple issues at once.
jira_get_link_types: изменено: описание и схема входных данных
До (0.22.1)
Get all available issue link types. Args: ctx: The FastMCP context. name_filter: Optional substring to filter link types by name. Returns: JSON string representing a list of issue link type objects.
После (0.23.0)
Get all available issue link types.
jira_get_proforma_form_details: изменено: описание и схема входных данных
До (0.22.1)
Get detailed information about a specific ProForma form. Uses the new Jira Forms REST API. Returns form details including ADF design structure. Args: ctx: The FastMCP context. issue_key: The issue key containing the form. form_id: The form UUID identifier. Returns: JSON string representing the ProForma form details, or an error object if failed.
После (0.23.0)
Get detailed information about a specific ProForma form. Uses the new Jira Forms REST API. Returns form details including ADF design structure.

jira_get_project_components: изменено: схема входных данных

jira_get_project_fields: изменено: описание и схема входных данных
До (0.22.1)
Get the fields available on issues of a project (the create schema), deduplicated across the project's issue types — i.e. which fields tickets in this project have, regardless of whether they are filled. Args: ctx: The FastMCP context. project_key: The project key. Returns: JSON string with a list of fields: each {field_id, name, required, schema_type, custom, issue_types}. Empty list if none / on error. Raises: ValueError: If the Jira client is not configured or available.
После (0.23.0)
Get the fields available on issues of a project (the create schema), deduplicated across the project's issue types — i.e. which fields tickets in this project have, regardless of whether they are filled.
jira_get_project_issue_types: изменено: описание и схема входных данных
До (0.22.1)
Get available issue types for a Jira project. Returns the list of issue types (Bug, Task, Story, Epic, etc.) that can be created in the specified project. Use the returned issue type IDs with get_create_fields to discover what fields each type requires. Args: ctx: The FastMCP context. project_key: The project key. Returns: JSON string with list of issue types (id, name, description, subtask).
После (0.23.0)
Get available issue types for a Jira project. Returns the list of issue types (Bug, Task, Story, Epic, etc.) that can be created in the specified project. Use the returned issue type IDs with get_create_fields to discover what fields each type requires.
jira_get_project_issues: изменено: описание и схема входных данных
До (0.22.1)
Get all issues for a specific Jira project. Args: ctx: The FastMCP context. project_key: The project key. limit: Maximum number of results. start_at: Starting index for pagination. Returns: JSON string representing the search results including pagination info.
После (0.23.0)
Get all issues for a specific Jira project.

jira_get_project_versions: изменено: схема входных данных

jira_get_queue_issues: изменено: описание и схема входных данных
До (0.22.1)
Get issues from a Jira Service Desk queue. Server/Data Center only. Not available on Jira Cloud. Args: ctx: The FastMCP context. service_desk_id: Service desk ID. queue_id: Queue ID. start_at: Starting index for pagination. limit: Maximum number of issues to return. Returns: JSON string with queue metadata, issues, and pagination metadata. Raises: NotImplementedError: If connected to Jira Cloud (Server/DC only).
После (0.23.0)
Get issues from a Jira Service Desk queue. Server/Data Center only. Not available on Jira Cloud.
jira_get_service_desk_for_project: изменено: описание и схема входных данных
До (0.22.1)
Get the Jira Service Desk associated with a project key. Server/Data Center only. Not available on Jira Cloud. Args: ctx: The FastMCP context. project_key: Jira project key. Returns: JSON string with project key and service desk data (or null if not found). Raises: NotImplementedError: If connected to Jira Cloud (Server/DC only).
После (0.23.0)
Get the Jira Service Desk associated with a project key. Server/Data Center only. Not available on Jira Cloud.
jira_get_service_desk_queues: изменено: описание и схема входных данных
До (0.22.1)
Get queues for a Jira Service Desk. Server/Data Center only. Not available on Jira Cloud. Args: ctx: The FastMCP context. service_desk_id: Service desk ID. start_at: Starting index for pagination. limit: Maximum number of queues to return. Returns: JSON string with queue list and pagination metadata. Raises: NotImplementedError: If connected to Jira Cloud (Server/DC only).
После (0.23.0)
Get queues for a Jira Service Desk. Server/Data Center only. Not available on Jira Cloud.
jira_get_sprint_issues: изменено: описание и схема входных данных
До (0.22.1)
Get jira issues from sprint. Args: ctx: The FastMCP context. sprint_id: The ID of the sprint. fields: Comma-separated fields to return. start_at: Starting index. limit: Maximum results. Returns: JSON string representing the search results including pagination info.
После (0.23.0)
Get jira issues from sprint.
jira_get_sprints_from_board: изменено: описание и схема входных данных
До (0.22.1)
Get jira sprints from board by state. Args: ctx: The FastMCP context. board_id: The ID of the board. state: Sprint state ('active', 'future', 'closed'). If None, returns all sprints. start_at: Starting index. limit: Maximum results. Returns: JSON string representing a list of sprint objects.
После (0.23.0)
Get jira sprints from board by state.
jira_get_transitions: изменено: описание и схема входных данных
До (0.22.1)
Get available status transitions for a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: JSON string representing a list of available transitions.
После (0.23.0)
Get available status transitions for a Jira issue.
jira_get_user_profile: изменено: описание и схема входных данных
До (0.22.1)
Retrieve profile information for a specific Jira user. Args: ctx: The FastMCP context. user_identifier: User identifier (email, username, key, or account ID). Returns: JSON string representing the Jira user profile object, or an error object if not found. Raises: ValueError: If the Jira client is not configured or available.
После (0.23.0)
Retrieve profile information for a specific Jira user.
jira_get_worklog: изменено: описание и схема входных данных
До (0.22.1)
Get worklog entries for a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. Returns: JSON string representing the worklog entries.
После (0.23.0)
Get worklog entries for a Jira issue.
jira_link_to_epic: изменено: описание и схема входных данных
До (0.22.1)
Link an existing issue to an epic. Args: ctx: The FastMCP context. issue_key: The key of the issue to link. epic_key: The key of the epic to link to. Returns: JSON string representing the updated issue object. Raises: ValueError: If in read-only mode or Jira client unavailable.
После (0.23.0)
Link an existing issue to an epic.
jira_move_issue: изменено: описание и схема входных данных
До (0.22.1)
Move a Jira issue to a different project (Jira Cloud only). Uses Jira Cloud's bulk move API to perform a cross-project move. The issue keeps its current issue type and may be assigned a new key in the target project (e.g., OLDPROJ-123 becomes NEWPROJ-456). The move is processed asynchronously on Jira's side; this tool polls until confirmed or times out after 30 seconds. Args: ctx: The FastMCP context. issue_key: Jira issue key of the issue to move. target_project_key: Key of the target project. Returns: JSON string representing the moved issue with its new key and project. Raises: ValueError: If in read-only mode, Jira client unavailable, or the move fails. NotImplementedError: If not running on Jira Cloud.
После (0.23.0)
Move a Jira issue to a different project (Jira Cloud only). Uses Jira Cloud's bulk move API to perform a cross-project move. The issue keeps its current issue type and may be assigned a new key in the target project (e.g., OLDPROJ-123 becomes NEWPROJ-456). The move is processed asynchronously on Jira's side; this tool polls until confirmed or times out after 30 seconds.
jira_move_issues_to_backlog: изменено: описание и схема входных данных
До (0.22.1)
Move issues to the backlog, removing them from any sprint. Args: ctx: The FastMCP context. issue_keys: Comma-separated issue keys. Returns: JSON string with success message. Raises: ValueError: If in read-only mode or Jira client unavailable.
После (0.23.0)
Move issues to the backlog, removing them from any sprint.
jira_remove_issue_link: изменено: описание и схема входных данных
До (0.22.1)
Remove a link between two Jira issues. Args: ctx: The FastMCP context. link_id: The ID of the link to remove. Returns: JSON string indicating success. Raises: ValueError: If link_id is missing, in read-only mode, or Jira client unavailable.
После (0.23.0)
Remove a link between two Jira issues.
jira_remove_watcher: изменено: описание и схема входных данных
До (0.22.1)
Remove a user from watching a Jira issue. Args: ctx: The FastMCP context. issue_key: Jira issue key. username: Username to remove (Server/DC). account_id: Account ID to remove (Cloud). Returns: JSON string with success confirmation. Raises: ValueError: If the Jira client is not configured or available.
После (0.23.0)
Remove a user from watching a Jira issue.
jira_search: изменено: описание и схема входных данных; новые аргументы: use_display_names
До (0.22.1)
Search Jira issues using JQL (Jira Query Language). Args: ctx: The FastMCP context. jql: JQL query string. fields: Comma-separated fields to return. limit: Maximum number of results. start_at: Starting index for pagination. projects_filter: Comma-separated list of project keys to filter by. expand: Optional fields to expand. page_token: Pagination token from a previous search result (Cloud only). Returns: JSON string representing the search results including pagination info.
После (0.23.0)
Search Jira issues using JQL (Jira Query Language).
jira_search_assignable_users: изменено: описание и схема входных данных
До (0.22.1)
Search Jira users assignable in a given project or issue. Use this when you have a display name / partial name / email fragment and need a concrete identifier (``name`` / ``key`` for Server/DC, ``accountId`` for Cloud) to feed into assignee, reporter, watcher, etc. Returns the full result set so the caller can disambiguate when several users match — ``get_user_profile`` only resolves one identifier and is not designed for human-name search. Exactly one of ``project_key`` or ``issue_key`` must be provided — the underlying API (``/user/assignable/search``) requires a project or issue context and works without the global "Browse Users" permission that bot accounts in locked-down DC instances often lack. Args: ctx: The FastMCP context. query: Display name / username / email substring. project_key: Project key (e.g. 'DT') to scope the search. issue_key: Issue key (e.g. 'DT-779') to scope the search. limit: Maximum number of users to return. Returns: JSON string: {"success": true, "count": N, "users": [...]} on success, or an error object on failure.
После (0.23.0)
Search Jira users assignable in a given project or issue. Use this when you have a display name / partial name / email fragment and need a concrete identifier (``name`` / ``key`` for Server/DC, ``accountId`` for Cloud) to feed into assignee, reporter, watcher, etc. Returns the full result set so the caller can disambiguate when several users match — ``get_user_profile`` only resolves one identifier and is not designed for human-name search. Exactly one of ``project_key`` or ``issue_key`` must be provided — the underlying API (``/user/assignable/search``) requires a project or issue context and works without the global "Browse Users" permission that bot accounts in locked-down DC instances often lack.
jira_search_fields: изменено: описание и схема входных данных
До (0.22.1)
Search Jira fields by keyword with fuzzy match. Args: ctx: The FastMCP context. keyword: Keyword for fuzzy search. limit: Maximum number of results. refresh: Whether to force refresh the field list. Returns: JSON string representing a list of matching field definitions.
После (0.23.0)
Search Jira fields by keyword with fuzzy match.
jira_search_projects: изменено: описание и схема входных данных
До (0.22.1)
Search for Jira projects by name or key prefix. Uses the projects picker endpoint to return a ranked list of matching projects without fetching every visible project on the instance. Args: ctx: The FastMCP context. query: Name or key prefix to search for. max_results: Maximum number of results to return. current_project_ids: Comma-separated project IDs to exclude. Returns: JSON string representing a list of matching project objects. Project keys are always returned in uppercase. If JIRA_PROJECTS_FILTER is configured, only returns projects matching those keys.
После (0.23.0)
Search for Jira projects by name or key prefix. Uses the projects picker endpoint to return a ranked list of matching projects without fetching every visible project on the instance.
jira_transition_issue: изменено: описание и схема входных данных
До (0.22.1)
Transition a Jira issue to a new status. Args: ctx: The FastMCP context. issue_key: Jira issue key. transition_id: ID of the transition. fields: Optional JSON string of fields to update during transition. comment: Optional comment for the transition in Markdown format. Returns: JSON string representing the updated issue object. Raises: ValueError: If required fields missing, invalid input, in read-only mode, or Jira client unavailable.
После (0.23.0)
Transition a Jira issue to a new status.
jira_update_issue: изменено: описание и схема входных данных; новые аргументы: return_fields
До (0.22.1)
Update an existing Jira issue including changing status, adding Epic links, updating fields, etc. Args: ctx: The FastMCP context. issue_key: Jira issue key. fields: JSON string of fields to update. Text fields like 'description' should use Markdown format. additional_fields: Optional JSON string of additional fields. components: Comma-separated list of component names. attachments: Optional JSON array string or comma-separated list of file paths. Returns: JSON string representing the updated issue object and attachment results. Raises: ValueError: If in read-only mode or Jira client unavailable, or invalid input.
После (0.23.0)
Update an existing Jira issue including changing status, adding Epic links, updating fields, etc.
jira_update_proforma_form_answers: изменено: описание и схема входных данных
До (0.22.1)
Update form field answers using the Jira Forms REST API. This is the primary method for updating form data. Each answer object must specify the question ID, answer type, and value. **⚠️ KNOWN LIMITATION - DATETIME fields:** The Jira Forms API does NOT properly preserve time components in DATETIME fields. Only the date portion is stored; times are reset to midnight (00:00:00). **Workaround for DATETIME fields:** Use jira_update_issue to directly update the underlying custom fields instead: 1. Get the custom field ID from the form details (question's "jiraField" property) 2. Use jira_update_issue with fields like: {"customfield_XXXXX": "2026-01-09T11:50:00-08:00"} Example: ```python # Instead of updating via form (loses time): # jira_update_proforma_form_answers(issue_key, form_id, [{"questionId": "91", "type": "DATETIME", "value": "..."}]) # Use direct field update (preserves time): jira_update_issue(issue_key, {"customfield_10542": "2026-01-09T11:50:00-08:00"}) ``` **Automatic DateTime Conversion:** For DATE and DATETIME fields, you can provide values as: - ISO 8601 strings (e.g., "2024-12-17T19:00:00Z", "2024-12-17") - Unix timestamps in milliseconds (e.g., 1734465600000) The tool automatically converts ISO 8601 strings to Unix timestamps. Example answers: [ {"questionId": "q1", "type": "TEXT", "value": "Updated description"}, {"questionId": "q2", "type": "SELECT", "value": "Product A"}, {"questionId": "q3", "type": "NUMBER", "value": 42}, {"questionId": "q4", "type": "DATE", "value": "2024-12-17"} ] Common answer types: - TEXT: String values - NUMBER: Numeric values - DATE: Date values (ISO 8601 string or Unix timestamp in ms) - DATETIME: DateTime values - ⚠️ USE WORKAROUND ABOVE - SELECT: Single selection from options - MULTI_SELECT: Multiple selections (value as list) - CHECKBOX: Boolean values Args: ctx: The FastMCP context. issue_key: The issue key containing the form. form_id: The form UUID (get from get_issue_proforma_forms). answers: List of answer objects with questionId, type, and value. Returns: JSON string with operation result.
После (0.23.0)
Update form field answers using the Jira Forms REST API. This is the primary method for updating form data. Each answer object must specify the question ID, answer type, and value. **⚠️ KNOWN LIMITATION - DATETIME fields:** The Jira Forms API does NOT properly preserve time components in DATETIME fields. Only the date portion is stored; times are reset to midnight (00:00:00). **Workaround for DATETIME fields:** Use jira_update_issue to directly update the underlying custom fields instead: 1. Get the custom field ID from the form details (question's "jiraField" property) 2. Use jira_update_issue with fields like: {"customfield_XXXXX": "2026-01-09T11:50:00-08:00"} Example: ```python # Instead of updating via form (loses time): # jira_update_proforma_form_answers(issue_key, form_id, [{"questionId": "91", "type": "DATETIME", "value": "..."}]) # Use direct field update (preserves time): jira_update_issue(issue_key, {"customfield_10542": "2026-01-09T11:50:00-08:00"}) ``` **Automatic DateTime Conversion:** For DATE and DATETIME fields, you can provide values as: - ISO 8601 strings (e.g., "2024-12-17T19:00:00Z", "2024-12-17") - Unix timestamps in milliseconds (e.g., 1734465600000) The tool automatically converts ISO 8601 strings to Unix timestamps. Example answers: [ {"questionId": "q1", "type": "TEXT", "value": "Updated description"}, {"questionId": "q2", "type": "SELECT", "value": "Product A"}, {"questionId": "q3", "type": "NUMBER", "value": 42}, {"questionId": "q4", "type": "DATE", "value": "2024-12-17"} ] Common answer types: - TEXT: String values - NUMBER: Numeric values - DATE: Date values (ISO 8601 string or Unix timestamp in ms) - DATETIME: DateTime values - ⚠️ USE WORKAROUND ABOVE - SELECT: Single selection from options - MULTI_SELECT: Multiple selections (value as list) - CHECKBOX: Boolean values
jira_update_sprint: изменено: описание и схема входных данных
До (0.22.1)
Update jira sprint. Args: ctx: The FastMCP context. sprint_id: The ID of the sprint. name: Optional new name. state: Optional new state (future|active|closed). start_date: Optional new start date. end_date: Optional new end date. goal: Optional new goal. Returns: JSON string representing the updated sprint object or an error message. Raises: ValueError: If in read-only mode or Jira client unavailable.
После (0.23.0)
Update jira sprint.
jira_update_version: изменено: описание и схема входных данных
До (0.22.1)
Update an existing fix version in a Jira project. Only fields explicitly provided are modified; other attributes of the version are left untouched. Useful for archiving/unarchiving versions, renaming, or shifting release dates without recreating them. Args: ctx: The FastMCP context. version_id: Numeric ID of the version to update. name: New name (optional). description: New description (optional). start_date: New start date YYYY-MM-DD (optional). release_date: New release date YYYY-MM-DD (optional). archived: Archived flag (optional). released: Released flag (optional). Returns: JSON string of the updated version object.
После (0.23.0)
Update an existing fix version in a Jira project. Only fields explicitly provided are modified; other attributes of the version are left untouched. Useful for archiving/unarchiving versions, renaming, or shifting release dates without recreating them.

0.22.0 → 0.22.1

выпуск patch, 11 июля 2026 г.

jira_get_board_issues: изменено: схема входных данных

jira_get_issue: изменено: схема входных данных

jira_get_sprint_issues: изменено: схема входных данных

jira_search: изменено: схема входных данных

0.21.1 → 0.22.0

выпуск minor, 10 июля 2026 г.

Добавлено: jira_assign_issue, jira_get_create_fields, jira_get_project_fields, jira_get_project_issue_types, jira_move_issue, jira_move_issues_to_backlog, jira_search_assignable_users, jira_search_projects, jira_update_version

jira_get_board_issues: изменено: схема входных данных

jira_get_issue: изменено: описание и схема входных данных; новые аргументы: include
До (0.21.1)
Get details of a specific Jira issue including its Epic links and relationship information. Args: ctx: The FastMCP context. issue_key: Jira issue key. fields: Comma-separated list of fields to return (e.g., 'summary,status,customfield_10010'), a single field as a string (e.g., 'duedate'), '*all' for all fields, or omitted for essentials. expand: Optional fields to expand. comment_limit: Maximum number of comments. properties: Issue properties to return. update_history: Whether to update issue view history. Returns: JSON string representing the Jira issue object. Raises: ValueError: If the Jira client is not configured or available.
После (0.22.0)
Get details of a specific Jira issue. Includes Epic links and relationship information. Use the ``include`` parameter to inline enrichments (remote_links, transitions, watchers, changelog, comments, worklogs) so that separate tool calls are not needed. Args: ctx: The FastMCP context. issue_key: Jira issue key. fields: Comma-separated fields to return. expand: Optional fields to expand. comment_limit: Maximum number of comments. properties: Issue properties to return. update_history: Whether to update issue view history. include: Comma-separated enrichment sections to inline. Returns: JSON string representing the Jira issue object. Raises: ValueError: If the Jira client is not configured.

jira_get_issue_development_info: изменено: схема входных данных

jira_get_issues_development_info: изменено: схема входных данных

jira_get_sprint_issues: изменено: схема входных данных

jira_search: изменено: схема входных данных

0.21.0 → 0.21.1

выпуск patch, 10 апреля 2026 г.

jira_get_board_issues: изменено: схема входных данных

jira_get_issue: изменено: схема входных данных

jira_get_sprint_issues: изменено: схема входных данных

jira_search: изменено: схема входных данных

Проверенные выпуски: 0.21.0 (2026-03-02); 0.21.1 (2026-04-10); 0.22.0 (2026-07-10); 0.22.1 (2026-07-11); 0.23.0 (2026-07-18); 0.23.1 (2026-08-19); 0.24.0 (2026-11-08); 0.24.1 (2026-11-08); 0.24.2 (2026-11-12); 0.24.3 (2026-11-12).

Инструменты в 0.24.3

Отпечаток — это SHA-256 имени, описания и схемы входных данных инструмента, как его записывает verfy.lock. Тот же отпечаток в вашем lock-файле значит, что агент читает ровно это определение. Verfy 0.16.0 и новее фиксирует также заголовок, аннотации и схему вывода, если сервер их отдаёт, поэтому у такого инструмента в вашем lock-файле отпечаток будет другим.

Инструменты в 0.24.3
ИнструментОписаниеОтпечаток
jira_get_user_profileRetrieve profile information for a Jira user. Use ``user_identifier="me"`` to return the account authenticated for the current request directly from Jira's ``/myself`` endpoint. This path does not require Browse Users permission.a028e076f978
jira_search_assignable_usersSearch Jira users assignable in a given project or issue. Use this when you have a display name / partial name / email fragment and need a concrete identifier (``name`` / ``key`` for Server/DC, ``accountId`` for Cloud) to feed into assignee, reporter, watcher, etc. Returns the full result set so the caller can disambiguate when several users match — ``get_user_profile`` only resolves one identifier and is not designed for human-name search. Exactly one of ``project_key`` or ``issue_key`` must be provided — the underlying API (``/user/assignable/search``) requires a project or issue context and works without the global "Browse Users" permission that bot accounts in locked-down DC instances often lack.d90ed2c762a9
jira_get_issue_watchersGet the list of watchers for a Jira issue.7dd87da8ed94
jira_add_watcherAdd a user as a watcher to a Jira issue.6781ecf94f42
jira_remove_watcherRemove a user from watching a Jira issue.f13aabf7c4df
jira_get_issueGet details of a specific Jira issue. Includes Epic links and relationship information. Use the ``include`` parameter to inline enrichments (remote_links, transitions, watchers, changelog, comments, worklogs, epic_summary) so that separate tool calls are not needed. The ``epic_summary`` section only applies when the issue is an Epic and adds child-issue aggregations (counts by status, assignee, and type, plus a completion percentage); it is aggregate-only unless ``epic_summary_children`` is set.f65ea5e0f5ad
jira_searchSearch Jira issues using JQL (Jira Query Language).ae5319d868b2
jira_search_fieldsSearch Jira fields by keyword with fuzzy match.2e5e1e512717
jira_get_field_optionsGet allowed option values for a custom field. Returns the list of valid options for select, multi-select, radio, checkbox, and cascading select custom fields. Cloud: Uses the Field Context Option API. If context_id is not provided, automatically resolves to the global context. Server/DC: Uses createmeta to get allowedValues. Requires project_key and issue_type parameters.0b6054cce7ef
jira_get_project_issuesGet all issues for a specific Jira project.29c9e086c8ce
jira_get_transitionsGet available status transitions for a Jira issue.61ceec29a95d
jira_get_worklogGet worklog entries for a Jira issue.7229af3c22d2
jira_download_attachmentsDownload attachments from a Jira issue. Returns attachment contents as base64-encoded content so that they are available over the MCP protocol without requiring filesystem access on the server. Image attachments are returned as ``EmbeddedResource`` blobs; all other attachments (documents, archives, etc.) are returned as ``TextContent`` carrying a base64 payload, since many MCP clients only forward ``EmbeddedResource`` blobs for recognized image MIME types and otherwise drop the attachment (#1419).2a82203e04a0
jira_get_issue_imagesGet all images attached to a Jira issue as inline image content. Filters attachments to images only (PNG, JPEG, GIF, WebP, SVG, BMP) and returns them as base64-encoded ImageContent that clients can render directly. Non-image attachments are excluded. Files with ambiguous MIME types (application/octet-stream) are detected by filename extension as a fallback. Images larger than 50 MB are skipped with an error entry in the summary.153bae279e5b
jira_get_agile_boardsGet jira agile boards by name, project key, or type.d6162c0194d6
jira_get_board_issuesGet all issues linked to a specific board filtered by JQL.7ad7f96aa416
jira_get_sprints_from_boardGet jira sprints from board by state.854765a79406
jira_get_sprint_issuesGet jira issues from sprint.089fbae46787
jira_get_link_typesGet all available issue link types.ee4764575005
jira_create_issueCreate a new Jira issue with optional Epic link or parent for subtasks.3a24b27ae911
jira_batch_create_issuesCreate multiple Jira issues in a batch.25a85f021687
jira_batch_get_changelogsGet changelogs for multiple Jira issues (Cloud only).e7cd05d18261
jira_update_issueUpdate an issue and optionally transition, comment, and log work.5e9c5f85c1bd
jira_assign_issueAssign a Jira issue to a user using the dedicated assignment endpoint. This is more reliable than setting assignee via update_issue, which is silently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee. On Jira Server/DC the following identifier forms are all accepted: login name, email address, display name, or JIRAUSER key. The resolution order is: key lookup → email search (with email-as-username fallback) → text search → assignable-user search scoped to the issue.e1b8efbd1b70
jira_delete_issueDelete an existing Jira issue.230f7af9db9c
jira_move_issueMove a Jira issue to a different project (Jira Cloud only). Uses Jira Cloud's bulk move API to perform a cross-project move. The issue keeps its current issue type and may be assigned a new key in the target project (e.g., OLDPROJ-123 becomes NEWPROJ-456). The move is processed asynchronously on Jira's side; this tool polls until confirmed or times out after 30 seconds.8ca931bc4199
jira_add_commentAdd a comment to a Jira issue.92286e5e5310
jira_edit_commentEdit an existing comment on a Jira issue.ab0b55226c74
jira_add_worklogAdd a worklog entry to a Jira issue.6cffa4a30177
jira_link_to_epicLink an existing issue to an epic.47c8ecc2f4d2
jira_create_issue_linkCreate a link between two Jira issues.7667f99ffe75
jira_create_remote_issue_linkCreate a remote issue link (web link or Confluence link) for a Jira issue. This tool allows you to add web links and Confluence links to Jira issues. The links will appear in the issue's "Links" section and can be clicked to navigate to external resources.b209a3365237
jira_remove_issue_linkRemove a link between two Jira issues.7f5e220cd386
jira_transition_issueTransition a Jira issue to a new status.899ce2ae4643
jira_create_sprintCreate Jira sprint for a board.7832f64de4b8
jira_update_sprintUpdate jira sprint.99365c252b53
jira_add_issues_to_sprintAdd issues to a Jira sprint.cb4e95fea19b
jira_move_issues_to_backlogMove issues to the backlog, removing them from any sprint.2490f9a9d352
jira_get_project_issue_typesGet available issue types for a Jira project. Returns the list of issue types (Bug, Task, Story, Epic, etc.) that can be created in the specified project. Use the returned issue type IDs with get_create_fields to discover what fields each type requires.ebc07fa468e7
jira_get_create_fieldsGet fields available for creating an issue of a specific type. Returns all fields (required and optional) for the given project and issue type, including field names, IDs, whether they're required, and their schema. Use jira_get_field_options when a returned field needs its allowed values.8b603334744f
jira_get_project_versionsGet all fix versions for a specific Jira project.978eb60c6ed6
jira_get_project_componentsGet all components for a specific Jira project.124daf0fc6b2
jira_get_all_projectsGet all Jira projects accessible to the current user.c1fb94b371f0
jira_search_projectsSearch for Jira projects by name or key prefix. Uses the projects picker endpoint to return a ranked list of matching projects without fetching every visible project on the instance.dc647cc65729
jira_get_project_fieldsGet the fields available on issues of a project (the create schema), deduplicated across the project's issue types — i.e. which fields tickets in this project have, regardless of whether they are filled.53f6f8c57fae
jira_get_service_desk_for_projectGet the Jira Service Desk associated with a project key. Server/Data Center only. Not available on Jira Cloud.48042cbed908
jira_get_service_desk_queuesGet queues for a Jira Service Desk. Server/Data Center only. Not available on Jira Cloud.9b389b0b4302
jira_get_queue_issuesGet issues from a Jira Service Desk queue. Server/Data Center only. Not available on Jira Cloud.2f012b237581
jira_get_request_typesGet request types for a Jira Service Management service desk.855e3d6cfe70
jira_get_request_type_fieldsGet field definitions for a Jira Service Management request type.e43c6dca09d2
jira_create_customer_requestCreate a Jira Service Management customer request.a9e9a3b2136b
jira_create_versionCreate a new fix version in a Jira project.9201fc46045b
jira_batch_create_versionsBatch create multiple versions in a Jira project.e5c9694ba41d
jira_update_versionUpdate an existing fix version in a Jira project. Only fields explicitly provided are modified; other attributes of the version are left untouched. Useful for archiving/unarchiving versions, renaming, or shifting release dates without recreating them.bea2651e8e27
jira_get_issue_proforma_formsGet all ProForma forms associated with a Jira issue. Uses the new Jira Forms REST API. Form IDs are returned as UUIDs.c4d77461bac4
jira_get_proforma_form_detailsGet detailed information about a specific ProForma form. Uses the new Jira Forms REST API. Returns form details including ADF design structure.7eb1563c4970
jira_update_proforma_form_answersUpdate form field answers using the Jira Forms REST API. This is the primary method for updating form data. Each answer object must specify the question ID, answer type, and value. **⚠️ KNOWN LIMITATION - DATETIME fields:** The Jira Forms API does NOT properly preserve time components in DATETIME fields. Only the date portion is stored; times are reset to midnight (00:00:00). **Workaround for DATETIME fields:** Use jira_update_issue to directly update the underlying custom fields instead: 1. Get the custom field ID from the form details (question's "jiraField" property) 2. Use jira_update_issue with fields like: {"customfield_XXXXX": "2026-01-09T11:50:00-08:00"} Example: ```python # Instead of updating via form (loses time): # jira_update_proforma_form_answers(issue_key, form_id, [{"questionId": "91", "type": "DATETIME", "value": "..."}]) # Use direct field update (preserves time): jira_update_issue(issue_key, {"customfield_10542": "2026-01-09T11:50:00-08:00"}) ``` **Automatic DateTime Conversion:** For DATE and DATETIME fields, you can provide values as: - ISO 8601 strings (e.g., "2024-12-17T19:00:00Z", "2024-12-17") - Unix timestamps in milliseconds (e.g., 1734465600000) The tool automatically converts ISO 8601 strings to Unix timestamps. Example answers: [ {"questionId": "q1", "type": "TEXT", "value": "Updated description"}, {"questionId": "q2", "type": "SELECT", "value": "Product A"}, {"questionId": "q3", "type": "NUMBER", "value": 42}, {"questionId": "q4", "type": "DATE", "value": "2024-12-17"} ] Common answer types: - TEXT: String values - NUMBER: Numeric values - DATE: Date values (ISO 8601 string or Unix timestamp in ms) - DATETIME: DateTime values - ⚠️ USE WORKAROUND ABOVE - SELECT: Single selection from options - MULTI_SELECT: Multiple selections (value as list) - CHECKBOX: Boolean values7096066d924a
jira_get_issue_datesGet date information and status transition history for a Jira issue. Returns dates (created, updated, due date, resolution date) and optionally status change history with time tracking for workflow analysis.f2c9650bdfc7
jira_get_issue_slaCalculate SLA metrics for a Jira issue. Computes various time-based metrics including cycle time, lead time, time spent in each status, due date compliance, and more. Working hours can be configured via environment variables: - JIRA_SLA_WORKING_HOURS_ONLY: Enable working hours filtering (true/false) - JIRA_SLA_WORKING_HOURS_START: Start time (e.g., "09:00") - JIRA_SLA_WORKING_HOURS_END: End time (e.g., "17:00") - JIRA_SLA_WORKING_DAYS: Working days (e.g., "1,2,3,4,5" for Mon-Fri) - JIRA_SLA_TIMEZONE: Timezone for calculations (e.g., "America/New_York")c540b5f91743
jira_get_issue_development_infoGet development information (PRs, commits, branches) linked to a Jira issue. This retrieves the development panel information that shows linked pull requests, branches, and commits from connected source control systems like Bitbucket, GitHub, or GitLab.580f1942b60b
jira_get_issues_development_infoGet development information for multiple Jira issues. Batch retrieves development panel information (PRs, commits, branches) for multiple issues at once.17f40182fa6f
jira_get_project_epic_hierarchyGroup a project's epics under their cross-project parent issues. Fetches all epics in the project, detects their parent issue via the parent field or inward issue links, then groups them by parent. Epics with no detected parent appear under "Unlinked". Useful for understanding how a project's epics roll up to initiatives in another project.207344e93a17
jira_get_cross_project_dependenciesFind all cross-project issue links for a project. Scans issues in the project, extracts every issue link whose target belongs to a different project, and groups them by target project and link type. Useful for dependency analysis across multi-project Jira setups.4300bd7096fa

Зафиксируйте эти инструменты

Зафиксируйте то, что mcp-atlassian отдаёт вам сегодня, закоммитьте lock-файл, и pull request провалится, когда инструмент изменится, с текстом до и после. Зафиксируйте и версию пакета в MCP-конфигурации.

$ pip install verfy
$ verfy lock check --update   # показывает каждый инструмент и пишет verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, после actions/checkout
- uses: verfy-dev/verfy-action@v1

Поддерживаете этот сервер? Запускайте ту же проверку на своих выпусках и добавьте значок Locked by Verfy в README.