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 →
list_related_work List Related Work ~51
Retrieves all related work items associated with a specific version. Requires Browse projects permission for the project containing the version.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the version for which to retrieve related work items. |
No output schema declared.
No examples provided.
list_remote_issue_links List Remote Issue Links ~124
Retrieve remote issue links for an issue, optionally filtered by a specific global ID. Returns all linked remote issues or a single link matching the provided global ID.
| Name | Type | Req | Description |
|---|---|---|---|
| globalId | string | – | Optional global ID to retrieve a specific remote issue link. If omitted, all remote issue links for the issue are returned. URL-reserved characters in the global ID must be percent-encoded. |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID (e.g., 10000) or the issue key (e.g., PROJ-123). |
No output schema declared.
No examples provided.
list_resolutions List Resolutions ~137
Retrieve a paginated list of issue resolutions, optionally filtered by resolution IDs or default status. Useful for populating resolution dropdowns or validating resolution values in Jira.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The number of resolutions to return per page. Defaults to 50 items if not specified. |
| onlyDefault | boolean | – | When enabled, returns only default resolutions. If specific resolution IDs are provided and none are marked as default, an empty page is returned. Only applies to company-managed projects. |
| startAt | string | – | The starting position for pagination, where 0 represents the first item. Use this to navigate through pages of results. |
No output schema declared.
No examples provided.
list_screen_fields List Screen Fields ~55
Retrieve all fields available to be added to a screen tab. This helps identify which fields can be configured for a specific screen layout.
| Name | Type | Req | Description |
|---|---|---|---|
| screenId | string | yes | The unique identifier of the screen. Must be a positive integer. |
No output schema declared.
No examples provided.
list_security_levels_project List Security Levels for Project ~66
Retrieve all issue security levels available in a project that the authenticated user can access. Security levels are only returned for users with the Set Issue Security permission.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKeyOrId | string | yes | The project identifier, either the project key (case-sensitive) or the project ID. |
No output schema declared.
No examples provided.
list_status_categories List Status Categories ~37
Retrieves all available status categories in Jira. Status categories group statuses by their workflow state (e.g., To Do, In Progress, Done).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_statuses List Statuses ~39
Retrieves all statuses associated with active workflows in Jira. This operation is useful for understanding the available status values that can be assigned to issues across your projects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_statuses_bulk List Statuses in Bulk ~61
Retrieve detailed information for one or more statuses by their IDs. Useful for fetching status configurations needed for workflow operations or validation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | array | yes | One or more status IDs to retrieve. Provide between 1 and 50 IDs in a single request. |
No output schema declared.
No examples provided.
list_statuses_by_name List Statuses by Name ~101
Retrieve a list of statuses by their names. Supports bulk lookup of up to 50 status names, optionally scoped to a specific project or global statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| name | array | yes | One or more status names to retrieve. Provide between 1 and 50 names as an ampersand-separated list. |
| projectId | string | – | Optional project ID to scope the status lookup to a specific project. Omit or use null to retrieve global statuses. |
No output schema declared.
No examples provided.
list_system_avatars List System Avatars ~68
Retrieves a list of system avatars filtered by type (issue type, project, user, or priority). This operation is publicly accessible and requires no authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | The category of avatars to retrieve. Must be one of: issuetype, project, user, or priority. |
No output schema declared.
No examples provided.
list_trashed_fields List Trashed Fields ~140
Retrieve a paginated list of custom fields that have been moved to trash. Results can be filtered by field name or description, and sorted by name, trash date, or planned deletion date. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The number of fields to return per page. Defaults to 50 items per page. |
| orderBy | string | – | Sort the results by field name, the date the field was moved to trash, or the planned deletion date. |
| startAt | string | – | The starting position for pagination (zero-indexed). Use this to retrieve subsequent pages of results. Defaults to 0. |
No output schema declared.
No examples provided.
list_user_account_ids List User Account IDs ~203
Retrieve account IDs for specified users by their key or username. This operation supports pagination and is useful for migrating or bulk-processing user data.
| Name | Type | Req | Description |
|---|---|---|---|
| key | array | – | Key of a user. To specify multiple users, pass multiple copies of this parameter. For example, `key=fred&key=barney`. Required if `username` isn't provided. Cannot be provided if `username` is presen… |
| maxResults | string | – | The maximum number of user results to return in a single page. Defaults to 10 items per page. |
| startAt | string | – | The starting position for pagination, where 0 represents the first item. Use this to retrieve subsequent pages of results. |
| username | array | – | Username of a user. To specify multiple users, pass multiple copies of this parameter. For example, `username=fred&username=barney`. Required if `key` isn't provided. Cannot be provided if `key` is p… |
No output schema declared.
No examples provided.
list_user_default_columns List User Default Columns ~40
Retrieves the default issue table columns configured for a user. Returns the calling user's column preferences unless an account ID is specified, which requires Jira administration permissions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_user_groups List User Groups ~53
Retrieve all groups that a user belongs to. Requires Browse users and groups global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | The unique account ID of the user across all Atlassian products (up to 128 characters). |
No output schema declared.
No examples provided.
list_user_property_keys List User Property Keys ~85
Retrieves all property keys associated with a user. These are custom properties stored at the user level, distinct from Jira user profile properties.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | The account ID of the user, which uniquely identifies the user across all Atlassian products. For example, *5b10ac8d82e05b22cc7d4ef5*. |
No output schema declared.
No examples provided.
list_users List Users ~110
Retrieves a paginated list of all users in the Jira instance, including active, inactive, and previously deleted users with Atlassian accounts. Response visibility is filtered based on user privacy preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of users to return per request, capped at 1000. Defaults to 50 if not specified. |
| startAt | string | – | The zero-based index position to start returning results from, enabling pagination through large user lists. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
list_users_by_account_ids List Users by Account IDs ~123
Retrieve a paginated list of Jira users by their account IDs. Requires permission to access Jira.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | array | yes | One or more user account IDs to retrieve. Specify multiple account IDs to fetch multiple users in a single request. Each account ID must not exceed 128 characters. |
| maxResults | string | – | The number of users to return per page. Defaults to 10 if not specified. |
| startAt | string | – | The starting position for pagination, where 0 is the first user. Use this to navigate through pages of results. |
No output schema declared.
No examples provided.
list_users_default List Users ~108
Retrieves a paginated list of all users in the Jira instance, including active, inactive, and previously deleted users with Atlassian accounts. Response data is filtered based on user privacy preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of users to return per request, up to a limit of 1000. Defaults to 50 if not specified. |
| startAt | string | – | The zero-based index position to start returning results from. Use this to paginate through large result sets. |
No output schema declared.
No examples provided.
list_workflow_capabilities List Workflow Capabilities ~139
Retrieve available workflow capabilities including rules, scope, and project types. Requires either a workflow ID or a project and issue type ID pair to identify the target workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| issueTypeId | string | – | The unique identifier of the issue type. Use this with projectId as an alternative to workflowId to identify the workflow by issue type context. |
| projectId | string | – | The unique identifier of the project. Use this with issueTypeId as an alternative to workflowId to identify the workflow by project context. |
| workflowId | string | – | The unique identifier of the workflow. Use this to retrieve capabilities for a specific workflow by ID. |
No output schema declared.
No examples provided.
list_workflow_history List Workflow History ~73
Retrieves workflow history entries for a specified workflow, showing past changes and events. Note that historical data is only available for the last 60 days and entries before October 30th, 2025 are not accessible.
| Name | Type | Req | Description |
|---|---|---|---|
| workflowId | string | – | The unique identifier of the workflow whose history you want to retrieve. |
No output schema declared.
No examples provided.
list_workflow_issue_type_usages List Workflow Issue Type Usages ~113
Retrieve the issue types within a project that are currently using a specified workflow. Returns paginated results of issue type assignments.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of issue types to return per page. Must be between 1 and 200, defaults to 50 if not specified. |
| projectId | string | yes | The unique identifier of the project in which to find issue type usages. |
| workflowId | string | yes | The unique identifier of the workflow to query for issue type usage. |
No output schema declared.
No examples provided.
list_workflow_projects List Workflow Projects ~86
Retrieve a paginated list of projects that use a specified workflow. Useful for understanding workflow adoption and impact across your Jira instance.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of projects to return per page, between 1 and 200. Defaults to 50 if not specified. |
| workflowId | string | yes | The unique identifier of the workflow to query for project usage. |
No output schema declared.
No examples provided.
list_workflow_scheme_projects List Workflow Scheme Projects ~81
Retrieve a paginated list of projects that are currently using a specified workflow scheme.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of projects to return per page, between 1 and 200. Defaults to 50 if not specified. |
| workflowSchemeId | string | yes | The unique identifier of the workflow scheme for which to retrieve associated projects. |
No output schema declared.
No examples provided.
list_workflow_schemes_by_projects List Workflow Schemes by Projects ~92
Retrieves the workflow schemes associated with specified projects, showing which projects are linked to each scheme. Team-managed and non-existent projects are silently ignored. The Default Workflow Scheme is returned without an ID.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | array | yes | One or more project IDs to retrieve associated workflow schemes for. Provide between 1 and 100 project IDs; non-existent or team-managed projects are ignored without error. |
No output schema declared.
No examples provided.
list_workflow_usages_by_status List Workflow Usages by Status ~95
Retrieve a paginated list of workflows that use a specific status. This helps identify which workflows are affected by changes to a given status.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of workflow results to return per page. Must be between 1 and 200, with a default of 50 results. |
| statusId | string | yes | The unique identifier of the status for which to retrieve workflow usages. |
No output schema declared.
No examples provided.
list_worklog_property_keys List Worklog Property Keys ~95
Retrieves all property keys associated with a specific worklog entry. Use this to discover what custom properties are available for a worklog before retrieving their values.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, which can be either the numeric issue ID or the issue key (e.g., PROJECT-123). |
| worklogId | string | yes | The unique identifier of the worklog entry within the specified issue. |
No output schema declared.
No examples provided.
list_worklogs_modified_since List Worklogs Modified Since ~112
Retrieve a paginated list of worklog IDs and their update timestamps for all worklogs modified after a specified date and time. Results are ordered from oldest to youngest, with a maximum of 1000 worklogs per page.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | The UNIX timestamp in milliseconds marking the start of the time range. Only worklogs updated after this timestamp are returned. Defaults to 0 (epoch start) if not specified. Note: worklogs updated d… |
No output schema declared.
No examples provided.
merge_versions Merge Versions ~105
Merges two project versions by deleting the source version and reassigning all issues from it to the target version. Requires Administer Jira or Administer Projects permission.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the version to delete. This version will be removed after all its issues are reassigned to the target version. |
| moveIssuesTo | string | yes | The ID of the version to merge into. All issues currently assigned to the source version will be reassigned to this version. |
No output schema declared.
No examples provided.
move_custom_field_to_trash Move Custom Field to Trash ~59
Move a custom field to trash, making it unavailable for use while preserving the option to permanently delete it later. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the custom field to move to trash. |
No output schema declared.
No examples provided.
move_issues_bulk Move Issues in Bulk ~153
Move multiple issues across projects in a single operation. Supports moving up to 1,000 issues (including subtasks) to a single destination project, issue type, and parent, with automatic field mapping and optional bulk notifications.
| Name | Type | Req | Description |
|---|---|---|---|
| sendBulkNotification | boolean | – | Whether to send a bulk notification email to users when issues are moved. Defaults to true if not specified. |
| targetToSourcesMapping | object | – | Mapping of destination configurations to source issues. Each mapping key combines destination project (ID or key), issue type ID, and optional parent (ID or key) in comma-separated format. The mappin… |
No output schema declared.
No examples provided.
move_worklogs Move Worklogs ~235
Moves a list of worklogs from one issue to another. This experimental operation has limitations: maximum 5000 worklogs per request, no support for worklogs with attachments or project role restrictions, and no notifications, webhooks, or issue history are generated. Time tracking must be enabled in Jira.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustEstimate | string | – | Determines how to update time estimates on both issues. Use 'leave' to keep estimates unchanged, or 'auto' to reduce the source issue estimate by the total time spent and increase the destination iss… |
| ids | array | – | A list of worklog IDs to move. Maximum of 5000 worklogs per request. Worklogs with attachments or project role visibility restrictions cannot be moved. |
| issueIdOrKey | string | – | The issue ID or key of the destination issue where worklogs will be moved to. |
| overrideEditableFlag | boolean | – | When true, allows moving worklogs even if the source or destination issues are not editable (e.g., closed issues). Only available to Connect and Forge app users with admin permission. Defaults to fal… |
No output schema declared.
No examples provided.
preview_workflows Preview Workflows ~111
Retrieve a read-only preview of workflows for a specified project. Returns workflow configuration details filtered by issue types, project permissions, and lookup criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| issueTypeIds | array | – | List of issue type IDs to filter workflows. Specify up to 25 issue type IDs; at least one lookup criterion (issueTypeIds, workflowNames, or workflowIds) is required. |
| projectId | string | yes | The project ID for permission validation and workflow association. Required to identify the project context and enforce access controls. |
No output schema declared.
No examples provided.
record_worklog Record Worklog ~517
Record time spent working on an issue. Time tracking must be enabled in Jira for this operation to succeed. The worklog can optionally update the issue's remaining time estimate based on the time recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustEstimate | string | – | How to adjust the issue's remaining time estimate: 'new' sets it to a specific value, 'leave' keeps it unchanged, 'manual' reduces it by a specified amount, or 'auto' reduces it by the time spent in… |
| comment | – | – | An optional comment about the worklog in Atlassian Document Format. |
| issueIdOrKey | string | yes | The issue ID or key to record work against. |
| newEstimate | string | – | The new remaining time estimate for the issue when adjustEstimate is 'new'. Specify as days (e.g., 2d), hours (e.g., 3h), or minutes (e.g., 30m). Required only when adjustEstimate is 'new'. |
| notifyUsers | boolean | – | Whether to notify users watching the issue via email about the worklog entry. Defaults to true. |
| overrideEditableFlag | boolean | – | Whether to force adding the worklog even if the issue is not editable (e.g., closed). Only available to Connect and Forge app users with Administer Jira permission. Defaults to false. |
| reduceBy | string | – | The amount to reduce the issue's remaining estimate by when adjustEstimate is 'manual'. Specify as days (e.g., 2d), hours (e.g., 3h), or minutes (e.g., 30m). Required only when adjustEstimate is 'man… |
| started | string | – | The date and time when the work effort started, in ISO 8601 format. Required when creating a worklog. |
| timeSpent | string | – | The time spent working on the issue as days (\#d), hours (\#h), or minutes (\#m or \#). Required when creating a worklog if `timeSpentSeconds` isn't provided. Optional when updating a worklog. Cannot… |
| timeSpentSeconds | string | – | The time in seconds spent working on the issue. Required when creating a worklog if `timeSpent` isn't provided. Optional when updating a worklog. Cannot be provided if `timeSpent` is provided. |
| visibility | object | – | Optional visibility restrictions for the worklog, such as restricting it to specific users or groups. |
No output schema declared.
No examples provided.
redact_issue_fields Redact Issue Fields ~69
Submit an asynchronous job to redact sensitive data from specified issue fields. Use the returned job ID to poll the redaction status.
| Name | Type | Req | Description |
|---|---|---|---|
| redactions | array | – | Array of field redaction specifications defining which issue fields should have their data redacted. Each item specifies the field identifier and redaction parameters. |
No output schema declared.
No examples provided.
remove_actor_from_project_role Remove Actor From Project Role ~121
Remove an actor (user) from a project role. Requires project administration permissions or global Jira administration rights.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The numeric ID of the project role. 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). |
| user | string | – | The user account ID of the actor to remove from the project role. If omitted, the operation will fail as a user must be specified for removal. |
No output schema declared.
No examples provided.
remove_dashboard_item_property Remove Dashboard Item Property ~83
Removes a custom property from a dashboard item. Requires edit permission on the dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboardId | string | yes | The unique identifier of the dashboard containing the item. |
| itemId | string | yes | The unique identifier of the dashboard item whose property will be deleted. |
| propertyKey | string | yes | The key identifying the specific property to delete from the dashboard item. |
No output schema declared.
No examples provided.
remove_filter_favorite Remove Filter Favorite ~73
Remove a filter from the user's favorites list. This operation only removes filters that are currently visible to the user; filters that were favorited but subsequently made private cannot be removed through this operation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the filter to remove from favorites, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
remove_filter_share_permission Remove Filter Share Permission ~88
Removes a share permission from a filter, restricting access for the specified user or group. Requires ownership of the filter and permission to access Jira.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the filter from which to remove the share permission. Must be a positive integer. |
| permissionId | string | yes | The unique identifier of the specific share permission to delete. Must be a positive integer. |
No output schema declared.
No examples provided.
remove_gadget Remove Gadget ~84
Remove a gadget from a dashboard. When removed, other gadgets in the same column automatically shift up to fill the vacant position.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboardId | string | yes | The unique identifier of the dashboard containing the gadget to remove. Must be a positive integer. |
| gadgetId | string | yes | The unique identifier of the gadget to remove from the dashboard. Must be a positive integer. |
No output schema declared.
No examples provided.
remove_issue_link Remove Issue Link ~54
Removes a link between two issues. Requires browse and link issue permissions for the affected projects, and view access if issue-level security is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| linkId | string | yes | The unique identifier of the issue link to delete. |
No output schema declared.
No examples provided.
remove_issue_property Remove Issue Property ~85
Removes a custom property from an issue. Requires browse and edit permissions for the project, and issue-level security permission if configured.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, either the issue key (e.g., PROJ-123) or the numeric issue ID. |
| propertyKey | string | yes | The unique key identifying the property to delete from the issue. |
No output schema declared.
No examples provided.
remove_issue_watcher Remove Issue Watcher ~121
Remove a user from watching an issue. Requires the 'Allow users to watch issues' option to be enabled in Jira's general configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | The account ID of the user, which uniquely identifies the user across all Atlassian products. For example, *5b10ac8d82e05b22cc7d4ef5*. Required. |
| 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.
remove_plan_only_team Remove Plan-Only Team ~82
Removes a plan-only team from a plan and deletes their associated planning settings. Requires Jira administrator permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| planId | string | yes | The unique identifier of the plan containing the team to be removed. Must be a positive integer. |
| planOnlyTeamId | string | yes | The unique identifier of the plan-only team to delete. Must be a positive integer. |
No output schema declared.
No examples provided.
remove_priority Remove Priority ~48
Removes an issue priority from the Jira instance. This is an asynchronous operation; check the returned location link to monitor task status.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the priority to delete. |
No output schema declared.
No examples provided.
remove_project_avatar Remove Project Avatar ~90
Remove a custom avatar from a project. Only custom avatars can be deleted; system-provided avatars are protected and cannot be removed. Requires Administer projects permission.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The numeric identifier of the avatar to delete. Must be a valid 64-bit integer. |
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the case-sensitive project key. |
No output schema declared.
No examples provided.
remove_project_property Remove Project Property ~86
Removes a custom property from a project. Requires Administer Jira global permission or Administer Projects permission for the target project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (case-sensitive). |
| propertyKey | string | yes | The key identifying the project property to delete. Retrieve available property keys using the list project properties operation. |
No output schema declared.
No examples provided.
remove_team_from_plan Remove Team from Plan ~88
Remove an Atlassian team from a plan and delete their associated planning settings. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| atlassianTeamId | string | yes | The unique identifier of the Atlassian team to remove from the plan. |
| planId | string | yes | The unique identifier of the plan from which the team will be removed. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
remove_user_property Remove User Property ~72
Removes a custom property from a user's profile. Requires either Jira administrator permissions to delete properties from any user, or standard Jira access to delete properties from your own user record.
| Name | Type | Req | Description |
|---|---|---|---|
| propertyKey | string | yes | The unique identifier for the user property to delete. This key must match an existing property on the user's profile. |
No output schema declared.
No examples provided.
remove_vote Remove Vote ~69
Remove a user's vote from an issue, equivalent to clicking Unvote in Jira. Requires voting to be enabled in Jira's general configuration.
| 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.
remove_worklog Remove Worklog ~307
Remove a worklog entry from an issue and optionally adjust the issue's time estimate. Requires time tracking to be enabled in Jira and appropriate permissions to delete worklogs.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustEstimate | string | – | How to adjust the issue's remaining time estimate after deletion. Use 'auto' to reduce by the deleted worklog's time, 'new' to set a specific value, 'manual' to increase by an amount, or 'leave' to k… |
| id | string | yes | The unique identifier of the worklog entry to delete. |
| increaseBy | string | – | The amount to increase the remaining time estimate when adjustEstimate is set to 'manual'. Specify as a duration using days (d), hours (h), or minutes (m). |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the project key followed by issue number (e.g., PROJ-123). |
| newEstimate | string | – | The new remaining time estimate for the issue when adjustEstimate is set to 'new'. Specify as a duration using days (d), hours (h), or minutes (m). |
| notifyUsers | boolean | – | Whether to send email notifications to users watching the issue. Defaults to true. |
| overrideEditableFlag | boolean | – | Whether to allow deletion even if the issue is not editable (e.g., closed or read-only). Only available to Connect and Forge app users with admin permission. Defaults to false. |
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.