Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
Jira Dc 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.
94/100
trust score
78
tools declared
local
runs on your machine
—
downloads a day
What it does
MCP server for Jira Data Center and Jira Server
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user tekthar-jira-dc-mcp '--' npx -y mcp-jira-dc
# 2 — ask your agent for something these tools do
# jira_searchIssues, jira_getIssue, jira_getIssueComments and 75 more
Jira Dc costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TEAll 3 servers
tekthar3 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 Dc 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. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user tekthar-jira-dc-mcp '--' npx -y mcp-jira-dcReconnect, 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
Nothing is required, but it can take ATLASSIAN_DC_MCP_CONFIG_FILE (Absolute path to a shared dotenv-style config file. When set, values are read from this file before direct environment variable overrides are applied.), 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_BASE_PATH (Jira API base path (alternative to JIRA_HOST). Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE or JIRA_HOST.), JIRA_API_TOKEN (Jira Personal Access Token or API token. Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE.) if you want to set them.
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
78 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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.
List the versions (releases) of a JIRA project in the JIRA Data Center edition instance, optionally filtered by name, released and archived state. Returns ids, names, dates and release state.
No parameter schema on file.
Get a JIRA project version (release) by its id from the JIRA Data Center edition instance. To list its issues, use jira_searchIssues with JQL such as 'fixVersion = <id> AND resolution = Unresolved'.
No parameter schema on file.
Create a new version (release) in a JIRA project in the JIRA Data Center edition instance. Use jira_getProjectVersions first to avoid duplicate names.
No parameter schema on file.
Update a JIRA project version in the JIRA Data Center edition instance: rename it, change its description or dates, release it (released=true, usually with releaseDate), or archive it. Only the given fields are changed.
No parameter schema on file.
Delete a JIRA project version in the JIRA Data Center edition instance. This cannot be undone: the version is removed from every issue that uses it, unless moveFixIssuesTo / moveAffectedIssuesTo name another version of the same project to receive those issues. Returns how many issues used the…
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 metadata only unless you pass returnContent: bytes come back as data with 'base64'/'text', and a PNG/JPEG/GIF/WEBP comes back as a…
No parameter schema on file.
Search the system and custom fields of the … by keyword, matching field ids, names and JQL clause names case-insensitively. Returns each field's id, name, whether it is custom, and its schema type. Use it to find a custom field id (e.g. for "Story Points") before reading, setting or querying it.
No parameter schema on file.
List the allowed values of a select, multi-select, radio, checkbox or cascading-select field, as offered when creating an issue of the given type in a project of the …. Also works for system fields with fixed values (priority, components, versions). The field must be on that issue type's create…
No parameter schema on file.
List the fields that can be set when creating an issue of the given type in a project of the …, with whether each is required and its schema type. Get the issue type id from jira_getProjectIssueTypes; for a field's allowed values use jira_getFieldOptions or includeAllowedValues.
No parameter schema on file.
List the issue types that can be created in a project of the … (id, name, description, whether it is a sub-task type). Pass an id to jira_getCreateFields to see the fields of that type.
No parameter schema on file.
List every field that issues of a project in the … can have on creation, merged across the project's issue types, with the issue types each field appears on and those that require it. Makes one request per issue type.
No parameter schema on file.
List all projects visible to the current user in the … (id, key, name, type, category). Prefer jira_searchProjects when you know part of the name or key.
No parameter schema on file.
Find projects in the … whose name or key matches the query, ranked by Jira's project picker. Returns the total number of matches and the matching projects (id, key, name).
No parameter schema on file.
List the components of a project in the … (id, name, description, lead, default assignee type).
No parameter schema on file.
Create several versions (releases) in one project of the …, in the given order. Each version is created separately, so one failure does not stop the others; the result reports the outcome of each. Check existing names with jira_getProjectVersions first.
No parameter schema on file.
Get Xray tests from the … by issue key or JQL, with each test's type, steps or definition, and preconditions. Give keys or jql.
No parameter schema on file.
Get the steps of an Xray manual test in the …: each step's action, data, expected result and attachments.
No parameter schema on file.
List the Xray test executions, test plans, test sets and preconditions an Xray test belongs to in the ….
No parameter schema on file.
List the Xray test run and test step statuses configured in the …, such as PASS, FAIL, TODO and EXECUTING. Use these names with xray_updateTestRun.
No parameter schema on file.
List the tests of an Xray test execution in the …, with each test run's id and status. Pass a test run id to xray_getTestRun or xray_updateTestRun.
No parameter schema on file.
List the tests of an Xray test plan in the …, with each test's latest status across the plan's executions.
No parameter schema on file.
List the Xray test executions of a test plan in the ….
No parameter schema on file.
List the tests of an Xray test set in the ….
No parameter schema on file.
Get one Xray test run from the …, by id or by its test execution and test: status, comment, defects, evidence and step results.
No parameter schema on file.
Search Xray test runs in the … by test execution, test, test plan or saved filter, with paging. Give at least one of them.
No parameter schema on file.
Add Xray tests to a test execution in the …. Each added test gets a test run in the execution.
No parameter schema on file.
Add Xray tests to a test plan in the ….
No parameter schema on file.
Add Xray tests to a test set in the ….
No parameter schema on file.
Add Xray test executions to a test plan in the …, optionally adding their tests to the plan too.
No parameter schema on file.
Record the result of an Xray test run in the …: its status, comment, assignee, linked defects and step results. Only the fields you give change. Read the run with xray_getTestRun first to get its step result ids.
No parameter schema on file.
List the agile (Jira Software) boards on the …, filtered by name, project or type. Returns the board ids the other jira_agile tools take.
No parameter schema on file.
List the issues on an agile board in the …, in board rank order, optionally narrowed by JQL. Returns key, summary, status, type, priority and assignee per issue.
No parameter schema on file.
List the sprints of a scrum board in the …, optionally only those in given states (future, active, closed). Returns sprint id, name, state, goal and dates.
No parameter schema on file.
List the issues in a sprint in the …, in rank order, optionally narrowed by JQL. Returns key, summary, status, type, priority and assignee per issue.
No parameter schema on file.
Create a future sprint on a scrum board in the …. Dates are optional; start it later with jira_updateSprint (state 'active').
No parameter schema on file.
Change a sprint in the …: rename it, set its goal or dates, start it (state 'active') or complete it (state 'closed'). Only the fields you pass change. Closed sprints cannot be edited.
No parameter schema on file.
Move issues into a future or active sprint in the …, taking them out of any other sprint. At most 50 issues per call.
No parameter schema on file.
Move issues to the backlog in the …, removing them from their future or active sprint. At most 50 issues per call.
No parameter schema on file.
Get an issue's created, updated, due and resolution dates from the …, plus its status timeline from the changelog: each status with entry/exit times and duration (the current status is measured up to now and marked ongoing), and total time per status.
No parameter schema on file.
Calculate SLA metrics for an issue in the … from its dates and status changelog: cycle time, lead time, time in status, due date compliance, resolution time and first response time. Optionally counts only working hours (configurable hours, weekdays and time zone).
No parameter schema on file.
Map a project's epics in the …: groups epics under their parent issue (Advanced Roadmaps Parent Link, or a parent field / "is child of" link to another project; the rest under "Unlinked") and lists each epic's child issues via the Epic Link field. Scans up to 500 epics and 1000 children.
No parameter schema on file.
Find issue links from a project's issues to issues in other projects in the …, grouped by target project and link type, with each link's direction, relationship (e.g. "is blocked by") and the target's status. Scans up to 500 issues, most recently updated first.
No parameter schema on file.
Get linked pull requests, branches, commits and repositories for up to … issues at once from the … development panel (dev-status API). Each issue reports its own error, so one failure does not fail the batch.
No parameter schema on file.
List the issues of a project in the …, newest first, with paging. Returns key, summary, status, type, priority, assignee, reporter and dates per issue, plus the total. For other filters or fields use jira_searchIssues.
No parameter schema on file.
Create up to … issues in one request in the …. Each issue is created or rejected on its own: the result lists created issues (0-based input index, key, id) and failed ones (input index, Jira's field errors). Some issues can be created while others fail; never resubmit the created ones.…
No parameter schema on file.
Assign an issue to a user, or unassign it, in the …. Uses the dedicated assignee endpoint, which only needs the Assign Issues permission. Takes a username: resolve names or emails with jira_searchAssignableUsers first. Returns the resulting assignee.
No parameter schema on file.
Permanently delete an issue from the …. This cannot be undone. deleteSubtasks must be given explicitly: with true, the issue's sub-tasks are deleted too; with false, Jira refuses to delete an issue that has sub-tasks. Check the sub-tasks with jira_getIssue first.
No parameter schema on file.
List the watchers of an issue in the …: the watch count, whether you are watching, and each watcher's username and display name. Without the View Voters and Watchers permission Jira may return the count but not the list.
No parameter schema on file.
Add a user, by username, as a watcher of an issue in the …. Adding someone other than yourself needs the Manage Watchers permission. To watch an issue yourself, use jira_watchIssue.
No parameter schema on file.
Remove a user, by username, from the watchers of an issue in the …. Removing someone other than yourself needs the Manage Watchers permission. To stop watching an issue yourself, use jira_unwatchIssue.
No parameter schema on file.
Find the Jira Service Management service desk for a project key in the …. Returns its numeric id, which the other service desk tools need, or serviceDesk: null when the project is not a service desk.
No parameter schema on file.
List the queues of a Jira Service Management service desk in the …, with each queue's JQL and issue count.
No parameter schema on file.
List the issues in a Jira Service Management queue in the …, with the queue's columns as fields.
No parameter schema on file.
List the request types customers can raise in a Jira Service Management service desk in the ….
No parameter schema on file.
Get the fields of a Jira Service Management request type in the …: ids, required flags, schemas and allowed values. Call it before jira_createCustomerRequest.
No parameter schema on file.
Raise a Jira Service Management customer request in the …. Checks required fields and maps select option labels to ids before creating. Returns the new issue key and portal URL.
No parameter schema on file.
Get a user's profile (username, key, display name, email, active state) from the …. Accepts a username, user key, email address, or 'me'.
No parameter schema on file.
Find users who can be assigned issues in a project or on an issue in the …. Use it to turn a name or email fragment into the username that assignee, reporter and watcher fields expect.
No parameter schema on file.
Get all worklog entries (who logged how much time, when, with which comment) for an issue in the …, with the total time logged.
No parameter schema on file.
Log work on an issue in the … as the authenticated user, optionally adjusting the remaining or original estimate.
No parameter schema on file.
Add a web link (any http(s) URL, such as a Confluence page) to an issue in the …. It appears in the issue's Links section. To link two Jira issues use jira_linkIssues instead.
No parameter schema on file.
Put one or more issues into an epic (sets their Epic Link) in the …, using the Jira Software agile API.
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 Dc 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 94 / 100
Release 0.47.1 · scanned 7 Nov 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 score94
Findings2 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest34f00b841e58ef1082334ec2b4df804b9e8942b8b346ec71dbe599e8e76a55c1
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| 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 (78 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>".
20 of the 78 recovered tools are registered only when missingEnvVars.length > 0 is false (dist/index.js:2700) — 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 only the other 56.
1 of the 78 recovered tools are registered only when isVersionDeleteEnabled() holds (dist/index.js:2849) — 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 only the other 56.
1 of the 78 recovered tools are registered only when attachmentGateway.upload.enabled holds (dist/index.js:2859) — 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 only the other 56.
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. high is the level these add up to.
56 tools are registered unconditionally · (1) 20 more only when missingEnvVars.length > 0 is false (dist/index.js:2700) · (2) 1 more only when isVersionDeleteEnabled() holds (dist/index.js:2849) · (3) 1 more only when attachmentGateway.upload.enabled holds (dist/index.js:2859) — typically when a key or option is configured. All 78 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| xray_getTests | no tags | |
| xray_getTestSteps | no tags | |
| xray_getTestRelations | no tags | |
| xray_getTestStatuses | no tags | |
| xray_getTestExecutionTests | no tags | |
| xray_getTestPlanTests | no tags | |
| xray_getTestPlanExecutions | no tags | |
| xray_getTestSetTests | no tags | |
| xray_getTestRun | no tags | |
| xray_searchTestRuns | no tags | |
| xray_addTestsToTestExecution | no tags | |
| xray_addTestsToTestPlan | no tags | |
| xray_addTestsToTestSet | no tags | |
| xray_addTestExecutionsToTestPlan | no tags | |
| xray_updateTestRun | no tags | |
| jira_getAgileBoards | no tags | |
| jira_getBoardIssues | no tags | |
| jira_getSprintsFromBoard | no tags | |
| jira_getSprintIssues | no tags | |
| jira_createSprint | no tags | |
| jira_updateSprint | no tags | |
| jira_addIssuesToSprint | no tags | |
| jira_moveIssuesToBacklog | no tags | |
| jira_getIssueDates | no tags | |
| jira_getIssueSla | no tags | |
| jira_getProjectEpicHierarchy | no tags | |
| jira_getCrossProjectDependencies | no tags | |
| jira_getIssuesDevelopmentInfo | no tags | |
| jira_getUserProfile | no tags | |
| jira_searchAssignableUsers | no tags | |
| jira_searchFields | no tags | |
| jira_getFieldOptions | no tags | |
| jira_getCreateFields | no tags | |
| jira_getProjectIssueTypes | no tags | |
| jira_getProjectFields | no tags | |
| jira_getAllProjects | no tags | |
| jira_searchProjects | no tags | |
| jira_getProjectComponents | no tags | |
| jira_batchCreateVersions | no tags | |
| jira_getProjectIssues | no tags | |
| jira_batchCreateIssues | no tags | |
| jira_assignIssue | no tags | |
| jira_deleteIssue | no tags | |
| jira_getIssueWatchers | no tags | |
| jira_addWatcher | no tags | |
| jira_removeWatcher | no tags | |
| jira_getServiceDeskForProject | no tags | |
| jira_getServiceDeskQueues | no tags | |
| jira_getQueueIssues | no tags | |
| jira_getRequestTypes | no tags | |
| jira_getRequestTypeFields | no tags | |
| jira_createCustomerRequest | no tags | |
| jira_getWorklog | no tags | |
| jira_addWorklog | no tags | |
| jira_createRemoteIssueLink | no tags | |
| jira_linkToEpic | no tags | |
| 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_getProjectVersions conditional (1) | no tags | |
| jira_getVersion conditional (1) | no tags | |
| jira_createVersion conditional (1) | no tags | |
| jira_updateVersion conditional (1) | no tags | |
| jira_deleteVersion conditional (2) | no tags | |
| jira_uploadAttachment conditional (3) | no tags | |
| jira_downloadAttachment conditional (1) | untrusted-input | untrusted-input: keyword "download" |
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 digest34f00b841e58ef10
Scanned2026-11-07
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.47.1. Pin a release below and the command asks for exactly that one.
0.47.1
undated
latestNo release note was published with this version.
—
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 Dc 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.