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 →
delete_issue_type Delete Issue Type ~100
Deletes an issue type from your Jira instance. If the issue type is currently in use, all associated issues are automatically reassigned to a replacement issue type that you specify.
| Name | Type | Req | Description |
|---|---|---|---|
| alternativeIssueTypeId | string | – | The unique identifier of the issue type to use as a replacement for any issues currently using the deleted type. Required if the issue type being deleted is in use. |
| id | string | yes | The unique identifier of the issue type to delete. |
No output schema declared.
No examples provided.
delete_issues_bulk Delete Issues in Bulk ~106
Submit a bulk delete request to remove multiple issues across projects in a single operation. You can delete up to 1,000 issues at once, with optional notification to affected users.
| Name | Type | Req | Description |
|---|---|---|---|
| selectedIssueIdsOrKeys | array | yes | List of issue IDs or keys to delete. Can include issues from different projects and types. Order is not significant. |
| sendBulkNotification | boolean | – | Whether to send a bulk change notification email to users about the deletions. Enabled by default. |
No output schema declared.
No examples provided.
delete_project Delete Project ~87
Permanently delete a Jira project. Archived projects must be restored before deletion. Requires Jira administrator permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| enableUndo | boolean | – | Whether to move the project to the Jira recycle bin for later restoration instead of permanently deleting it. Defaults to true. |
| projectIdOrKey | string | yes | The unique identifier for the project, either the numeric project ID or the project key (case-sensitive). |
No output schema declared.
No examples provided.
delete_project_async Delete Project Asynchronously ~66
Asynchronously delete a project. The operation is transactional—if any part fails, the project remains unchanged. Monitor the returned task location to track deletion progress.
| 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.
delete_project_category Delete Project Category ~49
Permanently deletes a project category from Jira. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the project category to delete, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_project_role Delete Project Role ~117
Deletes a project role from your Jira instance. If the role is currently in use, you must specify a replacement role to reassign its associations in schemes, workflows, worklogs, and comments.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the project role to delete. Retrieve available project role IDs using the list project roles operation. |
| swap | string | – | The unique identifier of a project role to replace the deleted role across all schemes, workflows, worklogs, and comments. Required if the role being deleted is currently in use. |
No output schema declared.
No examples provided.
delete_related_work Delete Related Work ~73
Removes a related work item from a specific version. Requires permissions to resolve and edit issues in the project containing the version.
| Name | Type | Req | Description |
|---|---|---|---|
| relatedWorkId | string | yes | The unique identifier of the related work item to remove. |
| versionId | string | yes | The unique identifier of the version containing the related work to be deleted. |
No output schema declared.
No examples provided.
delete_remote_link_by_id Delete Remote Link by ID ~104
Removes a remote issue link from an issue. Requires issue linking to be enabled and appropriate project permissions including Browse projects, Edit issues, and Link issues.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID (e.g., 10000) or the issue key (e.g., PROJ-123). |
| linkId | string | yes | The numeric ID of the remote issue link to delete (e.g., 10000). |
No output schema declared.
No examples provided.
delete_resolution Delete Resolution ~103
Deletes an issue resolution from Jira. All issues currently using the deleted resolution will be reassigned to the specified replacement resolution. This is an asynchronous operation; check the returned task location to monitor completion status.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the issue resolution to delete. |
| replaceWith | string | yes | The unique identifier of the issue resolution that will replace the deleted one for all affected issues. This parameter is required to ensure no issues are left without a resolution. |
No output schema declared.
No examples provided.
delete_statuses Delete Statuses ~58
Permanently delete one or more statuses by their IDs. Requires either Administer projects or Administer Jira permission.
| Name | Type | Req | Description |
|---|---|---|---|
| id | array | yes | One or more status IDs to delete. Provide between 1 and 50 IDs in a single request. |
No output schema declared.
No examples provided.
delete_user Delete User ~95
Permanently removes a user from Jira's user base. Note that this operation only deletes the user's Jira account and does not affect their Atlassian account.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | The unique account ID that identifies the user across all Atlassian products. This is a string identifier up to 128 characters long (for example, 5b10ac8d82e05b22cc7d4ef5). |
No output schema declared.
No examples provided.
delete_worklogs Delete Worklogs ~213
Permanently delete multiple worklogs from an issue. This experimental operation supports bulk deletion of up to 5000 worklogs at once, with no notifications sent to users. Time tracking must be enabled in Jira for this operation to succeed.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustEstimate | string | – | Controls how the issue's time estimate is updated after deletion. Use 'leave' to keep the estimate unchanged, or 'auto' to automatically reduce it by the total time spent across all deleted worklogs.… |
| ids | array | yes | A list of worklog IDs to delete. All worklogs must belong to the specified issue. Maximum of 5000 IDs per request. |
| issueIdOrKey | string | yes | The issue ID or key identifying which issue to delete worklogs from. |
| overrideEditableFlag | boolean | – | Set to true to force deletion of worklogs even if the issue is not editable (e.g., closed issues). Only available to Connect and Forge app users with admin permission. Defaults to false. |
No output schema declared.
No examples provided.
download_attachment Download Attachment ~96
Download the full content of an attachment file. Supports partial downloads using HTTP Range headers to retrieve specific byte ranges. This operation can be accessed anonymously if you have the required project and issue permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the attachment to download. |
| redirect | boolean | – | Whether to follow HTTP redirects for the attachment download. Set to false if your client doesn't automatically follow redirects to avoid multiple requests. Defaults to true. |
No output schema declared.
No examples provided.
duplicate_dashboard Duplicate Dashboard ~160
Creates a copy of an existing dashboard with customizable name, description, and permissions. The source dashboard must be owned by or shared with the requesting user.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional text describing the purpose or content of the copied dashboard. |
| editPermissions | array | yes | An array of user or group permissions that grants edit access to the dashboard. Specifies who can modify the dashboard after creation. |
| id | string | yes | The unique identifier of the dashboard to copy. |
| name | string | yes | The display name for the copied dashboard. This identifies the dashboard in lists and navigation. |
| sharePermissions | array | yes | An array of user or group permissions that grants view and share access to the dashboard. Specifies who can view and redistribute access to the dashboard. |
No output schema declared.
No examples provided.
duplicate_plan Duplicate Plan ~78
Creates a duplicate copy of an existing plan with a new name. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name for the duplicated plan. This will be the display name of the new plan copy. |
| planId | string | yes | The unique identifier of the plan to duplicate. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
evaluate_jira_expression Evaluate Jira Expression ~161
Evaluates a Jira expression and returns its computed value using the enhanced search API for better performance and scalability. Supports flexible data retrieval with access to issues, projects, sprints, boards, and custom context variables.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Optional context object that defines variables available to the expression, including built-in contexts (user, issue, issues, project, sprint, board, serviceDesk, customerRequest) and custom variable… |
| expression | string | yes | The Jira expression to evaluate as a string. Can reference context variables and perform operations like field extraction, filtering, and mapping (e.g., extracting issue keys, types, and linked issue… |
No output schema declared.
No examples provided.
export_archived_issues Export Archived Issues ~210
Export archived issues to a CSV file for download. An admin can filter archived issues by date range, project, issue type, reporter, or archival user, and will receive an email with a download link upon completion.
| Name | Type | Req | Description |
|---|---|---|---|
| archivedBy | array | – | Filter results to include only issues archived by specific user account IDs. Provide as a list of account identifiers. |
| dateAfter | string | yes | Include only issues archived on or after this date. Specify in YYYY-MM-DD format. |
| dateBefore | string | yes | Include only issues archived on or before this date. Specify in YYYY-MM-DD format. |
| issueTypes | array | – | Filter results to include only issues of specified issue type IDs. Provide as a list of type identifiers. |
| projects | array | – | Filter results to include only issues from specified project keys. Provide as a list of project key identifiers. |
| reporters | array | – | Filter results to include only issues reported by specific user account IDs. Provide as a list of account identifiers. |
No output schema declared.
No examples provided.
fetch_changelogs Fetch Changelogs ~117
Retrieve specific changelogs for an issue by their IDs. Returns detailed change history records for the specified changelog identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| changelogIds | array | yes | A list of changelog IDs to retrieve. Specify the exact IDs of the changelog entries you want to fetch; order is preserved in the response. |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the human-readable key (e.g., PROJ-123). Used to locate the issue whose changelogs you want to retrieve. |
No output schema declared.
No examples provided.
fetch_issue_changelogs Fetch Issue Changelogs ~163
Retrieve change history for multiple issues in a paginated list, optionally filtered by specific fields. Results are sorted chronologically by changelog date and issue ID, starting from the oldest entries.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldIds | array | – | Optional list of field IDs to narrow changelog results to specific fields. You can filter by up to 10 fields. |
| issueIdsOrKeys | array | yes | List of issue identifiers (IDs or keys) to fetch changelogs for. You can request changelogs for up to 1000 issues. At least one issue identifier is required. |
| maxResults | string | – | Maximum number of changelog items to return per page. Defaults to 1000 if not specified. Must be between 1 and 10000. |
No output schema declared.
No examples provided.
fetch_issues Fetch Issues ~103
Retrieve details for multiple issues by their IDs or keys in a single request. Supports up to 100 issues per request with case-insensitive matching and automatic detection of moved issues.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdsOrKeys | array | yes | Array of issue identifiers to fetch, accepting up to 100 items. You can mix issue IDs and keys in the same request (e.g., both numeric IDs and text keys like 'PROJ-123'). Results are returned in asce… |
No output schema declared.
No examples provided.
filter_issues_by_jql Filter Issues by JQL ~111
Evaluate whether specified issues match one or more JQL queries. Returns matching results for each issue-query combination, respecting project permissions and issue-level security.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIds | array | yes | A list of issue IDs to evaluate against the JQL queries. Each ID must correspond to an issue the user has permission to view. |
| jqls | array | yes | A list of JQL (Jira Query Language) queries to match against the provided issues. Each query is evaluated independently for each issue. |
No output schema declared.
No examples provided.
get_accessible_project_type Get Accessible Project Type ~74
Retrieves a project type if it is accessible to the authenticated user. Returns project type details for the specified project type key.
| Name | Type | Req | Description |
|---|---|---|---|
| projectTypeKey | string | yes | The unique identifier for the project type. Must be one of the four supported project types: software, service_desk, business, or product_discovery. |
No output schema declared.
No examples provided.
get_archive_contents_metadata Get Archive Contents Metadata ~61
Retrieve metadata for the contents of an archive attachment, such as files within a ZIP archive. Use this operation when processing attachment data programmatically without user presentation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the attachment to expand and retrieve contents metadata for. |
No output schema declared.
No examples provided.
get_attachment Get Attachment ~55
Retrieve metadata for an attachment, including details like filename, size, and creation date. The attachment content itself is not returned by this operation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the attachment whose metadata you want to retrieve. |
No output schema declared.
No examples provided.
get_attachment_metadata_with_contents Get Attachment Metadata with Contents ~65
Retrieve complete metadata for an attachment and its contents if it's an archive. Returns information about the attachment itself (ID, name) plus details about any files within supported archive formats like ZIP.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the attachment to retrieve metadata for. |
No output schema declared.
No examples provided.
get_attachment_thumbnail Get Attachment Thumbnail ~170
Retrieves a thumbnail image for an attachment. Supports optional scaling and fallback behavior when thumbnails are unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| fallbackToDefault | boolean | – | Whether to return a default placeholder thumbnail when the requested attachment thumbnail cannot be generated or found. |
| height | string | – | The maximum height in pixels to scale the thumbnail to. The thumbnail will be scaled proportionally to fit within this height. |
| id | string | yes | The unique identifier of the attachment for which to retrieve the thumbnail. |
| redirect | boolean | – | Whether to return a redirect URL for the thumbnail instead of the image content directly. Set to false to avoid multiple requests if your client doesn't automatically follow redirects. |
| width | string | – | The maximum width in pixels to scale the thumbnail to. The thumbnail will be scaled proportionally to fit within this width. |
No output schema declared.
No examples provided.
get_avatar_image_by_avatar_id Get Avatar Image by ID ~166
Retrieves an avatar image for a project, issue type, or priority by ID. Returns the image in the requested size and format, or defaults to the original if not specified.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | The image format to return: either 'png' or 'svg'. If omitted, the avatar's original format is returned. |
| id | string | yes | The unique identifier of the avatar to retrieve. |
| size | string | – | The desired image size: 'xsmall', 'small', 'medium', 'large', or 'xlarge'. If omitted, the default size is returned. |
| type | string | yes | The avatar category: either 'issuetype' for issue type avatars, 'project' for project avatars, or 'priority' for priority avatars. |
No output schema declared.
No examples provided.
get_avatar_image_by_entity Get Avatar Image by Entity ~159
Retrieves the avatar image for a project, issue type, or priority in the specified size and format. This operation can be accessed anonymously, though custom avatars may require project browse permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| entityId | string | yes | The unique identifier of the entity (project or issue type) that owns the avatar. |
| format | string | – | The image format to return: either 'png' or 'svg'. Defaults to the original content format if not specified. |
| size | string | – | The desired avatar image size: xsmall, small, medium, large, or xlarge. Defaults to the original size if not specified. |
| type | string | yes | The avatar type to retrieve: either 'issuetype', 'project', or 'priority'. |
No output schema declared.
No examples provided.
get_bulk_operation_progress Get Bulk Operation Progress ~72
Retrieve the current progress and status of a bulk issue operation. Returns real-time progress metrics while running, or final results upon completion. Task progress data is available for up to 14 days after creation.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | The unique identifier of the bulk operation task whose progress you want to check. |
No output schema declared.
No examples provided.
get_comment Get Comment ~82
Retrieve a specific comment from an issue. Requires browse permissions on the project and any applicable issue-level security or comment visibility restrictions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the comment to retrieve. |
| issueIdOrKey | string | yes | The issue identifier, which can be either the numeric issue ID or the issue key (e.g., PROJ-123). |
No output schema declared.
No examples provided.
get_comment_property Get Comment Property ~78
Retrieves the value of a specific property attached to a comment. Requires appropriate project and issue permissions, and respects any visibility restrictions on the comment.
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | The unique identifier of the comment from which to retrieve the property. |
| propertyKey | string | yes | The identifier of the property whose value should be retrieved from the comment. |
No output schema declared.
No examples provided.
get_component Get Component ~45
Retrieve detailed information about a specific component by its ID. Requires Browse projects permission for the project containing the component.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the component to retrieve. |
No output schema declared.
No examples provided.
get_component_issue_counts Get Component Issue Counts ~54
Retrieves the count of issues assigned to a specific component. This provides a summary of issue distribution for component management and reporting purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the component for which to retrieve issue counts. |
No output schema declared.
No examples provided.
get_current_user Get Current User ~31
Retrieves the profile and account details of the currently authenticated user in Jira. This operation requires valid Jira access permissions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_custom_field_option Get Custom Field Option ~71
Retrieve a custom field option by ID, such as an option from a select list. This operation works only with options created in Jira or via the Issue custom field options API, and can be accessed anonymously with appropriate permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the custom field option to retrieve. |
No output schema declared.
No examples provided.
get_dashboard Get Dashboard ~56
Retrieve a dashboard by its ID. The dashboard must be shared with the user, owned by the user, or the user must have Jira administration permissions to access it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the dashboard to retrieve. |
No output schema declared.
No examples provided.
get_dashboard_item_property Get Dashboard Item Property ~108
Retrieve a specific property value stored for a dashboard item. Dashboard items are gadgets that apps use to display user-specific information on dashboards, and properties store the item's content or configuration details.
| 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 (gadget) whose property you want to retrieve. |
| propertyKey | string | yes | The key name of the property to retrieve from the dashboard item. |
No output schema declared.
No examples provided.
get_default_share_scope Get Default Share Scope ~30
Retrieves the default sharing settings that apply to new filters and dashboards created by the authenticated user in Jira.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_field_option Get Field Option ~121
Retrieve a specific option from a Connect app-provided select list issue field. This operation only works with field options added by Connect apps, not those created directly in Jira.
| 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). Find this value in the app's plugin descriptor or by running Get fields to retrieve the key from field deta… |
| optionId | string | yes | The numeric ID of the option to retrieve. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
get_filter Get Filter ~62
Retrieve a filter by its ID. The filter is only returned if you have access to it through ownership, group sharing, project sharing, or public sharing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the filter to retrieve, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
get_filter_share_permission Get Filter Share Permission ~113
Retrieves a specific share permission for a filter. Returns details about how a filter is shared with groups, projects, all logged-in users, or the public. This operation can be accessed anonymously, but only returns permissions for filters you own, are shared with your groups, or are in projects you can access.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the filter. Must be a positive integer. |
| permissionId | string | yes | The unique identifier of the share permission to retrieve. Must be a positive integer. |
No output schema declared.
No examples provided.
get_issue_creation_fields Get Issue Creation Fields ~143
Retrieve the available fields and their metadata for creating issues of a specific type in a project. Use this information to populate requests when creating single or bulk issues.
| Name | Type | Req | Description |
|---|---|---|---|
| issueTypeId | string | yes | The ID of the issue type for which to retrieve creation field metadata. |
| maxResults | string | – | The maximum number of fields to return per page, up to 200. Defaults to 50 if not specified. |
| projectIdOrKey | string | yes | The project identifier, either the project ID or project key. |
| startAt | string | – | The starting position for pagination, where 0 is the first item. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
get_issue_editable_fields Get Issue Editable Fields ~112
Retrieve the fields that are editable for a specific issue based on the user's permissions, screen configuration, and workflow state. Use this to determine which fields can be modified before submitting an edit request.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the issue key (e.g., PROJ-123). |
| overrideEditableFlag | boolean | – | When enabled, returns non-editable fields by bypassing workflow editability checks. Only available to administrators. Defaults to false. |
No output schema declared.
No examples provided.
get_issue_link Get Issue Link ~51
Retrieves details about a specific issue link by its ID. Returns the link information if you have permission to view both linked issues.
| Name | Type | Req | Description |
|---|---|---|---|
| linkId | string | yes | The unique identifier of the issue link to retrieve. |
No output schema declared.
No examples provided.
get_issue_link_type Get Issue Link Type ~61
Retrieves the details of a specific issue link type by its ID. Requires issue linking to be enabled on the site and the user to have Browse projects permission.
| Name | Type | Req | Description |
|---|---|---|---|
| issueLinkTypeId | string | yes | The unique identifier of the issue link type to retrieve. |
No output schema declared.
No examples provided.
get_issue_property Get Issue Property ~89
Retrieves a specific property value associated with an issue by its property key. Returns both the key and value of the requested issue property.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, which can be either the issue key (e.g., PROJ-123) or the numeric issue ID. |
| propertyKey | string | yes | The unique identifier for the property to retrieve from the issue. |
No output schema declared.
No examples provided.
get_issue_type Get Issue Type ~51
Retrieves detailed information about a specific issue type by its ID. Requires either Browse projects permission in an associated project or Jira administrator access.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the issue type to retrieve. |
No output schema declared.
No examples provided.
get_issue_type_hierarchy Get Issue Type Hierarchy ~74
Retrieve the issue type hierarchy for a next-gen project, which defines the structural levels of issue types (Epic, Story/Task/Bug, and Subtask) and their relationships. Requires Browse projects permission.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | The numeric identifier of the project for which to retrieve the issue type hierarchy. |
No output schema declared.
No examples provided.
get_issue_type_property Get Issue Type Property ~92
Retrieves a specific property value stored on an issue type by its key. Returns both the key and value of the requested issue type property.
| Name | Type | Req | Description |
|---|---|---|---|
| issueTypeId | string | yes | The unique identifier of the issue type whose property you want to retrieve. |
| propertyKey | string | yes | The key identifying which property to retrieve. Use the list issue type property keys operation to discover available property keys for an issue type. |
No output schema declared.
No examples provided.
get_jql_autocomplete_suggestions Get JQL Autocomplete Suggestions ~184
Retrieve JQL search autocomplete suggestions for a field, optionally filtered by field value or predicate criteria. Use this to populate autocomplete dropdowns when users are constructing JQL queries.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldName | string | – | The JQL field name to get suggestions for (e.g., 'reporter'). Required to initiate any suggestion query. |
| fieldValue | string | – | Partial field value entered by the user to filter suggestions. When provided with fieldName, returns values containing this text. |
| predicateName | string | – | The CHANGED operator predicate name for which to generate suggestions. Valid values are 'by', 'from', or 'to'. Use with fieldName to get predicate-specific suggestions. |
| predicateValue | string | – | Partial predicate value entered by the user to filter suggestions. When provided with predicateName and fieldName, returns predicate values containing this text. |
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.