MCP Server for ZenTao bug management with CAS SSO login
from $14/mo
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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Community-maintained MCP server for Atlassian Jira Data Center. Not affiliated with Atlassian.
Quickstart
# 1 — run it from where its publisher ships it
npx -y @atlassian-dc-mcp/jira
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> Community-maintained MCP server for Atlassian Jira Data Center. Not affiliated with Atlassian.
Publishernot claimed
BFAll 2 servers
b1ff2 servers
2 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. It is scanned, signed and pinned to the version you choose — 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. Claude Code registers it in one command.
claude mcp add jira-mcp -- npx -y @atlassian-dc-mcp/jiraReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
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
14 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 ${jiraInstanceType}
Takes no parameters.
Example callreturns →
Get details of a JIRA issue by its key from the ${jiraInstanceType}
Takes no parameters.
Example callreturns →
Get comments of a JIRA issue by its key from the ${jiraInstanceType}
Takes no parameters.
Example callreturns →
Create a new JIRA issue in the ${jiraInstanceType}
Takes no parameters.
Example callreturns →
Update an existing JIRA issue in the ${jiraInstanceType}
Takes no parameters.
Example callreturns →
Post a comment on a JIRA issue in the ${jiraInstanceType}
Takes no parameters.
Example callreturns →
Get available status transitions for a JIRA issue in the ${jiraInstanceType}. Returns a list of transitions with their IDs, names, and target statuses.
Takes no parameters.
Example callreturns →
Get linked development information (pull requests, commits, or branches) shown in the Development panel of a JIRA issue in the ${jiraInstanceType}. Defaults to pull requests from Bitbucket.
Takes no parameters.
Example callreturns →
Transition a JIRA issue to a new status in the ${jiraInstanceType}. Use jira_getTransitions first to get available transition IDs.
Takes no parameters.
Example callreturns →
Get the list of available issue link types (e.g. Blocks, Relates, Duplicate) in the ${jiraInstanceType}. Use this to discover valid link type names before calling jira_linkIssues.
Takes no parameters.
Example callreturns →
Create a link between two JIRA issues in the ${jiraInstanceType}. Use jira_getIssueLinkTypes to find valid link type names.
Takes no parameters.
Example callreturns →
Delete an existing link between two JIRA issues in the ${jiraInstanceType}. Requires the issue link id (found in the
Takes no parameters.
Example callreturns →
Upload a local file as an attachment to a JIRA issue in the ${jiraInstanceType}. The file must live under the server-configured upload directory; the path is given relative to that directory.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Standardmost installed
$25 / month
- 20,000 calls a month, included
- 240 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Team
$65 / month
- 150,000 calls a month, included
- 1,800 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $25 a month covers every tool 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: $8.42
$16.58 left
ATrust score 100 / 100
Release 0.29.0 · scanned 25 Aug 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
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest3d7dc524bf56218b8ad7a55c2411091fd9bf017bdeb3ebf22a8ee6660422e3a9
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 (14 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>".
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.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| jira_searchIssues | no tags | |
| jira_getIssue | no tags | |
| jira_getIssueComments | no tags | |
| jira_createIssue | no tags | |
| jira_updateIssue | no tags | |
| jira_postIssueComment | no tags | |
| jira_getTransitions | no tags | |
| jira_getIssueDevelopmentInfo | no tags | |
| jira_transitionIssue | no tags | |
| jira_getIssueLinkTypes | no tags | |
| jira_linkIssues | no tags | |
| jira_unlinkIssues | no tags | |
| jira_uploadAttachment | no tags | |
| jira_downloadAttachment | 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 digest3d7dc524bf56218b
Scanned2026-08-25
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
Pinned to 0.29.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.29.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Jira in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.