A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
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.
100/100
trust score
4k
downloads a day
local
runs on your machine
27k
downloads in 30d
What it does
Community-maintained MCP server for Atlassian Jira Data Center. Not affiliated with Atlassian.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'JIRA_HOST=${JIRA_HOST}' --env 'JIRA_API_TOKEN=${JIRA_API_TOKEN}' --transport stdio jira-mcp '--' npx -y @atlassian-dc-mcp/jira
# 2 — ask your agent for something these tools do
# jira_searchIssues, jira_getIssue, jira_getIssueComments and 14 more
It needs JIRA_HOST, JIRA_API_TOKEN: this reads them from your environment, so export them first.
Jira costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
B1All 3 servers
b1ff3 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 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. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads JIRA_HOST (Jira host domain (e.g. your-instance.atlassian.net). Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE or JIRA_API_BASE_PATH), JIRA_API_TOKEN (Jira Personal Access Token or API token. Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx JIRA_HOST …, setx JIRA_API_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'JIRA_HOST=${JIRA_HOST}' --env 'JIRA_API_TOKEN=${JIRA_API_TOKEN}' --transport stdio jira-mcp '--' npx -y @atlassian-dc-mcp/jiraReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: JIRA_HOST — Jira host domain (e.g. your-instance.atlassian.net). Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE or JIRA_API_BASE_PATH.; JIRA_API_TOKEN — Jira Personal Access Token or API token. Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE.. You set them in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search for JIRA issues using JQL in the JIRA Data Center edition instance
No parameter schema on file.
Get details of a JIRA issue by its key from the JIRA Data Center edition instance
No parameter schema on file.
Get comments of a JIRA issue by its key from the JIRA Data Center edition instance
No parameter schema on file.
Create a new JIRA issue in the JIRA Data Center edition instance
No parameter schema on file.
Update an existing JIRA issue in the JIRA Data Center edition instance
No parameter schema on file.
Post a comment on a JIRA issue in the JIRA Data Center edition instance
No parameter schema on file.
Update the body of an existing comment on a JIRA issue in the JIRA Data Center edition instance. Use jira_getIssueComments to find the comment id.
No parameter schema on file.
Get available status transitions for a JIRA issue in the JIRA Data Center edition instance. Returns a list of transitions with their IDs, names, and target statuses.
No parameter schema on file.
Get linked development information (pull requests, commits, or branches) shown in the Development panel of a JIRA issue in the JIRA Data Center edition instance. Defaults to pull requests from Bitbucket.
No parameter schema on file.
Transition a JIRA issue to a new status in the JIRA Data Center edition instance. Use jira_getTransitions first to get available transition IDs.
No parameter schema on file.
Get the list of available issue link types (e.g. Blocks, Relates, Duplicate) in the JIRA Data Center edition instance. Use this to discover valid link type names before calling jira_linkIssues.
No parameter schema on file.
Create a link between two JIRA issues in the JIRA Data Center edition instance. Direction is easy to invert vs the Jira UI: inwardIssueKey is the issue that DISPLAYS the outward phrase (e.g. 'blocks'); outwardIssueKey displays the inward phrase (e.g. 'is blocked by'). After create, GET the first…
No parameter schema on file.
Delete an existing link between two JIRA issues in the JIRA Data Center edition instance. Requires the issue link id (found in the 'issuelinks' field of an issue).
No parameter schema on file.
Add yourself (the authenticated user) as a watcher on a JIRA issue in the JIRA Data Center edition instance. Only the calling user can be added; there is no way to watch on behalf of someone else.
No parameter schema on file.
Remove yourself (the authenticated user) as a watcher from a JIRA issue in the JIRA Data Center edition instance. Only the calling user can be removed; there is no way to unwatch on behalf of someone else.
No parameter schema on file.
Upload a local file as an attachment to a JIRA issue in the JIRA Data Center edition instance. The file must live under the server-configured upload directory; the path is given relative to that directory.
No parameter schema on file.
Download attachment(s) from a JIRA issue in the JIRA Data Center edition instance, by issue key (optionally filtered by filename) or by a single attachment id. Returns the file content inline (base64 or text). Useful for inspecting a file or moving it elsewhere (e.g. re-uploading to a Confluence…
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- 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 Jira or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.38.0 · scanned 14 Oct 2026
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.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest4f3a28170534e8f1e287065db2b400b18f1d5ea45984d59036e7142b9866ab33
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
16 of the 17 recovered tools are registered only when missingEnvVars.length > 0 is false (build/index.js:9) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 17 recovered tools are registered only when attachmentGateway.upload.enabled holds (build/index.js:81) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
build/jira-client/models/AffectedEntityBean.d.ts (1 KB) was not read: over the file-count budget.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
No tool is registered unconditionally · (1) 16 only when missingEnvVars.length > 0 is false (build/index.js:9) · (2) 1 only when attachmentGateway.upload.enabled holds (build/index.js:81) — typically when a key or option is configured. All 17 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| jira_searchIssues conditional (1) | no tags | |
| jira_getIssue conditional (1) | no tags | |
| jira_getIssueComments conditional (1) | no tags | |
| jira_createIssue conditional (1) | no tags | |
| jira_updateIssue conditional (1) | no tags | |
| jira_postIssueComment conditional (1) | no tags | |
| jira_updateIssueComment conditional (1) | no tags | |
| jira_getTransitions conditional (1) | no tags | |
| jira_getIssueDevelopmentInfo conditional (1) | no tags | |
| jira_transitionIssue conditional (1) | no tags | |
| jira_getIssueLinkTypes conditional (1) | no tags | |
| jira_linkIssues conditional (1) | no tags | |
| jira_unlinkIssues conditional (1) | no tags | |
| jira_watchIssue conditional (1) | no tags | |
| jira_unwatchIssue conditional (1) | no tags | |
| jira_uploadAttachment conditional (2) | no tags | |
| jira_downloadAttachment conditional (1) | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest4f3a28170534e8f1
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.38.0. Pin a release below and the command asks for exactly that one.
0.38.0
12 Oct 2026
latestNo release note was published with this version.
0.37.0
9 Oct 2026
No release note was published with this version.
0.35.0
22 Sep 2026
No release note was published with this version.
0.34.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Jira can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.