Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Atlassian Jira is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search, create and transition Jira issues, worklogs, links and attachments.
Quickstart
This image runs as a local HTTP server (Streamable HTTP), not over stdio, and the port it listens on is not recorded here, so there is no line to print: start it the way its own source says, publishing that port with -p, then add its address to your client as a remote server.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Atlassian Jira as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
This image runs as a local HTTP server (Streamable HTTP), not over stdio, and the port it listens on is not recorded here, so there is no line to print: start it the way its own source says, publishing that port with -p, then add its address to your client as a remote server.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Add a comment to a Jira issue, or update an existing comment when commentId is given.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| body | string | yes | — |
| commentId | string | no | — |
Add a user as a watcher on a Jira issue, so they are notified of changes. Takes an account id: use lookupJiraAccountId to turn a name or email into one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| accountId | string | yes | — |
Log time against a Jira issue. timeSpent uses Jira's own duration wording, for example '3h 30m', '1d', '45m'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| timeSpent | string | yes | — |
| comment | string | no | — |
| started | string | no | — |
Assign a Jira issue to a user, or unassign it. Takes an account id: use lookupJiraAccountId to turn a name or email into one. Send either accountId or unassign, not neither.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| accountId | string | no | — |
| unassign | boolean | no | — |
Get the current authenticated user's Atlassian account information (account id, name, email). Useful for resolving 'me' or 'assign it to me' to a concrete account id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
Create a Jira issue in a project. When the project's required fields are not known, call getJiraIssueTypeMetaWithFields first: a project can require fields this tool does not name explicitly, and those go in additionalFields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| projectKey | string | yes | — |
| summary | string | yes | — |
| issueTypeName | string | yes | — |
| description | string | no | — |
| assigneeAccountId | string | no | — |
| additionalFields | object | no | — |
Link two Jira issues, for example 'PROJ-1 blocks PROJ-2'. The link type name must be one getIssueLinkTypes returns, and direction matters: inwardIssue is the one the relationship points at.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| linkTypeName | string | yes | — |
| inwardIssueKey | string | yes | — |
| outwardIssueKey | string | yes | — |
| comment | string | no | — |
Create a component in a Jira project, so issues can be assigned to it. leadAccountId sets who owns it; use lookupJiraAccountId to turn a name or email into one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| projectKey | string | yes | — |
| name | string | yes | — |
| description | string | no | — |
| leadAccountId | string | no | — |
Create a version (release) in a Jira project, so issues can be assigned to it via fixVersions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| projectKey | string | yes | — |
| name | string | yes | — |
| description | string | no | — |
| releaseDate | string | no | — |
Permanently delete a Jira issue. This cannot be undone. Jira rejects the call rather than leaving orphaned subtasks when deleteSubtasks is false and subtasks exist.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| deleteSubtasks | boolean | no | — |
Delete an attachment from a Jira issue by its attachment id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| attachmentId | string | yes | — |
Update fields on an existing Jira issue. Only the fields supplied are changed; everything else is left as it is. Send at least one of summary, description, assigneeAccountId or additionalFields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| summary | string | no | — |
| description | string | no | — |
| assigneeAccountId | string | no | — |
| additionalFields | object | no | — |
List every Atlassian site this connection can reach, with the cloudId of each. Every other tool needs a cloudId, so call this first when the site is not already known, and whenever an account has access to more than one site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
List the issue link types this site defines (for example 'Blocks', 'Relates'), with the inward and outward wording of each.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
List the Scrum/Kanban boards for a Jira project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| projectKeyOrId | string | yes | — |
| maxResults | integer | no | — |
| startAt | integer | no | — |
List the issues under a Jira epic.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| epicIdOrKey | string | yes | — |
| maxResults | integer | no | — |
| startAt | integer | no | — |
Get a Jira issue by its key (for example 'PROJ-123') or numeric id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| includeComments | boolean | no | — |
List the attachments on a Jira issue: filename, size, type, and a link. addJiraIssueAttachment adds one; deleteJiraIssueAttachment removes one by its id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
List the field changes recorded on a Jira issue: who changed what, from what, to what, and when. This is the issue's audit trail.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| maxResults | integer | no | — |
| startAt | integer | no | — |
List remote links on a Jira issue, such as linked Confluence pages or external URLs. These are separate from issue-to-issue links.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
Get the fields available when creating an issue of a given type in a given project, including which are required. Call this before createJiraIssue when the project's required fields are unknown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| projectIdOrKey | string | yes | — |
| issueTypeId | string | yes | — |
List the users watching a Jira issue. Watchers are notified of every change, so this answers who is already following an issue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
List the worklog entries on a Jira issue: who logged time, how much, and when. addWorklogToJiraIssue writes these.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| maxResults | integer | no | — |
| startAt | integer | no | — |
List the issue priorities this site defines (for example 'High', 'Low').
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
List the components defined in a Jira project. createJiraProjectComponent adds one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| projectIdOrKey | string | yes | — |
List the issue types available in a Jira project, with their ids.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| projectIdOrKey | string | yes | — |
List the versions (releases) defined in a Jira project, with their release status. createJiraProjectVersion adds one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| projectIdOrKey | string | yes | — |
List the issue resolutions this site defines (for example 'Fixed', "Won't Do").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
List the sprints on a board, newest first. Filter by state to find the active sprint, e.g. state='active'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| boardId | string | yes | — |
| state | string | no | — |
| maxResults | integer | no | — |
| startAt | integer | no | — |
List the issue statuses this site defines (for example 'To Do', 'Done').
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
List the workflow transitions currently available on an issue. The returned transition id is what transitionJiraIssue needs, and which transitions exist depends on the issue's current status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
List the Jira projects this user can see, newest page first. Use the returned key when another tool asks for a project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| searchString | string | no | — |
| maxResults | integer | no | — |
| startAt | integer | no | — |
Find Jira users by display name or email and return their account ids. Assignment and mention tools need an account id, never a name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| searchString | string | yes | — |
| maxResults | integer | no | — |
Move up to 50 Jira issues into a sprint.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| sprintId | string | yes | — |
| issueKeys | array | yes | — |
Delete a link between two Jira issues by its link id. The id comes from an issue's links, not from the issue keys themselves.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| linkId | string | yes | — |
Remove a user from a Jira issue's watchers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| accountId | string | yes | — |
Search Jira issues with a JQL query, for example 'project = PROJ AND status = "In Progress" ORDER BY created DESC'. Returns a page of issues plus a cursor for the next page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| jql | string | yes | — |
| maxResults | integer | no | — |
| nextPageToken | string | no | — |
Move a Jira issue through its workflow. Which transitions are legal depends on the issue's current status, so call getTransitionsForJiraIssue first to get a valid transitionId.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| transitionId | string | yes | — |
| comment | string | no | — |
Move a Jira issue to a status by name, e.g. 'In Progress' or 'Done', instead of a transition id. Looks up the matching transition automatically. Which statuses are reachable depends on the issue's current one and its workflow, so a status that exists on the site can still be unreachable from here;…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentials | object | yes | — |
| issueIdOrKey | string | yes | — |
| status | string | yes | — |
| comment | string | no | — |
Attach one or more files to a Jira issue. Pass files uploaded to the workflow (e.g. a Start node file or image field) or produced by another tool through attachments, as their platform file_id or storage key; the platform fetches the bytes from its storage, so large files work. fileName +…
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Atlassian Jira or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 2.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Atlassian Jira can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.