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 →
add_comment Add Comment ~135
Add a comment to a Jira issue. The comment can be formatted using Atlassian Document Format and optionally restricted to specific groups or roles.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The comment text formatted using Atlassian Document Format. This field supports rich text formatting including mentions, links, and other document elements. |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the project key followed by issue number (e.g., PROJ-123). |
| visibility | object | – | Restricts comment visibility to a specific group or role. When omitted, the comment is visible to all users with permission to view the issue. |
No output schema declared.
No examples provided.
add_field_option Add Field Option ~125
Add a new option to a Connect app's select list issue field. Each field supports up to 10,000 options, and requires Jira administrator permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldKey | string | yes | The unique identifier for the Connect app's custom field, formatted as app-key__field-key (e.g., example-add-on__example-issue-field). Find this value in the app's plugin descriptor or by calling Get… |
| value | string | yes | The display name for the new option as it will appear in Jira. This is the user-facing label for the select list option. |
No output schema declared.
No examples provided.
add_filter_to_favorites Add Filter to Favorites ~67
Mark a filter as a favorite for the current user. You can only favorite filters you own, filters shared with your groups or projects, or publicly shared filters.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the filter to add as a favorite. Must be a positive integer. |
No output schema declared.
No examples provided.
add_issue_watcher Add Issue Watcher ~111
Add a user as a watcher to an issue. The user will receive notifications about changes to the issue. If no user is specified, the calling user is added as the watcher.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The account ID of the user to add as a watcher. If omitted, the authenticated user making the request is added instead. |
| 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.
add_project_role_actors Add Project Role Actors ~124
Adds actors (users or groups) to a project role. Use this to grant role-based permissions to additional actors in a project.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The numeric ID of the project role to add actors to. Retrieve available project role IDs using the get_project_roles operation. |
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (case-sensitive string). |
| user | array | – | An array of user account IDs to add to the project role. Each entry should be a valid user account ID string. |
No output schema declared.
No examples provided.
add_team_to_plan Add Team to Plan ~168
Adds an existing Atlassian team to a plan and configures their planning settings including capacity, planning methodology, and sprint configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| capacity | number | – | The team's capacity allocation for the plan, expressed as a numeric value. |
| id | string | yes | The unique identifier of the Atlassian team to add to the plan. |
| issueSourceId | string | – | The identifier of the issue source that will supply work items for this team's planning. |
| planId | string | yes | The unique identifier of the plan to which the team will be added. |
| planningStyle | string | yes | The planning methodology for the team: either Scrum for sprint-based planning or Kanban for continuous flow. |
| sprintLength | string | – | The duration of sprints in days for Scrum-based teams. |
No output schema declared.
No examples provided.
add_user_to_group Add User to Group ~103
Adds a user to a group in Jira. Requires site administration permissions to perform this operation.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | The account ID of the user, which uniquely identifies the user across all Atlassian products. For example, *5b10ac8d82e05b22cc7d4ef5*. |
| groupId | string | – | The ID of the group. This parameter cannot be used with the `groupName` parameter. |
No output schema declared.
No examples provided.
archive_issues Archive Issues ~103
Archive up to 1000 issues by their ID or key in a single request. Returns details of successfully archived issues and any errors encountered. Requires Jira admin permissions and a Premium or Enterprise license.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdsOrKeys | array | – | Array of issue IDs or keys to archive (up to 1000 per request). Subtasks cannot be archived directly; archive them through their parent issues. Only issues from software, service management, and busi… |
No output schema declared.
No examples provided.
archive_issues_by_jql Archive Issues by JQL ~91
Asynchronously archive up to 100,000 issues matching a JQL query. Returns a task URL to monitor the archival progress. Requires Jira admin permissions and a Premium or Enterprise license.
| Name | Type | Req | Description |
|---|---|---|---|
| jql | string | – | JQL query string to select issues for archival. Only issues from software, service management, and business projects can be archived; subtasks must be archived through their parent issues. |
No output schema declared.
No examples provided.
archive_plan Archive Plan ~53
Archives a plan, removing it from active use while preserving its data. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| planId | string | yes | The unique identifier of the plan to archive, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
archive_project Archive Project ~69
Archive a project to prevent further modifications while preserving its data. Archived projects cannot be deleted directly; restore the project first if deletion is needed.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The unique identifier for the project, either the project ID (numeric) or project key (case-sensitive alphanumeric code). |
No output schema declared.
No examples provided.
assign_issue Assign Issue ~143
Assigns an issue to a user or removes the assignment. Use this operation when you have the Assign Issues permission but lack Edit Issues permission. You can assign to a specific user, the project's default assignee, or leave the issue unassigned.
| 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 in requests. |
| 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.
attach_files Attach Files ~104
Attach one or more files to a Jira issue. Files are uploaded as multipart form data and require the X-Atlassian-Token: no-check header.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | yes | Array of files to attach. Each file is submitted as a multipart form field named 'file'. Multiple files can be attached in a single request. |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the issue key (e.g., TEST-123). |
No output schema declared.
No examples provided.
bulk_edit_issues Bulk Edit Issues ~210
Simultaneously edit multiple issues across projects by specifying field values and target issues. Supports up to 1000 issues and 200 fields per request, with optional bulk notification to affected users.
| Name | Type | Req | Description |
|---|---|---|---|
| editedFieldsInput | object | yes | An object containing the new values for each field being edited. The structure varies by field type, and field IDs must correspond to those specified in selectedActions. |
| selectedActions | array | yes | List of field IDs to be modified in the bulk edit operation. Each ID must match a field in editedFieldsInput and corresponds to a specific issue attribute being updated. Obtain available field IDs fr… |
| selectedIssueIdsOrKeys | array | yes | List of issue IDs or keys to be edited, which may span multiple projects and issue types. Supports up to 1000 issues including subtasks per request. |
| sendBulkNotification | boolean | – | Whether to send bulk change notification emails to affected users about the updates. Defaults to true if not specified. |
No output schema declared.
No examples provided.
cancel_task Cancel Task ~44
Cancels an active task in Jira. Requires either Jira administrator permissions or creator status of the task.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | The unique identifier of the task to cancel. |
No output schema declared.
No examples provided.
check_permissions Check Permissions ~214
Check which permissions the authenticated or anonymous user has in a specific context (global, project, issue, or comment). Permissions are evaluated based on the user's roles and the context provided, with issue-based permissions determined by the user's relationship to that issue.
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | – | The comment ID to check permissions within. Only the BROWSE_PROJECTS permission is supported for comment context. When provided, the user must have both permission to browse the comment and the proje… |
| issueId | string | – | The issue ID to check permissions within. When provided, permissions are evaluated in the context of this specific issue, with issue-based permissions determined by the user's relationship to the iss… |
| permissions | string | – | A comma-separated list of permission keys to check (required when querying specific permissions). Use the Get all permissions operation to discover available permission keys. |
| projectId | string | – | The project ID to check permissions within. When provided, project-level permissions are evaluated for this specific project. |
No output schema declared.
No examples provided.
check_permissions_bulk Check Permissions in Bulk ~128
Verify which global and project permissions a user has, optionally checking access to specific projects and issues. Returns granted permissions and accessible resources for the specified user or the authenticated user if no account ID is provided.
| Name | Type | Req | Description |
|---|---|---|---|
| globalPermissions | array | – | List of global permission keys to check. Only permissions included in this list will be evaluated for the user. |
| projectPermissions | array | – | Project and issue-specific permissions to check. For each permission, specify the projects and issues to validate access against. Up to 1000 projects and 1000 issues can be checked per request; inval… |
No output schema declared.
No examples provided.
check_watched_issues_bulk Check Watched Issues in Bulk ~75
Check the watched status of multiple issues for the current user. Returns whether each issue is being watched, with invalid issue IDs returning a watched status of false.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIds | array | yes | A list of issue IDs to check the watched status for. The order of IDs in the list is preserved in the response. |
No output schema declared.
No examples provided.
count_issues Count Issues ~78
Get an estimated count of issues matching a JQL query. Returns a fast approximate count for issues the user has permission to view; note that recent updates may not be immediately reflected.
| Name | Type | Req | Description |
|---|---|---|---|
| jql | string | – | A JQL query expression to filter issues. The query must include at least one search restriction (bounded query) for performance reasons. |
No output schema declared.
No examples provided.
count_version_related_issues Count Version Related Issues ~74
Retrieves counts of issues related to a specific version, including issues where the version is set as a fix version, affected version, or in a custom version field. 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 issue counts. |
No output schema declared.
No examples provided.
create_component Create Component ~184
Create a new component in a project to serve as a container for organizing and grouping related issues. Requires project administration permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeType | string | – | Determines the default assignee for issues created with this component. Choose PROJECT_DEFAULT to use the project's default assignee, COMPONENT_LEAD to assign to the component lead, PROJECT_LEAD to a… |
| description | string | – | A brief text description of the component's purpose and scope. Optional and can be added or updated at any time. |
| name | string | – | The unique name for the component in the project. Required when creating a component. Optional when updating a component. The maximum length is 255 characters. |
| projectId | string | – | The ID of the project the component is assigned to. |
No output schema declared.
No examples provided.
create_custom_field_options Create Custom Field Options ~136
Create options for a custom select field within a specific context. Supports cascading options for cascading select fields, with a maximum of 1000 options per request and 10000 total options per field.
| Name | Type | Req | Description |
|---|---|---|---|
| contextId | string | yes | The unique identifier of the field context where options will be created. Must be a positive integer. |
| fieldId | string | yes | The unique identifier of the custom field to which options will be added. |
| options | array | – | An array of option objects to create. Each option defines a select list choice, and for cascading select fields, can include nested cascading options. Order is preserved as provided. |
No output schema declared.
No examples provided.
create_dashboard Create Dashboard ~126
Creates a new dashboard with specified name, description, and access permissions. The dashboard will be configured with edit and share permissions to control who can modify and access it.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional text describing the dashboard's purpose and content. |
| editPermissions | array | yes | Required array specifying which users or groups can edit the dashboard and their permission levels. |
| name | string | yes | Required name for the dashboard. Used as the primary identifier and display label. |
| sharePermissions | array | yes | Required array specifying which users or groups can view and access the dashboard and their permission levels. |
No output schema declared.
No examples provided.
create_filter Create Filter ~199
Creates a new filter with a JQL query and optional sharing settings. The filter is shared according to default scope settings and is not automatically marked as a favorite.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A brief explanation of the filter's purpose and usage. |
| editPermissions | array | – | Groups and projects that are granted permission to edit this filter. Specify as an array of group and project objects. |
| favourite | boolean | – | Whether to automatically mark this filter as a favorite for the current user. |
| jql | string | – | The JQL (Jira Query Language) query that defines which issues the filter returns. For example: project = SSP AND issuetype = Bug. |
| name | string | yes | The display name for the filter. Must be unique across all filters in the Jira instance. |
| sharePermissions | array | – | Groups and projects with whom this filter is shared. Specify as an array of group and project objects to control visibility and access. |
No output schema declared.
No examples provided.
create_group Create Group ~48
Creates a new group in Jira. Requires site administration permissions to perform this action.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name for the new group. This identifier is used to reference the group in Jira. |
No output schema declared.
No examples provided.
create_issue Create Issue ~185
Create a new issue or subtask in a Jira project. Define the issue content using fields and optional workflow transitions, with field availability determined by the project's create issue metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | List of issue screen fields to update, specifying the sub-field to update and its value for each field. This field provides a straightforward option when setting a sub-field. When multiple sub-fields… |
| update | object | – | A Map containing the field field name and a list of operations to perform on the issue screen field. Note that fields included in here cannot be included in `fields`. |
| updateHistory | boolean | – | Whether to add the project to your recently viewed projects list and track the issue type and request type in your project history for future create screen defaults. Defaults to false. |
No output schema declared.
No examples provided.
create_issue_link Create Issue Link ~345
Creates a link between two issues to indicate a relationship. Optionally adds a comment to the outward issue. Requires Issue Linking to be enabled on the site.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The comment text to add to the outward issue, formatted as Atlassian Document Format. Optional on creation. |
| id | string | – | The ID of the issue link type and is used as follows: * In the [ issueLink](#api-rest-api-3-issueLink-post) resource it is the type of issue link. Required on create when `name` isn't provided. Ot… |
| inwardIssueKey | string | – | The key of the inward (destination) issue. Required unless the issue ID is provided instead. |
| name | string | – | The name of the issue link type and is used as follows: * In the [ issueLink](#api-rest-api-3-issueLink-post) resource it is the type of issue link. Required on create when `id` isn't provided. Ot… |
| outwardIssueKey | string | – | The key of the outward (source) issue. Required unless the issue ID is provided instead. |
| visibility | object | – | The group or role to which the comment visibility is restricted. Optional; if omitted, the comment is visible to all users with permission to view the issue. |
No output schema declared.
No examples provided.
create_issues_bulk Create Issues in Bulk ~98
Create up to 50 issues and subtasks in bulk with optional workflow transitions and property assignments. Use the Get create issue metadata endpoint to determine available fields for your project.
| Name | Type | Req | Description |
|---|---|---|---|
| issueUpdates | array | – | Array of issue or subtask definitions to create. Each item specifies fields and updates for one issue. For subtasks, include the parent issue ID or key and set issueType to a subtask type. Order is p… |
No output schema declared.
No examples provided.
create_plan Create Plan ~217
Creates a new plan in Jira with specified issue sources, scheduling configuration, and optional cross-project releases and custom fields. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| crossProjectReleases | array | – | List of cross-project releases to include in the plan. Allows the plan to span multiple projects. |
| customFields | array | – | Custom fields to associate with the plan. Specify as an array of field configurations. |
| exclusionRules | object | – | Rules that define which issues should be excluded from the plan based on specified criteria. |
| issueSources | array | yes | The issue sources that populate the plan. This determines which issues are included and must be specified as an array of source identifiers or configurations. |
| name | string | yes | The name of the plan. Must be between 1 and 255 characters. |
| permissions | array | – | Access control settings that define which users or groups can view or modify the plan. |
| scheduling | object | yes | Scheduling configuration for the plan, including timeline and release dates. Specifies how issues are scheduled within the plan. |
No output schema declared.
No examples provided.
create_plan_only_team Create Plan-Only Team ~222
Creates a plan-only team within a Jira plan and configures their planning settings, including capacity, members, and sprint configuration. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| capacity | number | – | The team's capacity allocation for planning purposes, expressed as a decimal number. |
| issueSourceId | string | – | The unique identifier of the issue source that will supply work items to this plan-only team. |
| memberAccountIds | array | – | A list of Jira account IDs for the team members to be added to this plan-only team. |
| name | string | yes | The name of the plan-only team. Must be between 1 and 255 characters. |
| planId | string | yes | The unique identifier of the plan to which the team will be added. |
| planningStyle | string | yes | The planning methodology for the team. Must be either 'Scrum' for sprint-based planning or 'Kanban' for continuous flow. |
| sprintLength | string | – | The duration of sprints for this team, specified in days. Only applicable when using Scrum planning style. |
No output schema declared.
No examples provided.
create_project Create Project ~617
Creates a new Jira project based on a project type template (business, software, service_desk, or customer_service). Requires Administer Jira global permission and a unique project key.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeType | string | – | Determines who is automatically assigned to newly created issues in this project. Choose PROJECT_LEAD to assign to the project lead, or UNASSIGNED to leave issues unassigned by default. |
| avatarId | string | – | The numeric ID of the avatar image to display for this project. Retrieve available avatar IDs from the project avatars endpoint. |
| categoryId | string | – | The numeric ID of the project category for organizational grouping. Retrieve available category IDs using the Get all project categories operation. |
| description | string | – | A brief text description of the project's purpose and scope. |
| fieldScheme | string | – | The numeric ID of the field scheme that defines which custom and standard fields are available in this project. Cannot be combined with projectTemplateKey. Retrieve available field scheme IDs using t… |
| issueSecurityScheme | string | – | The numeric ID of the issue security scheme that controls visibility and access permissions for issues. Retrieve available scheme IDs using the Get issue security schemes operation. |
| issueTypeScheme | string | – | The numeric ID of the issue type scheme that defines which issue types are available in this project. Cannot be combined with projectTemplateKey. Retrieve available scheme IDs using the Get all issue… |
| issueTypeScreenScheme | string | – | The numeric ID of the issue type screen scheme that maps issue types to their corresponding screens. Cannot be combined with projectTemplateKey. Retrieve available scheme IDs using the Get all issue… |
| key | string | yes | A unique project identifier consisting of 1-10 uppercase alphanumeric characters, starting with a letter. This key is used in issue keys (e.g., PROJ-123) and cannot be changed after creation. |
| name | string | yes | The display name of the project, which appears in the Jira interface and project listings. |
| notificationScheme | string | – | The numeric ID of the notification scheme that defines how team members are notified of project events. Retrieve available scheme IDs using the Get notification schemes operation. |
| permissionScheme | string | – | The numeric ID of the permission scheme that controls user access and actions within the project. Retrieve available scheme IDs using the Get all permission schemes operation. |
| projectTemplateKey | string | – | A predefined project configuration template that sets up workflows, issue types, and screens. The template type must match the projectTypeKey (e.g., software templates for software projects). Cannot… |
| url | string | – | A URL pointing to project documentation, guidelines, or related resources. |
| workflowScheme | string | – | The numeric ID of the workflow scheme that defines the issue lifecycle and transitions for this project. Cannot be combined with projectTemplateKey. Retrieve available scheme IDs using the Get all wo… |
No output schema declared.
No examples provided.
create_project_category Create Project Category ~63
Creates a new project category in Jira. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional text describing the purpose and scope of this project category. |
| name | string | – | The name of the project category. Required on create, optional on update. |
No output schema declared.
No examples provided.
create_project_from_template Create Project From Template ~118
Creates a new Jira project based on a custom template with specified capabilities. This asynchronous operation configures project details, workflows, permissions, fields, and other components. Requires Jira Enterprise edition and Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| details | – | – | Project details: name, description, access level, assignee type, avatar, category, language, URL, and other project-level settings. |
| template | – | – | Project template configuration: boards, field schemes, issue types, notification schemes, permission schemes, roles, security levels, workflows, and their mappings. |
No output schema declared.
No examples provided.
create_related_work Create Related Work ~130
Creates a generic related work item linked to a specific version. The related work ID is automatically generated and does not need to be provided.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The category classification for the related work item. |
| id | string | yes | The unique identifier of the version to which the related work will be linked. |
| title | string | – | The display title or name of the related work item. |
| url | string | – | The web address pointing to the related work item. Required for all related work types except native release notes, which will have a null URL. Must be a valid URI format. |
No output schema declared.
No examples provided.
create_user Create User ~131
Creates a new user in Jira with specified product access. Returns 201 if the user is created or already exists with access, or 400 if the user exists without access. Requires Administer Jira global permission and organization admin status.
| Name | Type | Req | Description |
|---|---|---|---|
| emailAddress | string | yes | The email address for the new user. This serves as the unique identifier for the user account. |
| products | array | yes | An array of products the user should have access to. Valid options include jira-core, jira-servicedesk, jira-product-discovery, and jira-software. Pass an empty array to create a user without any pro… |
No output schema declared.
No examples provided.
create_version Create Version ~273
Creates a new project version in Jira. Requires the project ID and appropriate permissions to administer the project.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Whether the version should be marked as archived. Defaults to false if not specified. |
| description | string | – | A text description of the version, up to 16,384 bytes in length. |
| driver | string | – | The Atlassian account ID of the person responsible for driving this version's development. |
| moveUnfixedIssuesTo | string | – | The URL of the version to which unfixed issues should be moved when this version is released. Only applicable when updating a version. |
| name | string | – | The unique name of the version. Required when creating a version. Optional when updating a version. The maximum length is 255 characters. |
| projectId | string | – | The ID of the project to which this version belongs. Required when creating a version. |
| releaseDate | string | – | The date when the version is released, specified in ISO 8601 format (yyyy-mm-dd). |
| released | boolean | – | Whether the version has been released. Once released, subsequent release requests are ignored. Only applicable when updating a version. |
| startDate | string | – | The date when work on the version begins, specified in ISO 8601 format (yyyy-mm-dd). |
No output schema declared.
No examples provided.
delete_and_replace_version Delete and Replace Version ~142
Deletes a project version and optionally reassigns issues to alternative versions. Issues referencing the deleted version in fixVersion, affectedVersion, or version picker custom fields will be updated with the provided replacements or cleared if no alternatives are specified.
| Name | Type | Req | Description |
|---|---|---|---|
| customFieldReplacementList | array | – | An optional array of mappings to reassign custom fields containing the deleted version. Each mapping specifies a custom field ID and the replacement version ID to use. All replacement versions must b… |
| id | string | yes | The unique identifier of the version to delete. Must be a valid version ID from the target project. |
No output schema declared.
No examples provided.
delete_attachment Delete Attachment ~48
Removes an attachment from an issue. Requires either permission to delete your own attachments or permission to delete any attachment in the project.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the attachment to delete. |
No output schema declared.
No examples provided.
delete_avatar Delete Avatar ~93
Permanently removes a custom avatar from a project, issue type, or priority. Requires Jira administrator permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique numeric identifier of the avatar to delete. |
| owningObjectId | string | yes | The unique identifier of the project, issue type, or priority that owns the avatar. |
| type | string | yes | The category of object the avatar belongs to: project, issue type, or priority. |
No output schema declared.
No examples provided.
delete_comment Delete Comment ~75
Removes a comment from an issue. Requires appropriate permissions based on comment ownership and visibility restrictions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the comment to delete. |
| 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.
delete_comment_property Delete Comment Property ~72
Removes a custom property from a comment. Requires either Edit All Comments permission or Edit Own Comments permission if you created the comment.
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | The unique identifier of the comment containing the property to delete. |
| propertyKey | string | yes | The key identifying the custom property to remove from the comment. |
No output schema declared.
No examples provided.
delete_component Delete Component ~84
Deletes a component from a project. Optionally specify a replacement component to reassign any issues currently associated with the deleted component.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the component to delete. |
| moveIssuesTo | string | – | The unique identifier of a component to replace the deleted one. If not provided, issues associated with the deleted component will not be reassigned. |
No output schema declared.
No examples provided.
delete_custom_field Delete Custom Field ~62
Permanently deletes a custom field from Jira, whether it's in the trash or active. This is an asynchronous operation; use the location link in the response to track the deletion task status.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the custom field to delete. |
No output schema declared.
No examples provided.
delete_custom_field_option Delete Custom Field Option ~104
Deletes a custom field option from a specific context. Options with cascading options cannot be deleted until their cascading options are removed first.
| Name | Type | Req | Description |
|---|---|---|---|
| contextId | string | yes | The unique identifier of the context from which the option should be deleted. This is a numeric ID. |
| fieldId | string | yes | The unique identifier of the custom field containing the option to delete. |
| optionId | string | yes | The unique identifier of the option to delete. This is a numeric ID. |
No output schema declared.
No examples provided.
delete_dashboard Delete Dashboard ~41
Permanently deletes a dashboard. You must be the owner of the dashboard to delete it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the dashboard to delete. |
No output schema declared.
No examples provided.
delete_filter Delete Filter ~54
Permanently delete a filter from Jira. Only the filter creator or users with Administer Jira permission can delete filters.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the filter to delete, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
delete_group Delete Group ~124
Permanently deletes a group from the system. Optionally transfer group restrictions to another group to preserve access to comments and worklogs; otherwise, these items become inaccessible after deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| groupId | string | – | The ID of the group. This parameter cannot be used with the `groupname` parameter. |
| swapGroupId | string | – | The ID of an existing group to receive the deleted group's restrictions. Only comments and worklogs are transferred. Omit this parameter if you want restrictions to be removed without transfer. Canno… |
No output schema declared.
No examples provided.
delete_issue Delete Issue ~120
Permanently deletes an issue from the project. Subtasks must be handled explicitly—either delete them along with the issue or remove them first.
| Name | Type | Req | Description |
|---|---|---|---|
| deleteSubtasks | string | – | Whether to automatically delete all subtasks when the issue is deleted. Set to 'true' to delete subtasks along with the issue, or 'false' to prevent deletion if subtasks exist. Defaults to 'false'. |
| issueIdOrKey | string | yes | The unique identifier or key of the issue to delete (e.g., PROJ-123 or 10001). |
No output schema declared.
No examples provided.
delete_issue_link_type Delete Issue Link Type ~55
Permanently deletes an issue link type from your Jira instance. Requires issue linking to be enabled and Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| issueLinkTypeId | string | yes | The unique identifier of the issue link type to delete. |
No output schema declared.
No examples provided.
delete_issue_property_bulk Delete Issue Properties in Bulk ~119
Bulk delete a property from multiple issues based on filter criteria. This operation is transactional and asynchronous—either the property is deleted from all matching issues or no changes are made if errors occur.
| Name | Type | Req | Description |
|---|---|---|---|
| currentValue | – | – | Optional filter to only delete the property from issues where it currently has this specific value. |
| entityIds | array | – | Optional list of specific issue IDs to target for deletion. If provided with currentValue, only issues matching both criteria are affected. |
| propertyKey | string | yes | The unique identifier of the property to delete from issues. |
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.