com.mcparmory/atlassian-jira
PYPI · MCPARMORY-ATLASSIAN-JIRA · 2 COMPONENTS
Create, search, and manage issues, projects, and team workflows
Available components
Last scanned (10 hours ago)
Scores higher than 81% of PyPI servers
Category Project Management
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 2 of 45 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 177 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 Management63
- Stability observed for 19 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
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.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −6
- Stability: pass → 0.60 functional
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 0
- 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 5 Nov 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 |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 45 packages
| Packages resolved | 45 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_field_options List Field Options ~150
Retrieve a paginated list of all options available for 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 the Get fields operation. |
| maxResults | string | – | The maximum number of options to return per page. Defaults to 50 if not specified. |
| 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.
list_field_screens List Field Screens ~100
Retrieve a paginated list of all screens where a specific field is used. Requires Jira administrator permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldId | string | yes | The unique identifier of the field to retrieve screens for. |
| maxResults | string | – | The maximum number of screens to return per page. Defaults to 100 if not specified. |
| startAt | string | – | The zero-based index where the paginated results should start. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
list_fields List Fields ~38
Retrieve all available issue fields in Jira, including system and custom fields. Returns fields based on global settings, screen configuration, and your project access permissions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_fields_search Search Fields ~200
Retrieve a paginated list of Jira fields, optionally filtered by field IDs, search query, or project IDs. Supports sorting by various field attributes and can be restricted to custom fields only.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The number of fields to return per page. Defaults to 50 if not specified. |
| orderBy | string | – | Sort the results by field attribute: contextsCount (number of related contexts), lastUsed (date of last value change), name (field name), screensCount (number of related screens), or projectsCount (n… |
| projectIds | array | – | Filter results to fields belonging only to the specified project IDs. Fields from projects you lack access to will be excluded. Provide as a comma-separated list of project identifiers. |
| startAt | string | – | The starting position for pagination (zero-indexed). Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
list_filter_columns List Filter Columns ~81
Retrieves the columns configured for a filter, which are used when viewing filter results in List View with Columns set to Filter. Column details are only returned for filters you own, filters shared with your groups, or filters shared with projects you have access to.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the filter. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
list_filter_permissions List Filter Permissions ~67
Retrieve all share permissions for a filter, including access granted to groups, projects, all logged-in users, or the public. Only returns permissions visible to the requesting user based on their access level.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the filter. Must be a positive integer. |
No output schema declared.
No examples provided.
list_group_members List Group Members ~142
Retrieve a paginated list of all users in a group. Users are ordered by username but usernames are not included in results for privacy reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| groupId | string | – | The ID of the group. This parameter cannot be used with the `groupName` parameter. |
| includeInactiveUsers | boolean | – | Whether to include inactive users in the results. Defaults to excluding inactive users. |
| maxResults | string | – | The maximum number of users to return per page. Must be between 1 and 50 users. |
| startAt | string | – | The zero-based index where the result page should start. Use this for pagination to retrieve subsequent pages of results. |
No output schema declared.
No examples provided.
list_groups List Groups ~181
Retrieve a paginated list of groups from your Jira instance. Filter by group names, access level, or product application to find specific groups.
| Name | Type | Req | Description |
|---|---|---|---|
| accessType | string | – | Filter groups by their access level within your Jira instance. Choose from site administrator, administrator, or standard user access levels. |
| applicationKey | string | – | Limit results to groups associated with a specific Jira product. Specify the product key to filter groups by their application context. |
| groupName | array | – | Filter results by one or more group names. Specify multiple names to search for groups matching any of the provided names. |
| maxResults | string | – | The number of groups to return per page. Defaults to 50 if not specified. |
| startAt | string | – | The starting position for pagination, where 0 is the first group. Use this to navigate through large result sets. |
No output schema declared.
No examples provided.
list_issue_changelogs List Issue Change Logs ~134
Retrieve a paginated list of all changes made to an issue, sorted chronologically from oldest to newest. Requires browse permission for the project and any applicable issue-level security permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the human-readable key (e.g., PROJ-123). |
| maxResults | string | – | The number of changelog entries to return per page. Defaults to 100 if not specified. |
| startAt | string | – | The starting position for pagination, where 0 represents the first changelog entry. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
list_issue_comments List Issue Comments ~152
Retrieve all comments for a specific issue, with support for pagination and sorting. Comments are filtered based on user permissions and visibility restrictions.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the issue key (e.g., PROJ-123). |
| maxResults | string | – | The maximum number of comments to return per page. Defaults to 100 if not specified. |
| orderBy | string | – | Sort comments by creation date. Use 'created' for ascending order, '-created' for descending order, or '+created' for ascending order. |
| startAt | string | – | The starting position for pagination (zero-indexed). Use this to retrieve subsequent pages of results. |
No output schema declared.
No examples provided.
list_issue_limit_violations List Issue Limit Violations ~84
Retrieve all issues that are breaching or approaching per-issue limits in Jira. Requires Browse projects permission for the relevant projects or Administer Jira global permission for complete results.
| Name | Type | Req | Description |
|---|---|---|---|
| isReturningKeys | boolean | – | Return issue keys (e.g., PROJ-123) instead of numeric issue IDs in the response. Defaults to false, which returns issue IDs. |
No output schema declared.
No examples provided.
list_issue_link_types List Issue Link Types ~37
Retrieves all available issue link types configured in the Jira instance. Requires issue linking to be enabled and the user to have Browse projects permission.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_issue_property_keys List Issue Property Keys ~72
Retrieves all property keys and their URLs associated with a specific issue. This allows you to discover what custom properties are stored on an issue.
| 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. |
No output schema declared.
No examples provided.
list_issue_transitions List Issue Transitions ~81
Retrieve available transitions for specified issues that can be used in bulk transition operations. Returns transitions organized by workflow, including only those common across all specified issues that don't require additional field updates.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdsOrKeys | string | yes | Comma-separated list of issue IDs or keys to retrieve available transitions for. Supports up to 1,000 issues per request. |
No output schema declared.
No examples provided.
list_issue_transitions_single List Issue Transitions ~159
Retrieve available transitions for an issue based on its current status. Returns all possible transitions the user can perform, or a specific transition if requested. An empty list is returned if the requested transition doesn't exist or cannot be performed given the issue's current status.
| Name | Type | Req | Description |
|---|---|---|---|
| includeUnavailableTransitions | boolean | – | Whether to include transitions that fail their conditions in the response. Defaults to false, returning only transitions that can currently be performed. |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the project key followed by issue number (e.g., PROJ-123). |
| transitionId | string | – | Optional ID of a specific transition to retrieve. When provided, only that transition is returned if it exists and is available. |
No output schema declared.
No examples provided.
list_issue_type_property_keys List Issue Type Property Keys ~59
Retrieves all property keys stored on a specific issue type. Property keys are identifiers for custom data attached to the issue type entity.
| Name | Type | Req | Description |
|---|---|---|---|
| issueTypeId | string | yes | The unique identifier of the issue type whose property keys you want to retrieve. |
No output schema declared.
No examples provided.
list_issue_type_schemes List Issue Type Schemes ~147
Retrieve a paginated list of issue type schemes used in classic Jira projects. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The number of issue type schemes to return per page. Defaults to 50 items per page. |
| orderBy | string | – | Sort results by issue type scheme name or ID, with optional ascending (+) or descending (-) direction. Defaults to sorting by ID. |
| queryString | string | – | Filter results by performing a case-insensitive partial match against issue type scheme names. |
| startAt | string | – | The starting position for pagination, where 0 is the first item. Use this to retrieve subsequent pages of results. |
No output schema declared.
No examples provided.
list_issue_type_schemes_for_projects List Issue Type Schemes for Projects ~126
Retrieve issue type schemes used by specified projects in classic Jira instances. Returns a paginated list showing which projects use each scheme.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The number of results to return per page. Defaults to 50 items if not specified. |
| projectId | array | yes | One or more project IDs to filter schemes by. Provide multiple IDs as an ampersand-separated list in the query string. |
| startAt | string | – | The starting position for pagination, where 0 represents the first item. Use this to navigate through large result sets. |
No output schema declared.
No examples provided.
list_issue_type_usages List Issue Type Usages ~112
Retrieves the issue types currently using a specific status within a project. Returns paginated results showing which issue types are associated with the given status.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of results to return per page. Must be between 1 and 200, defaults to 50 if not specified. |
| projectId | string | yes | The unique identifier of the project to filter issue type usages. |
| statusId | string | yes | The unique identifier of the status to query for issue type usage. |
No output schema declared.
No examples provided.
list_issue_types List Issue Types ~57
Retrieve all issue types available to the authenticated user. The returned issue types depend on the user's permissions: administrators see all types, users with project browse permissions see types for those projects, and anonymous users see types for projects with anonymous browse access.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_issue_types_for_creation List Issue Types for Creation ~120
Retrieve issue type metadata for a project to determine which issue types can be created and what fields are required. Use this information to populate requests when creating issues.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The number of issue types to return per page, with a maximum of 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 (zero-indexed). Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
list_issue_types_project List Issue Types for Project ~118
Retrieves all issue types available for a specific project, optionally filtered by type hierarchy level (Subtask, Base, or Epic).
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Optional filter to retrieve issue types at a specific hierarchy level: use -1 for Subtasks, 0 for Base issue types, or 1 for Epics. Omit this parameter to retrieve all issue types regardless of level. |
| projectId | string | yes | The numeric identifier of the project. This is a 64-bit integer that uniquely identifies the project in your Jira instance. |
No output schema declared.
No examples provided.
list_issue_watchers List Issue Watchers ~72
Retrieve the list of users watching an issue. Requires the 'Allow users to watch issues' option 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.
list_issue_worklogs List Issue Worklogs ~195
Retrieve time tracking worklogs for an issue, ordered chronologically from oldest to newest. Optionally filter worklogs by start date range using UNIX timestamps in milliseconds.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the project key (e.g., PROJ-123). |
| maxResults | string | – | The maximum number of worklogs to return per page. Defaults to 5000 if not specified. |
| startAt | string | – | The zero-based index for pagination, allowing you to retrieve results starting from a specific position in the list. Defaults to 0 (first page). |
| startedAfter | string | – | Filter to return only worklogs that started on or after this date and time, specified as a UNIX timestamp in milliseconds. |
| startedBefore | string | – | Filter to return only worklogs that started before this date and time, specified as a UNIX timestamp in milliseconds. |
No output schema declared.
No examples provided.
list_jql_autocomplete_data List JQL Autocomplete Data ~49
Retrieve JQL field and function reference data for building and validating JQL queries programmatically. Returns comprehensive metadata including field definitions, available functions, and reserved words to support dynamic query construction.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_jql_autocomplete_data_filtered List JQL Autocomplete Data Filtered ~113
Retrieve JQL field and function reference data to support programmatic query building and validation. Returns system fields always, with optional filtering by project and support for collapsed fields that enable cross-field searches.
| Name | Type | Req | Description |
|---|---|---|---|
| includeCollapsedFields | boolean | – | Include collapsed fields that allow searches across multiple fields with the same name and type. Disabled by default. |
| projectIds | array | – | Filter returned field details by one or more project IDs. Invalid project IDs are ignored; system fields are always included regardless of this filter. |
No output schema declared.
No examples provided.
list_labels List Labels ~93
Retrieve a paginated list of all available labels in the system. Use pagination parameters to control which results are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of labels to return in a single page, with a default of 1000 items per page. |
| startAt | string | – | The starting position for pagination, where 0 represents the first item. Use this to skip earlier results and navigate through pages. |
No output schema declared.
No examples provided.
list_my_filters List My Filters ~94
Retrieve filters owned by the authenticated user, with optional inclusion of their favorite filters. Favorite filters are only visible if they are owned by the user, shared with a group the user belongs to, shared with a private project the user can browse, shared with a public project, or shared publicly.
| Name | Type | Req | Description |
|---|---|---|---|
| includeFavourites | boolean | – | When enabled, includes the user's favorite filters in the response alongside owned filters. Disabled by default. |
No output schema declared.
No examples provided.
list_notification_scheme_project_mappings List Notification Scheme Project Mappings ~157
Retrieve a paginated list of projects and their assigned notification schemes. Filter results by specific notification scheme IDs or project IDs, or retrieve all mappings. Only company-managed projects are supported.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The number of items to return per page. Defaults to 50 items if not specified. |
| notificationSchemeId | array | – | One or more notification scheme IDs to filter the results. Only mappings for these schemes will be returned. |
| projectId | array | – | One or more project IDs to filter the results. Only mappings for these projects will be returned. |
| startAt | string | – | The starting position for pagination, where 0 represents the first item. Use this to navigate through pages of results. |
No output schema declared.
No examples provided.
list_permissions List Permissions ~38
Retrieve all available permissions in the system, including global permissions, project-specific permissions, and permissions added by installed plugins. This operation is accessible without authentication.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_permitted_projects List Permitted Projects ~80
Retrieve all projects where the authenticated user has been granted specific permissions. This operation helps identify which projects a user can access based on their assigned permission keys.
| Name | Type | Req | Description |
|---|---|---|---|
| permissions | array | yes | A list of permission keys to filter projects by. Only projects where the user has all specified permissions will be returned. Permission keys should be provided as strings in the array. |
No output schema declared.
No examples provided.
list_plan_teams List Plan Teams ~93
Retrieve a paginated list of all teams associated with a plan, including both plan-only teams and Atlassian teams. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of teams to return per page, up to a maximum of 50. Defaults to 50 if not specified. |
| planId | string | yes | The unique identifier of the plan for which to retrieve teams. |
No output schema declared.
No examples provided.
list_plans List Plans ~112
Retrieve a paginated list of plans. Requires Jira administrator permissions. Optionally filter results to include trashed or archived plans.
| Name | Type | Req | Description |
|---|---|---|---|
| includeArchived | boolean | – | Include archived plans in the results. By default, only active plans are returned. |
| includeTrashed | boolean | – | Include trashed plans in the results. By default, only active plans are returned. |
| maxResults | string | – | Maximum number of plans to return per page. Must be between 1 and 50, defaults to 50. |
No output schema declared.
No examples provided.
list_priorities List Priorities ~121
Retrieves a paginated list of priorities configured in a specific priority scheme. Use this to fetch all available priorities for a given scheme with optional pagination control.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of priorities to return in a single page of results. Defaults to 50 if not specified. |
| schemeId | string | yes | The unique identifier of the priority scheme from which to retrieve priorities. |
| startAt | string | – | The zero-based index position to start returning results from, enabling pagination through large result sets. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
list_project_avatars List Project Avatars ~63
Retrieves all avatars available for a project, organized into system-provided and custom avatar groups. Requires browse project permission and can be accessed anonymously.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the case-sensitive project key. |
No output schema declared.
No examples provided.
list_project_categories List Project Categories ~30
Retrieves all available project categories in Jira. Use this to populate category selections or understand the complete category taxonomy.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_project_components List Project Components ~193
Retrieve a paginated list of all components in a project. Returns Jira components by default, or Compass components if configured. Requires Browse Projects permission.
| Name | Type | Req | Description |
|---|---|---|---|
| componentSource | string | – | The component source to return: `jira` for Jira components, `compass` for Compass components, or `auto` to return Compass components if available, otherwise Jira components. |
| maxResults | string | – | The maximum number of components to return per page. Defaults to 50 items. |
| orderBy | string | – | Sort results by component attribute: name, description, issue count, or project lead. Prefix with `-` for descending or `+` for ascending order. |
| projectIdOrKey | string | yes | The project identifier, either the project ID or project key (case-sensitive). |
| startAt | string | – | The zero-based index where the result page begins. Use this to navigate through paginated results. |
No output schema declared.
No examples provided.
list_project_features List Project Features ~71
Retrieves all available features for a specified project. Features represent optional capabilities or modules that can be enabled or configured within the project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The unique identifier or key of the project. You can use either the numeric project ID or the case-sensitive project key to identify the project. |
No output schema declared.
No examples provided.
list_project_fields List Project Fields ~191
Retrieve available fields for specified projects and work types. Returns a paginated list of fields that are applicable to the given project and work type combination, with optional filtering by specific field IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldId | array | – | Optional list of specific field IDs to retrieve. If omitted, all available fields for the project and work type combination are returned. |
| maxResults | string | – | The number of fields to return per page. Must be between 1 and 100 items. |
| projectId | array | yes | One or more project IDs to retrieve fields for. Only fields available to these projects will be returned. |
| startAt | string | – | The starting position for pagination (zero-indexed). Use this to retrieve subsequent pages of results. |
| workTypeId | array | yes | One or more work type (issue type) IDs to retrieve fields for. Only fields applicable to these work types will be returned. |
No output schema declared.
No examples provided.
list_project_property_keys List Project Property Keys ~60
Retrieves all property keys stored for a specific project. Property keys are identifiers for custom data associated with the project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (which is case-sensitive). |
No output schema declared.
No examples provided.
list_project_roles List Project Roles ~65
Retrieve all project roles available for a specific project, including their names and API endpoints. Project roles are shared across all projects in Jira Cloud.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (which is case-sensitive). |
No output schema declared.
No examples provided.
list_project_roles_global List Global Project Roles ~48
Retrieve all project roles available in the Jira instance, including their details and default actors. Project roles are used globally across all projects for permission schemes, notifications, issue security, and workflow conditions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_project_roles_with_details List Project Roles with Details ~118
Retrieve all project roles and their details for a specific project. Project roles are shared across all projects in the Jira instance.
| Name | Type | Req | Description |
|---|---|---|---|
| currentMember | boolean | – | Filter roles to show only those assigned to the current user. Defaults to false to return all roles. |
| excludeOtherServiceRoles | boolean | – | Exclude service management roles that don't apply to the project type. Defaults to false to include all roles. |
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (case-sensitive). |
No output schema declared.
No examples provided.
list_project_statuses List Project Statuses ~87
Retrieves all valid statuses for a project, organized by issue type. Each issue type within the project has its own set of valid statuses that can be used for workflow transitions.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (which is case-sensitive). Use the key for human-readable references or the ID for programmatic consistency. |
No output schema declared.
No examples provided.
list_project_types List Project Types ~38
Retrieves all available project types in the Jira instance, including both licensed and unlicensed types. This operation requires no authentication and can be accessed anonymously.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_project_usages_by_status List Project Usages by Status ~88
Retrieves a paginated list of projects that use a specific status. Useful for understanding status adoption and impact across your Jira instance.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of results to return per page. Must be between 1 and 200, defaults to 50 results. |
| statusId | string | yes | The unique identifier of the status to query for project usage. |
No output schema declared.
No examples provided.
list_project_versions List Project Versions ~207
Retrieve a paginated list of all versions in a project. Use this operation when you need to browse versions with pagination control; for a complete unpaginated list, use the alternative get_project_versions operation instead.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of versions to return per page. Defaults to 50 items. |
| orderBy | string | – | Sort the results by a specific field: description, name, releaseDate (oldest first), sequence (UI order), or startDate (oldest first). Prefix with '-' for descending order or '+' for ascending order. |
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (case-sensitive). |
| startAt | string | – | The zero-based index where the paginated results should start. Defaults to 0 for the first page. |
| status | string | – | Filter versions by status using a comma-separated list. Valid statuses are: released, unreleased, and archived. |
No output schema declared.
No examples provided.
list_project_versions_all List Project Versions ~85
Retrieves all versions for a specified project in a single non-paginated response. Use this operation when you need the complete list of versions; for paginated results, use the paginated versions endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The unique identifier for the project, either as the project ID (numeric) or project key (case-sensitive alphanumeric code). |
No output schema declared.
No examples provided.
list_projects List Projects ~394
Retrieve a paginated list of projects visible to the user based on their permissions. Supports filtering by project keys, type, category, and status, with flexible sorting options.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Filter results by the user's permission level on projects: `view` (has browse or admin permissions), `browse` (has browse permission), `edit` (has admin permission), or `create` (can create issues).… |
| categoryId | string | – | Filter results by project category ID. Retrieve available category IDs using the Get all project categories operation. |
| keys | array | – | Filter results to include only specific projects by their keys. Provide up to 50 project keys as a comma-separated list. |
| maxResults | string | – | Maximum number of projects to return per page, capped at 100. Values exceeding 100 will be automatically limited to 100. |
| orderBy | string | – | Sort results by a specific field: category, issue count, project key, last issue update time, project name, project owner/lead, archived date, or deleted date. Prefix with `-` for descending order or… |
| propertyQuery | string | – | Search projects by custom property values using dot-notation syntax. Enclose property keys in square brackets to support keys containing dots or equals signs. This is an experimental feature. |
| startAt | string | – | The starting position for pagination (zero-indexed). Use this to retrieve subsequent pages of results. |
| status | array | – | Filter results by project status: `live` for active projects, `archived` for archived projects, or `deleted` for projects in the recycle bin. This is an experimental feature. |
| typeKey | string | – | Filter results by project type. Accepts comma-separated values: `business`, `service_desk`, or `software`. |
No output schema declared.
No examples provided.
list_recent_projects List Recent Projects ~47
Retrieve up to 20 projects recently viewed by the user, filtered to show only those the user has permission to access. This operation can be used anonymously and respects project-level and global permissions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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
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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mcparmory/atlassian-jira MCP server under?
com.mcparmory/atlassian-jira declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.