com.mcparmory/atlassian-jira
OCI · GHCR.IO/MCPARMORY/ATLASSIAN-JIRA:1.0.3 · 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 Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
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: no license is declared. 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 Management83
- Stability observed for 25 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/atlassian-jira MCP server?
com.mcparmory/atlassian-jira runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/atlassian-jira:1.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/atlassian-jira:1.0.3
claude mcp add com-mcparmory-atlassian-jira -- docker run --rm -i ghcr.io/mcparmory/atlassian-jira:1.0.3
{
"mcpServers": {
"com-mcparmory-atlassian-jira": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/atlassian-jira:1.0.3"
]
}
}
} {
"servers": {
"com-mcparmory-atlassian-jira": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/atlassian-jira:1.0.3"
]
}
}
} codex mcp add com-mcparmory-atlassian-jira -- docker run --rm -i ghcr.io/mcparmory/atlassian-jira:1.0.3
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-atlassian-jira": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/atlassian-jira:1.0.3"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-atlassian-jira:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/atlassian-jira:1.0.3"] {
"McpServers": {
"com-mcparmory-atlassian-jira": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/atlassian-jira:1.0.3"
]
}
}
} {
"mcpServers": {
"com-mcparmory-atlassian-jira": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/atlassian-jira:1.0.3"
]
}
}
} 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.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 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.
- 12 Sept 26 −2
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 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.
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 oci/ghcr.io/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 | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
get_locale Get Locale ~53
Retrieves the locale preference for the current user. If no preference is set, returns the browser locale detected from the Accept-Language header, or the site default locale if no match is found. This operation can be accessed anonymously.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_plan_only_team Get Plan-Only Team ~83
Retrieve planning settings and configuration for a specific plan-only team within a plan. Requires Jira administrator permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| planId | string | yes | The unique identifier of the plan containing the team. Must be a positive integer. |
| planOnlyTeamId | string | yes | The unique identifier of the plan-only team whose settings you want to retrieve. Must be a positive integer. |
No output schema declared.
No examples provided.
get_priority Get Priority ~48
Retrieve details of a specific issue priority in Jira. Returns the priority configuration including its name, description, and other metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the issue priority to retrieve. |
No output schema declared.
No examples provided.
get_project Get Project ~78
Retrieve detailed information about a specific project, including its configuration and metadata. Requires Browse projects permission for the target project.
| 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). Project keys are typically short uppercase abbreviations like 'PROJ'. |
No output schema declared.
No examples provided.
get_project_category Get Project Category ~50
Retrieve a specific project category by its ID. Returns the category details for use in project organization and filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the project category as a 64-bit integer. |
No output schema declared.
No examples provided.
get_project_classification Get Default Project Classification ~69
Retrieve the default data classification level assigned to a project. This determines the default sensitivity or confidentiality level for issues and data within the project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The unique identifier for the project, either as the numeric project ID or the project key (which is case-sensitive). |
No output schema declared.
No examples provided.
get_project_components_all Get Project Components ~109
Retrieves all components in a project, including Compass components if the project is opted into Compass. Requires Browse Projects permission and can be accessed anonymously.
| Name | Type | Req | Description |
|---|---|---|---|
| componentSource | string | – | The source of components to return: use 'jira' for Jira components (default), 'compass' for Compass components, or 'auto' to return Compass components if available, otherwise Jira components. |
| projectIdOrKey | string | yes | The project identifier, either the project ID or project key (case-sensitive). |
No output schema declared.
No examples provided.
get_project_email Get Project Email ~53
Retrieves the sender email address configured for a project. This email is used as the from address for project notifications and communications.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | The unique identifier of the project. Must be a positive integer. |
No output schema declared.
No examples provided.
get_project_property Get Project Property ~90
Retrieves the value of a specific project property by its key. Requires Browse Projects permission for the project containing the property.
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (case-sensitive). |
| propertyKey | string | yes | The key identifying the project property to retrieve. Use the list project property keys operation to discover available property keys for a project. |
No output schema declared.
No examples provided.
get_project_role Get Project Role ~126
Retrieve a project role's details and the list of actors (users and groups) assigned to it within a specific project. The actors are returned sorted by display name.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeInactiveUsers | boolean | – | When enabled, filters out inactive users from the returned actors list. Defaults to false, including all users. |
| id | string | yes | The numeric ID of the project role to retrieve. Use the get_project_roles operation to discover available project role IDs. |
| projectIdOrKey | string | yes | The project identifier, either the numeric project ID or the project key (case-sensitive). |
No output schema declared.
No examples provided.
get_project_role_global Get Project Role ~65
Retrieve the details of a specific project role, including its default actors sorted by display name. Requires Jira administrator permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the project role as a 64-bit integer. Retrieve available project role IDs using the list project roles operation. |
No output schema declared.
No examples provided.
get_project_type Get Project Type ~69
Retrieve detailed information about a specific project type by its key. This operation is publicly accessible and requires no authentication or permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| projectTypeKey | string | yes | The unique identifier for the project type. Must be one of the following: software, service_desk, business, or product_discovery. |
No output schema declared.
No examples provided.
get_remote_link Get Remote Link ~81
Retrieves a specific remote issue link for an issue. Requires issue linking to be enabled and appropriate project permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, which can be either the numeric issue ID or the issue key (e.g., PROJECT-123). |
| linkId | string | yes | The unique identifier of the remote issue link to retrieve. |
No output schema declared.
No examples provided.
get_resolution Get Resolution ~50
Retrieve the details of a specific issue resolution value by its ID. This returns metadata about how an issue can be resolved in Jira.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the resolution value to retrieve. |
No output schema declared.
No examples provided.
get_security_level Get Security Level ~54
Retrieve detailed information about a specific issue security level. Use this to get security level properties after obtaining the level ID from the issue security scheme.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the issue security level to retrieve. |
No output schema declared.
No examples provided.
get_status Get Status ~81
Retrieve a status associated with an active workflow by its ID or name. If multiple statuses share the same name, the first match is returned; using the status ID is recommended for precise identification.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrName | string | yes | The unique identifier or display name of the status. Using the status ID is preferred when the name may not be unique across your instance. |
No output schema declared.
No examples provided.
get_status_category Get Status Category ~52
Retrieve a status category by its ID or key. Status categories are used to group and organize statuses in Jira workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| idOrKey | string | yes | The unique identifier or key of the status category to retrieve. |
No output schema declared.
No examples provided.
get_task Get Task ~60
Retrieve the status and results of a long-running asynchronous task. Once completed, returns the JSON response applicable to the task; details are retained for 14 days.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | The unique identifier of the task to retrieve status and results for. |
No output schema declared.
No examples provided.
get_team Get Atlassian Team ~83
Retrieve planning settings and configuration for an Atlassian team within a specific plan. Requires Administer Jira global permission.
| Name | Type | Req | Description |
|---|---|---|---|
| atlassianTeamId | string | yes | The unique identifier of the Atlassian team whose planning settings should be retrieved. |
| planId | string | yes | The unique identifier of the plan containing the team. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
get_user Get User ~85
Retrieve a user's profile information from Jira. Privacy controls are applied based on the user's preferences, which may hide sensitive details like email addresses.
| 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. |
No output schema declared.
No examples provided.
get_user_preference Get User Preference ~92
Retrieves a specific preference value for the current user. Use this to fetch user settings like notifications, locale, or timezone preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The preference key to retrieve (e.g., jira.user.locale, jira.user.timezone, user.notifications.watcher). Note that some keys like jira.user.locale and jira.user.timezone are deprecated; use the user… |
No output schema declared.
No examples provided.
get_user_property Get User Property ~114
Retrieves the value of a specific property associated with a user account. Requires either Jira administrator permissions to access any user's properties, or standard Jira access to retrieve properties from your own user record.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | – | The account ID of the user, which uniquely identifies the user across all Atlassian products. For example, *5b10ac8d82e05b22cc7d4ef5*. |
| propertyKey | string | yes | The unique identifier for the user property you want to retrieve. |
No output schema declared.
No examples provided.
get_version Get Version ~52
Retrieve details for a specific project version by its ID. This operation can be accessed anonymously and requires Browse projects permission for the project containing the version.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the version to retrieve. |
No output schema declared.
No examples provided.
get_version_unresolved_issues Get Version Unresolved Issue Count ~56
Retrieves the count of total and unresolved issues for a specific project version. Useful for tracking version completion status and identifying outstanding work.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the version for which to retrieve issue counts. |
No output schema declared.
No examples provided.
get_workflow_default_editor Get Workflow Default Editor ~31
Retrieve the user's default workflow editor preference, which can be either the new editor or the legacy editor.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_worklog Get Worklog ~80
Retrieve a specific worklog entry for an issue. Time tracking must be enabled in Jira for this operation to succeed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the worklog entry to retrieve. |
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the human-readable key (e.g., PROJ-123). |
No output schema declared.
No examples provided.
get_worklog_property Get Worklog Property ~112
Retrieves a specific property value associated with a worklog entry. Requires appropriate project and issue permissions, plus any worklog visibility restrictions must be satisfied.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdOrKey | string | yes | The issue identifier, either the numeric ID or the human-readable key (e.g., PROJ-123). |
| propertyKey | string | yes | The name of the property to retrieve from the worklog. |
| worklogId | string | yes | The unique identifier of the worklog entry from which to retrieve the property. |
No output schema declared.
No examples provided.
get_worklogs Get Worklogs ~87
Retrieve detailed worklog information for a specified list of worklog IDs. Returns up to 1000 worklogs where you have permission to view them.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | A list of worklog IDs to retrieve. Only worklogs that are viewable by all users or where you have project role or group permissions will be returned, up to a maximum of 1000 items. |
No output schema declared.
No examples provided.
grant_filter_share_permission Grant Filter Share Permission ~236
Grant share permission for a filter to a user, group, project, or project role. Global or authenticated permissions will override all existing share permissions for the filter.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the filter to share. Must be a positive integer. |
| projectId | string | – | The project identifier to share the filter with. Required when type is set to 'project'. |
| projectRoleId | string | – | The project role identifier to share the filter with. Required when type is set to 'projectRole'; must be used together with projectId. |
| rights | string | – | The access rights level for this share permission. Specified as a 32-bit integer representing the permission level. |
| type | string | yes | The recipient type for the share permission. Choose from: 'user' (share with individual user), 'group' (share with group), 'project' (share with project), 'projectRole' (share with project role), 'gl… |
No output schema declared.
No examples provided.
link_remote_issue Link Remote Issue ~216
Creates or updates a remote issue link to connect an issue with an item in an external system. If a globalId is provided and a matching link exists, it updates the link; otherwise, it creates a new one.
| Name | Type | Req | Description |
|---|---|---|---|
| application | object | – | Details about the remote application containing the linked item, such as the application name or identifier (e.g., trello, confluence). |
| globalId | string | – | A unique identifier for the remote item in the external system that enables updating or deleting the link using remote system details instead of the Jira record ID. Maximum length is 255 characters. |
| issueIdOrKey | string | yes | The Jira issue identifier, either the numeric ID or the issue key (e.g., PROJ-123). |
| object | object | yes | Details about the item being linked to, including its URL, title, and other metadata from the remote system. |
| relationship | string | – | A description of how the issue relates to the linked item. If not specified, defaults to 'links to'. |
No output schema declared.
No examples provided.
list_accessible_project_types List Accessible Project Types ~39
Retrieve all project types available with valid licenses in your Jira instance. Use this to discover which project type options are available for creating new projects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_alternative_issue_types List Alternative Issue Types ~63
Retrieve a list of issue types that can replace a given issue type. The alternatives are those sharing the same workflow scheme, field configuration scheme, and screen scheme.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier of the issue type for which to find compatible alternatives. |
No output schema declared.
No examples provided.
list_assignable_users List Assignable Users ~213
Retrieve a list of users who can be assigned to an issue, optionally filtered by project, issue, or workflow transition. Use this to populate assignee dropdowns or validate user assignment eligibility.
| Name | Type | Req | Description |
|---|---|---|---|
| accountType | array | – | Filter results by account type (e.g., atlassian, app, customer). Specify as a comma-separated list if multiple types are needed. |
| actionDescriptorId | string | – | The workflow transition ID to check assignability during a state change. Use with issueKey or issueId to validate users for a specific transition. |
| issueId | string | – | The issue ID to check assignability against. Required unless issueKey or project is specified. |
| maxResults | string | – | Maximum number of users to return per page. Defaults to 50. Note: the operation may return fewer users than requested, as it filters results to only assignable users. |
| startAt | string | – | The starting position for pagination (zero-indexed). Defaults to 0 for the first page. |
No output schema declared.
No examples provided.
list_assignable_users_multiproject List Assignable Users Across Multiple Projects ~135
Retrieve users who can be assigned issues across one or more projects. Results are filtered based on user attributes and privacy settings, and may return fewer users than requested due to pagination constraints.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | Maximum number of users to return per page. Defaults to 50 if not provided. |
| projectKeys | string | yes | Comma-separated list of project keys (case-sensitive) to search for assignable users. At least one project key is required. |
| startAt | string | – | Zero-based index for pagination to specify which result page to return. Defaults to 0 if not provided. |
No output schema declared.
No examples provided.
list_available_priorities List Available Priorities ~118
Retrieves a paginated list of priorities that can be added to a specific priority scheme. Use this to discover which priorities are available for assignment within your priority scheme.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The number of priorities to return per page. Defaults to 50 items if not specified. |
| schemeId | string | yes | The unique identifier of the priority scheme for which to retrieve available priorities. |
| 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_avatars List Avatars ~96
Retrieves all available avatars (system and custom) for a project, issue type, or priority. Supports anonymous access for system and priority avatars, with permission checks for custom project and issue type avatars.
| Name | Type | Req | Description |
|---|---|---|---|
| entityId | string | yes | The unique identifier of the entity (project, issue type, or priority) associated with the avatars. |
| type | string | yes | The category of avatar to retrieve: project, issue type, or priority. |
No output schema declared.
No examples provided.
list_bulk_editable_fields List Bulk Editable Fields ~99
Retrieve a list of fields that are editable in bulk operations for the specified issues. Returns up to 50 fields per page, optionally filtered by search text.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIdsOrKeys | string | yes | One or more issue IDs or keys to determine which fields are eligible for bulk editing. Provide as a comma-separated list or array of values. |
| searchText | string | – | Optional text to filter the returned editable fields by name or description. |
No output schema declared.
No examples provided.
list_classification_levels List Classification Levels ~107
Retrieves all available classification levels, optionally filtered by status and sorted by rank. No permissions are required to access this endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| orderBy | string | – | Optional field to sort results by rank. Use 'rank' for ascending order, '+rank' for ascending, or '-rank' for descending order. If not specified, results are returned unsorted. |
| status | array | – | Optional filter to return only classification levels matching the specified statuses. Provide as an array of status values. |
No output schema declared.
No examples provided.
list_comment_property_keys List Comment Property Keys ~54
Retrieves all property keys associated with a specific comment. Useful for discovering what custom properties have been set on a comment.
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | The unique identifier of the comment whose property keys you want to retrieve. |
No output schema declared.
No examples provided.
list_comments List Comments ~72
Retrieve a paginated list of comments by their IDs. Returns comments where you have appropriate project browse permissions and any required issue-level security or visibility group/role permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | A list of comment IDs to retrieve. Specify up to 1000 IDs per request. Order is preserved in the response. |
No output schema declared.
No examples provided.
list_components List Components ~177
Retrieve a paginated list of all components in specified projects, including global Compass components when applicable. Requires Browse Projects permission for the target project(s).
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | string | – | The maximum number of components to return in a single page. Defaults to 50 items per page. |
| orderBy | string | – | Sort results by component name or description. Use `name` or `description` for ascending order, prefix with `-` for descending order, or `+` for explicit ascending order. |
| projectIdsOrKeys | array | – | One or more project IDs or keys (case-sensitive) to filter components. If not provided, returns components from all accessible projects. |
| startAt | string | – | The zero-based index position to start returning results from, enabling pagination through large result sets. Defaults to 0 (first item). |
No output schema declared.
No examples provided.
list_custom_field_context_issue_type_mappings List Custom Field Context Issue Type Mappings ~147
Retrieve a paginated list of issue type mappings for a custom field across specified contexts. Results are ordered by context ID first, then by issue type ID.
| Name | Type | Req | Description |
|---|---|---|---|
| contextId | array | – | Filter results to specific contexts by providing one or more context IDs. Omit to retrieve mappings for all contexts. |
| fieldId | string | yes | The unique identifier of the custom field for which to retrieve issue type mappings. |
| maxResults | string | – | The maximum number of mappings to return per page. Defaults to 50 items if not specified. |
| startAt | string | – | The zero-based index position to start returning results from, enabling pagination through large result sets. |
No output schema declared.
No examples provided.
list_custom_field_options List Custom Field Options ~156
Retrieve a paginated list of custom field options for a specific context, including both regular and cascading options in display order. Requires Jira administration or workflow edit permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| contextId | string | yes | The unique identifier of the context associated with the custom field. |
| fieldId | string | yes | The unique identifier of the custom field. |
| maxResults | string | – | The maximum number of options to return per page, up to 100 items. |
| onlyOptions | boolean | – | When enabled, returns only the direct options without cascading options. |
| optionId | string | – | Filter results to a specific option by its unique identifier. |
| startAt | string | – | The zero-based index position to start returning results from for pagination. |
No output schema declared.
No examples provided.
list_dashboard_gadgets List Dashboard Gadgets ~29
Retrieves a list of all available gadgets that can be added to dashboards. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_dashboard_item_property_keys List Dashboard Item Property Keys ~81
Retrieves all property keys associated with a specific dashboard item. This operation allows you to discover what custom properties are available for a dashboard item without retrieving their values.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboardId | string | yes | The unique identifier of the dashboard containing the item. |
| itemId | string | yes | The unique identifier of the dashboard item whose property keys you want to retrieve. |
No output schema declared.
No examples provided.
list_dashboards List Dashboards ~139
Retrieve a list of dashboards owned by or shared with the user. Results can be filtered to show only favorite or owned dashboards, with support for pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Filter the dashboard list by ownership or favorite status. Use 'my' to show only dashboards you own, or 'favourite' to show only dashboards you've marked as favorites. |
| maxResults | string | – | The maximum number of dashboards to return per page. Defaults to 20 if not specified. |
| startAt | string | – | The starting position for pagination (zero-indexed). Use this to retrieve subsequent pages of results. Defaults to 0 if not specified. |
No output schema declared.
No examples provided.
list_deleted_worklogs List Deleted Worklogs ~93
Retrieve a paginated list of worklog IDs and deletion timestamps for worklogs deleted after a specified date and time. Results are ordered from oldest to youngest, with up to 1000 worklogs per page.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | The UNIX timestamp in milliseconds marking the start of the deletion window. Only worklogs deleted after this timestamp are returned. Defaults to 0 (epoch start) if not specified. |
No output schema declared.
No examples provided.
list_events List Events ~26
Retrieve all issue events from your Jira instance. Requires Administer Jira global permission to access.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_favorite_filters List Favorite Filters ~59
Retrieves all visible favorite filters for the authenticated user. A filter is visible only if it's owned by the user, shared with a group they belong to, shared with a private project they can browse, shared with a public project, or shared publicly.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_field_option_suggestions List Field Option Suggestions ~180
Retrieve a paginated list of selectable options for a Connect app custom issue field that the user can view and select. This operation only works with field options added by Connect apps, not those created natively in Jira.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldKey | string | yes | The field key in the format $(app-key)__$(field-key), such as example-add-on__example-issue-field. Find this value in the app's plugin descriptor or by calling Get fields. |
| maxResults | string | – | The maximum number of options to return per page. Defaults to 50 items. |
| projectId | string | – | Optionally filter results to show only options available in a specific project by providing its numeric ID. |
| 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.
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 container image (ghcr.io/mcparmory/atlassian-jira:1.0.3).
Is the com.mcparmory/atlassian-jira MCP server safe to use?
com.mcparmory/atlassian-jira scores 50 out of 100 on VerifyMCP. 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.