com.mcparmory/atlassian-jira
PYPI · MCPARMORY-ATLASSIAN-JIRA · 2 COMPONENTS · SCANNED SEP 20
Create, search, and manage issues, projects, and team workflows
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 37126 tokens (~117/item across 317 items; 317 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety99
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 45 of 47 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "transfer_filter_ownership" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 317 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/atlassian-jira MCP server?
com.mcparmory/atlassian-jira runs locally as a PyPI package, launched with uvx mcparmory-atlassian-jira. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-atlassian-jira
claude mcp add com-mcparmory-atlassian-jira -- uvx mcparmory-atlassian-jira
{
"mcpServers": {
"com-mcparmory-atlassian-jira": {
"command": "uvx",
"args": [
"mcparmory-atlassian-jira"
]
}
}
} {
"servers": {
"com-mcparmory-atlassian-jira": {
"command": "uvx",
"args": [
"mcparmory-atlassian-jira"
]
}
}
} codex mcp add com-mcparmory-atlassian-jira -- uvx mcparmory-atlassian-jira
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-atlassian-jira": {
"type": "local",
"command": [
"uvx",
"mcparmory-atlassian-jira"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-atlassian-jira --command uvx --arg mcparmory-atlassian-jira
mcp_servers:
com-mcparmory-atlassian-jira:
command: "uvx"
args: ["mcparmory-atlassian-jira"] {
"McpServers": {
"com-mcparmory-atlassian-jira": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-atlassian-jira"
]
}
}
} assistant mcp add com-mcparmory-atlassian-jira -t stdio -c uvx -a mcparmory-atlassian-jira
{
"mcpServers": {
"com-mcparmory-atlassian-jira": {
"command": "uvx",
"args": [
"mcparmory-atlassian-jira"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −2
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −2
- Stability: pass → 0.80 functional
- 10 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcparmory-atlassian-jira@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
remove_worklog_property Remove Worklog Property ~107
Removes a custom property from a worklog entry. Requires appropriate project and worklog visibility permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the project key followed by issue number (e.g., PROJ-123). |
| propertyKey | string | yes | The identifier of the custom property to delete from the worklog. |
| worklogId | string | yes | The unique identifier of the worklog entry from which the property will be removed. |
No output schema declared.
No examples provided.
reorder_custom_field_options Reorder Custom Field Options ~179
Reorder custom field options within a specific context. Rearranges the display order of custom field options or cascading options by specifying their desired sequence.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | The ID of the custom field option or cascading option to place the moved options after. Required if `position` isn't provided. |
| contextId | string | yes | The unique identifier of the context in which the custom field options are defined. |
| customFieldOptionIds | array | yes | An ordered list of custom field option IDs that defines their new sequence. All IDs must be either custom field options or cascading options, but not a mix of both types. |
| fieldId | string | yes | The unique identifier of the custom field containing the options to reorder. |
| position | string | – | The position the custom field options should be moved to. Required if `after` isn't provided. |
No output schema declared.
No examples provided.
reorder_version Reorder Version ~106
Changes the sequence position of a version within its project, affecting how versions are displayed in Jira. Requires browse permissions on the project containing the version.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | The URL (self link) of the version after which to place the moved version. Cannot be used with `position`. |
| id | string | yes | The unique identifier of the version to reorder. |
| position | string | – | An absolute position in which to place the moved version. Cannot be used with `after`. |
No output schema declared.
No examples provided.
replace_field_option Replace Field Option ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldKey | string | yes | The field key in the format app-key__field-key (e.g., example-add-on__example-issue-field). Retrieve this value from the app's plugin descriptor or by calling Get fields. |
| jql | string | – | A JQL query that limits the operation to a specific set of issues (e.g., project=10000). If not provided, the operation applies to all issues with the option selected. |
| optionId | string | yes | The numeric ID of the select-list option to be deselected from all issues. |
| overrideEditableFlag | boolean | – | Whether to override screen security to allow editing of uneditable fields. Only available to Connect and Forge app users with Administer Jira permission. Defaults to false. |
| replaceWith | string | – | The numeric ID of the option that will replace the deselected option. If not provided, the option is simply removed without replacement. |
No output schema declared.
No examples provided.
replace_project_role_actors Replace Project Role Actors ~178
Replace all actors assigned to a project role. This operation overwrites the existing actor list entirely; to add actors without removing existing ones, use the add actors operation instead.
| Name | Type | Req | Description |
|---|---|---|---|
| categorisedActors | object | – | The actors to assign to the project role, replacing all current assignments. Specify groups by ID (recommended) or name, and users by account ID. Use the appropriate actor type key (atlassian-group-r… |
| id | string | yes | The numeric ID of the project role to modify. Retrieve available project role IDs using the get all project roles operation. |
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (case-sensitive string). |
No output schema declared.
No examples provided.
restore_custom_field Restore Custom Field ~45
Restore a custom field from trash back to active use. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the custom field to restore from trash. |
No output schema declared.
No examples provided.
restore_issues Restore Issues ~106
Restore up to 1000 archived issues in a single request using their issue keys or IDs. Returns details of successfully restored issues and any errors encountered. Requires Jira admin permissions and a Premium or Enterprise license.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdsOrKeys | array | – | Array of issue keys or issue IDs to restore. You can restore up to 1000 issues per request. Subtasks cannot be restored directly; restore their parent issues instead. Only applicable to software, ser… |
No output schema declared.
No examples provided.
restore_project Restore Project ~77
Restore a project that has been archived or moved to the Jira recycle bin. Requires Administer Jira global permission for Company managed projects, or Administer Jira global permission or Administer projects project permission for Team managed projects.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (case sensitive). |
No output schema declared.
No examples provided.
retrieve_issue Retrieve Issue ~137
Retrieve detailed information about a specific issue by its ID or key. The operation performs case-insensitive matching and checks for moved issues, returning the current issue details without redirects. Requires browse permission for the project and any applicable issue-level security permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The unique identifier for the issue, either its numeric ID or alphanumeric key (e.g., PROJ-123). The search is case-insensitive and will locate moved issues. |
| updateHistory | boolean | – | When enabled, adds the issue's project to your recently viewed projects list and updates the lastViewed field for JQL searches. Defaults to disabled. |
No output schema declared.
No examples provided.
retrieve_issue_votes Retrieve Issue Votes ~72
Retrieve voting details for an issue, including vote count and voter information. Requires the voting feature to be enabled in Jira configuration and appropriate project permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the project key followed by issue number (e.g., PROJ-123). |
No output schema declared.
No examples provided.
retrieve_plan Retrieve Plan ~48
Retrieves detailed information about a specific plan by its ID. Requires Jira administrator permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| planId | string | yes | The unique identifier of the plan to retrieve, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
search_browsable_users Search Browsable Users ~258
Search for users who have permission to browse issues and match the given search criteria. Results can be filtered by a specific issue or project, with privacy controls applied based on user preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| issueKey | string | – | The issue key for the issue. Required, unless `projectKey` is specified. |
| maxResults | string | – | The maximum number of users to return per page, up to 50 by default. The operation may return fewer results if fewer users match the search criteria. |
| projectKey | string | – | The project key for the project (case sensitive). Required, unless `issueKey` is specified. |
| query | string | – | A query string that is matched against user attributes, such as `displayName` and `emailAddress`, to find relevant users. The string can match the prefix of the attribute's value. For example, *query… |
| startAt | string | – | The starting position for pagination, where 0 is the first user. Use this to retrieve subsequent pages of results. |
No output schema declared.
No examples provided.
search_dashboards Search Dashboards ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboardName | string | – | Filter dashboards by name using case-insensitive partial matching. |
| maxResults | string | – | Maximum number of dashboards to return per page. Defaults to 50. |
| orderBy | string | – | Sort results by a field: description, favorite count, ID, favorite status, name, or owner. Prefix with `-` for descending order or `+` for ascending order. Defaults to sorting by name. |
| projectId | string | – | Filter dashboards to only those shared with a specific project by its ID. |
| startAt | string | – | The starting position for pagination (zero-indexed). Defaults to 0. |
| status | string | – | Filter dashboards by their status: active, archived, or deleted. Defaults to active. |
No output schema declared.
No examples provided.
search_field_options Search Field Options ~159
Search for visible options in a Connect app custom select list field. Returns paginated results filtered by user permissions and optionally by project.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldKey | string | yes | The field identifier in the format appKey__fieldKey (e.g., example-add-on__example-issue-field). Retrieve this value from the app's plugin descriptor or by calling Get fields. |
| maxResults | string | – | Maximum number of options to return per page. Defaults to 50 if not specified. |
| projectId | string | – | Restrict results to options available in a specific project. When omitted, returns options available across all projects. |
| startAt | string | – | The starting position for pagination (0-based index). Use this to retrieve subsequent pages of results. |
No output schema declared.
No examples provided.
search_filters Search Filters ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filterName | string | – | Partial filter name to search for using case-insensitive matching. Matching behavior depends on the isSubstringMatch parameter. |
| isSubstringMatch | boolean | – | When true, performs case-insensitive substring matching on the filter name. When false, uses full text search syntax. Defaults to false. |
| maxResults | string | – | Maximum number of filters to return per page. Defaults to 50 results. |
| orderBy | string | – | Sort results by a field: name, description, ID, owner, favorite count, whether marked as favorite, or whether shared. Prefix with '-' for descending or '+' for ascending order. |
| projectId | string | – | Filter results to only those shared with a specific project by its ID. |
| startAt | string | – | Zero-based index for pagination, indicating which result to start from. Defaults to 0 for the first page. |
No output schema declared.
No examples provided.
search_groups Search Groups ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseInsensitive | boolean | – | Whether the group name search should ignore case distinctions. Defaults to case-sensitive matching when not specified. |
| maxResults | string | – | Maximum number of groups to return in the results. Limited by the system's autocomplete configuration, typically capped at a system-defined threshold. |
No output schema declared.
No examples provided.
search_issues Search Issues ~205
Search for issues using JQL (Jira Query Language) with optional read-after-write consistency reconciliation. Results reflect issues where you have browse permissions on the containing project and any applicable issue-level security permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| jql | string | – | A JQL expression to filter issues. Must include a search restriction (bounded query) for performance—for example, filtering by project, assignee, or status. The orderBy clause supports a maximum of 7… |
| maxResults | string | – | Maximum number of issues to return per page, up to 5000. The API may return fewer items when many fields or properties are requested. Defaults to 50 items per page. |
| reconcileIssues | array | – | List of up to 50 issue IDs to reconcile with search results for stronger consistency guarantees. Use this when read-after-write consistency is critical. The same list should be included across all pa… |
No output schema declared.
No examples provided.
search_issues_jql Search Issues with JQL ~167
Search for issues using JQL with optional read-after-write consistency reconciliation. Requires a bounded query with at least one search restriction for optimal performance.
| Name | Type | Req | Description |
|---|---|---|---|
| jql | string | – | A JQL expression to filter issues. Must include at least one search restriction (e.g., assignee, project, status) to be considered bounded. The orderBy clause supports a maximum of 7 fields. |
| maxResults | string | – | Maximum number of issues to return per page, up to 5000. Defaults to 50 items per page. Actual results may be fewer when requesting many fields. |
| reconcileIssues | array | – | List of up to 50 issue IDs to reconcile with search results for stronger consistency guarantees. Use the same list across all paginated requests to ensure consistency. |
No output schema declared.
No examples provided.
search_issues_picker Search Issues Picker ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currentIssueKey | string | – | The key of an issue to exclude from the search results, typically the issue currently being viewed. |
| currentJQL | string | – | A JQL query that defines the pool of issues to search within. Note that username and userkey cannot be used for privacy reasons; use accountId instead. |
| currentProjectId | string | – | The ID of a project to limit suggestions to issues belonging only to that project. |
| query | string | – | A string to match against text fields in the issue such as title, description, or comments. |
| showSubTaskParent | boolean | – | When the excluded issue is a subtask, whether to include its parent issue in the suggestions if it matches the query. |
| showSubTasks | boolean | – | Whether to include subtasks in the suggestions list. |
No output schema declared.
No examples provided.
search_statuses Search Statuses ~169
Search for statuses by name or project, returning paginated results. Requires project administration or Jira administration permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of statuses to return per page. Defaults to 200 if not specified. |
| projectId | string | – | The project ID to filter statuses to a specific project, or omit to search global statuses. |
| searchString | string | – | A search term to match against status names. Omit or leave empty to return all statuses in the search scope. Limited to 255 characters. |
| startAt | string | – | The starting position for pagination (zero-indexed). Defaults to 0 if not specified. |
| statusCategory | string | – | Filter results by status category: TODO, IN_PROGRESS, or DONE. Omit to include all categories. |
No output schema declared.
No examples provided.
search_users Search Users ~273
Search for active users by name or property. Returns matching users with privacy controls applied based on user preferences. Requires Browse users and groups permission; anonymous calls return empty results.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | A query string that is matched exactly against a user `accountId`. Required, unless `query` or `property` is specified. |
| maxResults | string | – | The number of users to return per page. Defaults to 50 users per page. |
| property | string | – | A property query string to filter users by custom properties using dot notation for nested values (e.g., `propertykey.nested.field=value`). Required unless `accountId` or `query` is specified. |
| query | string | – | A query string that is matched against user attributes ( `displayName`, and `emailAddress`) to find relevant users. The string can match the prefix of the attribute's value. For example, *query=john*… |
| startAt | string | – | The starting position for paginated results, where 0 is the first user. Use this to retrieve subsequent pages of results. |
No output schema declared.
No examples provided.
search_users_and_groups Search Users and Groups ~297
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.
| Name | Type | Req | Description |
|---|---|---|---|
| caseInsensitive | boolean | – | Whether group name matching should be case-insensitive. Defaults to false (case-sensitive matching). |
| fieldId | string | – | The custom field ID to scope the search. When provided, results are filtered to users and groups with permissions for the specified field. Required to use projectId or issueTypeId filters. |
| issueTypeId | array | – | One or more issue type IDs to filter results. Returned users and groups must have permission to view all specified issue types. Supports special values like -1 (all standard types) and -2 (all subtas… |
| maxResults | string | – | Maximum number of results to return per list (users and groups). Defaults to 50 items. |
| projectId | array | – | One or more project IDs to filter results. Returned users and groups must have permission to view all specified projects. Only applicable when fieldId is provided. Projects must be a subset of those… |
| query | string | yes | The search string to match against user display names, email addresses, and group names. User matches are case-insensitive; group matches are case-sensitive by default unless caseInsensitive is enabl… |
No output schema declared.
No examples provided.
search_users_by_permissions Search Users by Permissions ~192
Search for users who have specific permissions in a project or issue and match optional search criteria. Returns matching users with privacy controls applied based on user preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| issueKey | string | – | The issue key for the issue. |
| maxResults | string | – | Maximum number of users to return per page, up to 50 results. Defaults to 50. Note that the actual number returned may be fewer due to search filtering. |
| permissions | string | yes | Comma-separated list of permission identifiers to filter users. Use permission keys from the Jira permissions API, custom project permissions from Connect apps, or deprecated permission constants lik… |
| projectKey | string | – | The project key for the project (case sensitive). |
| startAt | string | – | Zero-based index for pagination to specify which result page to retrieve. Defaults to 0 for the first page. |
No output schema declared.
No examples provided.
search_users_by_query Search Users by Query ~175
Search for users using structured query syntax to find assignees, reporters, watchers, voters, commenters, or transitioners of specific issues, or match users by custom properties. Returns a paginated list of user keys matching the query criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResult | string | – | The maximum number of user keys to return per page, up to 100 items. Defaults to 100 if not specified. |
| query | string | yes | A structured query string using statements like 'is assignee of PROJ', 'is reporter of (PROJ-1, PROJ-2)', or property matching syntax. Multiple statements can be combined with AND/OR operators to cre… |
| startAt | string | – | The zero-based index where the result page begins. Use this to paginate through results in combination with maxResult. |
No output schema declared.
No examples provided.
search_users_picker Search Users for Picker ~154
Search for users by matching query terms against user attributes like display name and email address. Returns matching users with highlighted query matches in HTML format, with optional filtering to exclude specific users.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeAccountIds | array | – | List of user account IDs to exclude from search results. Accepts comma-separated or ampersand-separated format for multiple IDs. |
| maxResults | string | – | Maximum number of users to return in the results, up to 1000. Defaults to 50 if not specified. The total count of matched users is provided separately. |
| query | string | yes | Search query matched against user attributes such as displayName and emailAddress. Supports prefix matching, so partial names and email prefixes will return relevant results. |
No output schema declared.
No examples provided.
search_users_query Search Users by Query ~145
Search for users using structured queries based on their involvement with issues, projects, or custom properties. Returns a paginated list of matching user details.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of users to return per page. Defaults to 100 if not specified. |
| query | string | yes | A structured query string to filter users. Supports queries like 'is assignee of PROJ', 'is reporter of (PROJ-1, PROJ-2)', or custom property matching with AND/OR operators for complex filters. |
| startAt | string | – | The zero-based index where the result page begins. Use this to paginate through results in combination with maxResults. |
No output schema declared.
No examples provided.
send_issue_notification Send Issue Notification ~203
Send an email notification for an issue and queue it for delivery. The notification can be customized with subject and body content, and optionally restricted to users with specific permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| htmlBody | string | – | The HTML-formatted body content of the email notification. If provided, this takes precedence over plain text body for HTML-capable email clients. |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the issue key (e.g., PROJ-123). |
| restrict | object | – | Restricts notification delivery to users who have the specified permission level for the issue. |
| subject | string | – | The subject line of the email notification. If not provided, defaults to the issue key and summary. |
| textBody | string | – | The plain text body content of the email notification. Used as fallback for email clients that don't support HTML. |
| to | object | – | The list of recipients who should receive the email notification for this issue. |
No output schema declared.
No examples provided.
set_issue_properties_bulk Set Issue Properties in Bulk ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entitiesIds | array | – | List of issue IDs to update with the specified properties. Accepts between 1 and 10,000 issue identifiers. |
| properties | object | – | A list of entity property keys and values. |
No output schema declared.
No examples provided.
set_issue_properties_bulk_per_issue Set Issue Properties in Bulk ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | – | A list of issues with their respective properties to set or update. Each entry should contain an issue ID and its associated property key-value pairs. Maximum of 100 issues per request, with up to 10… |
No output schema declared.
No examples provided.
set_issue_property_bulk Set Issue Property in Bulk ~249
Bulk set a property on multiple issues using a constant value or Jira expression. The operation is transactional and asynchronous—either all eligible issues are updated or none are updated. Use the returned task location to monitor progress.
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | – | A Jira expression to dynamically calculate the property value for each issue. The expression must return a JSON-serializable object (number, boolean, string, list, or map) with a JSON representation… |
| filter | object | – | Filter criteria to identify which issues are eligible for update. Supports filtering by specific issue IDs, current property value, or property existence. Multiple criteria are combined with AND logi… |
| propertyKey | string | yes | The property key identifier. Maximum length is 255 characters. |
| value | – | – | A static JSON value to set on the property. Must be a valid, non-empty JSON object with a maximum length of 32,768 characters. Either this or `expression` should be specified, but not both. |
No output schema declared.
No examples provided.
set_project_avatar Set Project Avatar ~92
Sets the avatar image displayed for a project. The avatar must first be uploaded using the load project avatar operation before it can be set as the displayed avatar.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the avatar image to display. This avatar must have been previously uploaded to the project. |
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the case-sensitive project key. |
No output schema declared.
No examples provided.
transfer_filter_ownership Transfer Filter Ownership ~88
Transfer ownership of a filter to another user. The requesting user must own the filter or have Jira administrator permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | The account ID of the new filter owner. This must be a valid Jira user account ID. |
| id | string | yes | The unique identifier of the filter to transfer. This is a numeric ID that identifies the specific filter in your Jira instance. |
No output schema declared.
No examples provided.
transition_issue Transition Issue ~200
Move an issue to a new status by performing a transition. If the transition includes a screen, you can update issue fields as part of the transition.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | List of issue screen fields to update, specifying the sub-field to update and its value for each field. This field provides a straightforward option when setting a sub-field. When multiple sub-fields… |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the project key followed by issue number (e.g., PROJ-123). |
| transition | object | – | Details of a transition. Required when performing a transition, optional when creating or editing an issue. |
| update | object | – | A Map containing the field field name and a list of operations to perform on the issue screen field. Note that fields included in here cannot be included in `fields`. |
No output schema declared.
No examples provided.
transition_issues_bulk Transition Issues in Bulk ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bulkTransitionInputs | array | yes | Array of issue transition objects, each containing an issue identifier and its corresponding transition ID. Issues must share compatible workflows for their specified transitions. Maximum of 1,000 is… |
| sendBulkNotification | boolean | – | Whether to send bulk notification emails to affected users when issues are transitioned. Enabled by default. |
No output schema declared.
No examples provided.
trash_plan Trash Plan ~54
Move a plan to trash, removing it from active use. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| planId | string | yes | The unique identifier of the plan to move to trash. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
unwatch_issues_bulk Unwatch Issues in Bulk ~81
Remove your watch from multiple issues in a single operation. You can unwatch up to 1,000 issues across different projects and issue types.
| Name | Type | Req | Description |
|---|---|---|---|
| selectedIssueIdsOrKeys | array | yes | List of issue IDs or keys to unwatch. You can include up to 1,000 issues from any projects or issue types in a single request. |
No output schema declared.
No examples provided.
update_comment Update Comment ~180
Updates an existing comment on an issue. Requires appropriate permissions to edit the comment and view the issue.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The updated comment text formatted as Atlassian Document Format (ADF). |
| id | string | yes | The unique identifier of the comment to update. |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the project key-based identifier (e.g., PROJ-123). |
| notifyUsers | boolean | – | Controls whether users are notified about the comment update. Defaults to true. |
| overrideEditableFlag | boolean | – | Allows bypassing screen security restrictions to edit normally uneditable fields. Only available to administrators and Forge apps with admin privileges. Defaults to false. |
| visibility | object | – | Restricts comment visibility to a specific group or role. Child comments inherit visibility from their parent and cannot be modified independently. |
No output schema declared.
No examples provided.
update_component Update Component ~130
Updates an existing component in a project, overwriting any provided fields. Use an empty string for leadAccountId to remove the component lead.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeType | string | – | Determines who is assigned to issues created with this component. Choose from: PROJECT_DEFAULT (project's default assignee), COMPONENT_LEAD (component lead), PROJECT_LEAD (project lead), or UNASSIGNE… |
| description | string | – | A text description of the component's purpose and scope. |
| id | string | yes | The unique identifier of the component to update. |
No output schema declared.
No examples provided.
update_custom_field_options Update Custom Field Options ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contextId | string | yes | The unique identifier of the context where the custom field options apply. Must be a valid 64-bit integer. |
| fieldId | string | yes | The unique identifier of the custom field to update options for. |
| options | array | – | An array of custom field option objects to update. Each object should contain the option details to be modified. If any option is not found, the entire operation fails and no options are updated. |
No output schema declared.
No examples provided.
update_custom_field_value Update Custom Field Value ~114
Updates the value of a custom field across one or more issues. Only the app that owns the custom field can perform this operation.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldIdOrKey | string | yes | The ID or key of the custom field to update (e.g., customfield_10010). |
| generateChangelog | boolean | – | Whether to generate a changelog entry for this update. Defaults to true if not specified. |
| updates | array | – | An array of custom field update details specifying which issues to update and their new values. |
No output schema declared.
No examples provided.
update_custom_field_values Update Custom Field Values ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| generateChangelog | boolean | – | Whether to generate a changelog entry for this update. Defaults to true if not specified. |
| updates | array | – | Array of custom field value updates to apply. Each entry specifies a custom field and the issue(s) to update with their new values. Order is not significant. |
No output schema declared.
No examples provided.
update_dashboard Update Dashboard ~123
Update an existing dashboard by replacing all its details with the provided information. You must own the dashboard to update it.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A brief text description of the dashboard's purpose or content. |
| editPermissions | array | yes | An array of permission objects that define who can edit the dashboard and their access level. |
| id | string | yes | The unique identifier of the dashboard to update. |
| name | string | yes | The display name of the dashboard. |
| sharePermissions | array | yes | An array of permission objects that define who can view and access the dashboard. |
No output schema declared.
No examples provided.
update_dashboard_gadget Update Dashboard Gadget ~126
Modify a gadget's appearance and position on a dashboard by updating its title, color, and layout properties.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | The visual color of the gadget. Choose from: blue, red, yellow, green, cyan, purple, gray, or white. |
| dashboardId | string | yes | The unique identifier of the dashboard containing the gadget. Must be a positive integer. |
| gadgetId | string | yes | The unique identifier of the gadget to update. Must be a positive integer. |
| title | string | – | The display title for the gadget shown on the dashboard. |
No output schema declared.
No examples provided.
update_dashboards_bulk Bulk Update Dashboards ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The type of bulk operation to perform: change the dashboard owner, modify permissions, add new permissions, or remove existing permissions. |
| changeOwnerDetails | object | – | Required when action is 'changeOwner'. Contains the details needed to transfer ownership of the dashboards to a new owner. |
| entityIds | array | yes | A list of dashboard IDs to be modified by the bulk operation. Maximum of 100 dashboard IDs per request. |
| permissionDetails | object | – | Required when action is 'changePermission', 'addPermission', or 'removePermission'. Specifies the permission settings to apply to the selected dashboards. |
No output schema declared.
No examples provided.
update_filter Update Filter ~228
Update an existing filter's configuration including name, description, JQL query, and sharing settings. You must own the filter to make changes.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A text description explaining the filter's purpose or usage. |
| editPermissions | array | – | An array of groups and projects that are granted permission to edit this filter. Order and format are determined by the API's permission structure. |
| favourite | boolean | – | A boolean flag indicating whether this filter should be marked as a favorite in the user's filter list. |
| id | string | yes | The unique identifier of the filter to update. Must be a valid 64-bit integer. |
| jql | string | – | The JQL (Jira Query Language) query string that defines which issues this filter returns. For example: project = SSP AND issuetype = Bug. |
| name | string | yes | The display name for the filter. Must be unique across all filters you own. |
| sharePermissions | array | – | An array of groups and projects with whom this filter is shared. Order and format are determined by the API's permission structure. |
No output schema declared.
No examples provided.
update_issue Update Issue ~290
Updates an issue's fields and properties. Use the Get edit issue metadata endpoint to determine which fields are editable. Note that issue transitions are not supported through this operation; use the Transition issue endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | List of issue screen fields to update, specifying the sub-field to update and its value for each field. This field provides a straightforward option when setting a sub-field. When multiple sub-fields… |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the issue key (e.g., PROJ-123). |
| notifyUsers | boolean | – | Whether to send notification emails to all watchers about this update. Defaults to true; only users with Administer Jira or Administer project permissions can disable notifications. |
| overrideEditableFlag | boolean | – | Whether to bypass screen security restrictions to allow editing of normally uneditable fields. Only available to Connect and Forge apps with Administer Jira global permission. Defaults to false. |
| returnIssue | boolean | – | Whether to include the updated issue in the response with the same format as the Get issue endpoint. Defaults to false. |
| update | object | – | A Map containing the field field name and a list of operations to perform on the issue screen field. Note that fields included in here cannot be included in `fields`. |
No output schema declared.
No examples provided.
update_plan Update Plan ~162
Updates plan details including name, lead account, scheduling configuration, issue sources, exclusion rules, cross-project releases, custom fields, and permissions using JSON Patch operations. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | JSON Patch document (RFC 6902) containing one or more operations to update plan properties. Each operation specifies an action (add, replace, remove), a JSON pointer path to the target property, and… |
| planId | string | yes | The unique identifier of the plan to update. Must be a positive integer. |
No output schema declared.
No examples provided.
update_plan_team Update Plan-Only Team ~160
Update planning settings for a plan-only team, including name, planning style, issue source, sprint length, capacity, and team members. Uses JSON Patch format to specify changes.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | JSON Patch operations array specifying the updates to apply. Each operation must include 'op' (replace, add, remove), 'path' (target field), and 'value' (for replace/add operations). Note that add op… |
| planId | string | yes | The unique identifier of the plan containing the team. Must be a positive integer. |
| planOnlyTeamId | string | yes | The unique identifier of the plan-only team to update. Must be a positive integer. |
No output schema declared.
No examples provided.
update_project Update Project ~331
Update project details including name, description, avatar, category, and associated schemes. All parameters are optional; only included fields will be updated while omitted ones remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeType | string | – | The default assignee type for newly created issues in this project. Choose between the project lead or unassigned. |
| avatarId | string | – | The numeric ID of the avatar image to display for this project. |
| categoryId | string | – | The numeric ID of the project category. Use the Get all project categories operation to find available category IDs, or set to -1 to remove the category. |
| description | string | – | A brief description of the project's purpose and scope. |
| issueSecurityScheme | string | – | The numeric ID of the issue security scheme that controls issue visibility and access permissions. Use the Get issue security schemes operation to find available scheme IDs. |
| notificationScheme | string | – | The numeric ID of the notification scheme that defines how project members are notified of events. Use the Get notification schemes operation to find available scheme IDs. |
| permissionScheme | string | – | The numeric ID of the permission scheme that defines user roles and permissions. Use the Get all permission schemes operation to find available scheme IDs. |
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (case-sensitive). |
| releasedProjectKeys | array | – | An array of previous project keys to release from the current project. Released keys must belong to the current project and cannot include the current project key. |
| url | string | – | A URL pointing to project documentation or related information. |
No output schema declared.
No examples provided.
update_project_category Update Project Category ~86
Updates an existing project category with new metadata. Requires Jira administrator permissions to perform this action.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | The new description text for the project category. This field is optional and can be used to update the category's descriptive information. |
| id | string | yes | The unique identifier of the project category to update. This is a numeric ID that identifies which category to modify. |
No output schema declared.
No examples provided.
What is the com.mcparmory/atlassian-jira MCP server?
com.mcparmory/atlassian-jira is an MCP server listed in the public MCP registry as com.mcparmory/atlassian-jira. Create, search, and manage issues, projects, and team workflows. This page covers its PyPI package (mcparmory-atlassian-jira).
Is the com.mcparmory/atlassian-jira MCP server safe to use?
com.mcparmory/atlassian-jira scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/atlassian-jira MCP server expose?
com.mcparmory/atlassian-jira exposes 317 tools: update_custom_field_values, update_custom_field_value, download_attachment, get_attachment_thumbnail, get_attachment, and 312 more. Their descriptions and schemas cost roughly 37,126 tokens of context every time the server is loaded.
Is the com.mcparmory/atlassian-jira MCP server still maintained?
com.mcparmory/atlassian-jira is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.