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 →
update_project_role Update Project Role ~118
Partially update a project role by modifying either its name or description. Note that only one field can be updated per request; if both are provided, only the name will be updated.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | The new description for the project role. This field is optional for partial updates and will only be applied if the name is not provided in the same request. |
| id | string | yes | The unique identifier of the project role to update. This is a 64-bit integer that can be obtained from the list of all project roles. |
No output schema declared.
No examples provided.
update_project_role_full Update Project Role ~137
Fully update a project role by replacing its name and description. Both name and description are required for this operation.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | The new description for the project role. This field is required when fully updating a project role. |
| id | string | yes | The unique identifier of the project role to update. This is a numeric ID that can be retrieved from the list of all project roles. |
| name | string | – | The name of the project role. Must be unique. Cannot begin or end with whitespace. The maximum length is 255 characters. Required when creating a project role. Optional when partially updating a proj… |
No output schema declared.
No examples provided.
update_related_work Update Related Work ~166
Updates an existing related work item for a version. Only generic link related works can be modified through this API; archived version-related works cannot be edited.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The classification type of the related work (e.g., generic link, release note). |
| id | string | yes | The unique identifier of the version containing the related work to update. |
| relatedWorkId | string | – | The id of the related work. For the native release note related work item, this will be null, and Rest API does not support updating it. |
| title | string | – | The display name or title for the related work. |
| url | string | – | The web address pointing to the related work resource. Required for all related work types except native release notes, which use null. |
No output schema declared.
No examples provided.
update_remote_link Update Remote Link ~236
Updates an existing remote issue link for a Jira issue. Unspecified fields in the request will be set to null. Requires issue linking to be enabled and appropriate project permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| application | object | – | Details of the remote application containing the linked item, such as Trello or Confluence. |
| globalId | string | – | A unique identifier for the remote item in its external system (maximum 255 characters). For example, in Confluence this might be formatted as 'appId=456&pageId=123'. Enables updating or deleting the… |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the issue key (e.g., 'PROJ-123'). |
| linkId | string | yes | The numeric ID of the remote issue link to update. |
| object | object | yes | Details of the item being linked to, including its title, URL, and other relevant metadata from the remote system. |
| relationship | string | – | A description of the relationship between the issue and the linked item. If not provided, defaults to 'links to'. |
No output schema declared.
No examples provided.
update_resolution Update Resolution ~88
Updates an existing issue resolution in Jira. Requires Administer Jira global permission to perform this action.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | The description of the resolution. Limited to 255 characters maximum. |
| id | string | yes | The unique identifier of the issue resolution to update. |
| name | string | yes | The name of the resolution. Must be unique across all resolutions and limited to 60 characters maximum. |
No output schema declared.
No examples provided.
update_team_planning_settings Update Team Planning Settings ~174
Modify planning configuration for an Atlassian team within a plan, including planning style, issue source, sprint length, and capacity settings. Uses JSON Patch format for updates.
| Name | Type | Req | Description |
|---|---|---|---|
| atlassianTeamId | string | yes | The unique identifier of the Atlassian team to update within the plan. |
| body | object | yes | JSON Patch operations array specifying the updates to apply. Each operation must include 'op' (replace/add/remove), 'path' (e.g., /planningStyle, /sprintLength, /capacity, /issueSourceId), and 'value… |
| planId | string | yes | The unique identifier of the plan containing the team. Must be a positive integer. |
No output schema declared.
No examples provided.
update_version Update Version ~263
Updates an existing project version with new metadata such as release dates, status, and driver assignment. Requires Administer Jira global permission or Administer Projects permission for the target project.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Set whether this version is archived. Archived versions are typically hidden from active workflows. |
| description | string | – | A text description of the version. Maximum length is 16,384 bytes. |
| driver | string | – | The Atlassian account ID of the person responsible for this version. |
| id | string | yes | The unique identifier of the version to update. |
| moveUnfixedIssuesTo | string | – | The URI of another version to automatically move all unfixed issues to when this version is released. Only applicable during updates, not creation. |
| projectId | string | – | The ID of the project this version belongs to. Only used during version creation; ignored when updating. |
| releaseDate | string | – | The date when this version is released, specified in ISO 8601 format (yyyy-mm-dd). |
| released | boolean | – | Set whether this version is released. Once released, subsequent release requests are ignored. |
| startDate | string | – | The date when work on this version begins, specified in ISO 8601 format (yyyy-mm-dd). |
No output schema declared.
No examples provided.
update_worklog Update Worklog ~330
Updates an existing worklog entry for an issue. Requires time tracking to be enabled in Jira and appropriate permissions to edit the worklog.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustEstimate | string | – | How to adjust the issue's remaining time estimate: 'new' sets a specific value, 'leave' keeps it unchanged, or 'auto' adjusts it based on the difference in time spent. Defaults to 'auto'. |
| comment | – | – | A comment about the worklog in Atlassian Document Format. Optional for updates. |
| id | string | yes | The unique identifier of the worklog entry to update. |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the project key (e.g., PROJ-123). |
| newEstimate | string | – | The new remaining time estimate for the issue when adjustEstimate is set to 'new'. Specify as days (d), hours (h), or minutes (m). Required only when adjustEstimate is 'new'. |
| notifyUsers | boolean | – | Whether to send email notifications to users watching the issue. Defaults to true. |
| overrideEditableFlag | boolean | – | Whether to allow updating 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. |
| started | string | – | The date and time when the worklog effort started, in ISO 8601 format. Optional when updating an existing worklog. |
| visibility | object | – | Visibility restrictions for the worklog, such as limiting access to specific groups or roles. Optional for updates. |
No output schema declared.
No examples provided.
upload_avatar Upload Avatar ~219
Upload a custom avatar image for a project, issue type, or priority. The image is automatically cropped to a square and resized into multiple formats (16x16, 24x24, 32x32, 48x48 pixels). Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| entityId | string | yes | The unique identifier of the entity (project, issue type, or priority) that will use this avatar. |
| size | string | yes | The width and height (in pixels) of the square crop region. The cropped area is extracted from the uploaded image starting at the specified X and Y coordinates. |
| type | string | yes | The category of entity receiving the avatar. Must be one of: project, issuetype, or priority. |
| x | string | – | The X coordinate (in pixels) of the top-left corner of the crop region. Defaults to 0 if not specified. |
| y | string | – | The Y coordinate (in pixels) of the top-left corner of the crop region. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
upload_issue_type_avatar Upload Issue Type Avatar ~169
Upload and set a custom avatar image for an issue type. The image is automatically cropped to a square and resized into multiple formats (16x16, 24x24, 32x32, 48x48 pixels). Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the issue type to which the avatar will be assigned. |
| size | string | yes | The width and height in pixels of the square crop region. This determines the size of the cropped area before resizing. |
| x | string | – | The horizontal pixel position of the top-left corner of the crop region. Defaults to 0 if not specified. |
| y | string | – | The vertical pixel position of the top-left corner of the crop region. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
upload_project_avatar Upload Project Avatar ~183
Upload and process an image file as a project avatar. The image is automatically cropped to a square and resized into multiple formats (16x16, 24x24, 32x32, 48x48). Requires the Administer projects permission.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the case-sensitive project key. |
| size | string | – | The side length (in pixels) of the square crop region. Defaults to 0, which uses the smaller of the image's height or width. |
| x | string | – | The X coordinate (in pixels) of the top-left corner of the crop region. Defaults to 0 if not specified. |
| y | string | – | The Y coordinate (in pixels) of the top-left corner of the crop region. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
validate_jql_queries Validate JQL Queries ~119
Validates and parses JQL (Jira Query Language) queries to check syntax and structure. Returns parsed query details based on the specified validation mode.
| Name | Type | Req | Description |
|---|---|---|---|
| queries | array | yes | One or more JQL query strings to parse and validate. Each query is processed independently. |
| validation | string | yes | Validation mode that determines how strictly to validate queries and what to return on errors. Use 'strict' to reject malformed queries entirely, 'warn' to return structure even if errors exist, or '… |
No output schema declared.
No examples provided.
validate_project_key Validate Project Key ~44
Validates a project key to ensure it is a properly formatted string and is not already in use by another project. Use this to verify key availability before creating a new project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate_project_key_generate Validate Project Key ~36
Validates a project key and generates a valid random alternative if the provided key is invalid or already in use. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate_project_name Validate Project Name ~70
Validates whether a project name is available. Returns the provided name if unused, attempts to generate an alternative name by appending a sequence number if the name is taken, or returns an error if no valid alternative can be generated.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The desired project name to validate for availability. |
No output schema declared.
No examples provided.
vote_issue Vote on Issue ~73
Register the user's vote on an issue. This action is equivalent to clicking the Vote button in Jira and 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.
watch_issues Watch Issues ~93
Add up to 1,000 issues to your watch list in a single bulk operation. Watched issues will appear in your notifications and dashboards.
| Name | Type | Req | Description |
|---|---|---|---|
| selectedIssueIdsOrKeys | array | yes | List of issue IDs or keys to watch, supporting up to 1,000 items per request. Issues can be from different projects and types. Provide either numeric IDs or string keys (e.g., PROJ-123). |
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.