Jira Delivery

io.github.teransarathchandraPublished by GitHub account teransarathchandrav2.0.0Updated Oct 25, 2026

Jira Cloud delivery layer: ticket briefs, acceptance-criteria checks before the PR, QA handoff.

VerifiedSTDIODesktop onlyProductivity & WorkflowKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local Jira Cloud delivery assistant: turns tickets into implementation briefs, checks local diffs against acceptance criteria, and drafts QA handoffs and PRs.

What you can do
Search and read Jira issues, including full parent, epic and linked-issue context, and find relevant Confluence pages and page summaries for specs and runbooks. Turn a ticket into a ready-to-implement brief with goal, acceptance criteria, constraints and an implementation prompt. Compare the local diff against acceptance criteria and Definition of Done, and build a requirements traceability matrix mapping criteria to changed files. Generate test strategies, reviewer reports, QA handoffs, release notes and task reports. Detect and store repository conventions, and write reusable agent prompts or commands into the repository.
When to use it
Use it when you work tickets in Jira Cloud with a coding agent and want a structured start, a pre-PR readiness check against acceptance criteria, and generated handoff or release artifacts.
Requirements
Runs locally over stdio via npx, so Node.js 22+ is needed. Requires JIRA_BASE_URL, JIRA_EMAIL and JIRA_API_TOKEN, plus network access to your Atlassian site. Write tools are only registered when JIRA_ENABLE_WRITES=true; storing project patterns needs DELIVERY_PATTERN_MEMORY_ENABLED=true.
Before you install
The API token is a credential and should be kept in environment variables or secure storage. Write tools (comment, transition, assign, link) are off by default; when enabled they can change Jira issues, though the README says writes are previewed and require approval. delivery_generate_agent_pack and pattern storage write files into your repository. Ticket text is treated as untrusted data.

Installation

In SourceWeft

  1. Open Jira Delivery in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Jira Delivery MCP: from Jira ticket to merged PR without leaving your coding agent]

[npm version] [CI] [Tool-selection evals: 36/36] [Node.js 22 or newer] [MIT license]

An MCP server and agent skill for Jira Cloud. Start a ticket with a ready-to-build brief,
check your branch against its acceptance criteria before the PR, and hand off — from your coding agent.

[Install in Claude Code] [Add to Cursor] [Install in VS Code]

How it works

1 · Start a ticket

"I'm starting ABC-1, get me ready."

Readiness, blockers, acceptance criteria, next steps and a branch name — before you write a line.

[The agent lists open issues, then gets a ready-to-build brief for ABC-1]

2 · Verify before the PR

"Check my branch against ABC-1 before I open the PR."

Your local diff against the acceptance criteria and Definition of Done, with one verdict — ready_for_pr, needs_work or insufficient_evidence — and the files behind each criterion.

[The branch covers one of two criteria, so the verdict is needs_work]

3 · Hand off

"Post the QA handoff to ABC-1."

QA handoffs, release notes, test plans and reviews. With write-back on, the agent shows you a preview and waits for your approval.

[A comment is previewed; nothing changes in Jira until the user approves]

Install

You need Node.js 22+, your Jira Cloud URL, your Atlassian email and an API token.

[Image] Claude Code — plugin with the server and the skill 
/plugin marketplace add teransarathchandra/jira-mcp-server/plugin install jira-delivery@jira-delivery

It asks for your site, email and token (the token goes to secure storage). Without the plugin:

bash
claude mcp add jira-delivery \  -e JIRA_BASE_URL=https://your-domain.atlassian.net \  -e [email protected] \  -e JIRA_API_TOKEN=your-api-token \  -- npx -y jira-delivery-mcp
[Image] Cursor

Click Add to Cursor and replace the three placeholder values, or add the JSON below to ~/.cursor/mcp.json.

[Image] VS Code (GitHub Copilot agent mode)

Click Install in VS Code (or Insiders). VS Code asks for your site, email and token and stores the token as a secret.

Manually: add to .vscode/mcp.json — VS Code uses servers, not mcpServers:

json
{  "servers": {    "jira-delivery": {      "type": "stdio",      "command": "npx",      "args": ["-y", "jira-delivery-mcp"],      "env": { "JIRA_BASE_URL": "https://your-domain.atlassian.net", "JIRA_EMAIL": "[email protected]", "JIRA_API_TOKEN": "your-api-token" }    }  }}
[Image] Windsurf · [Image] Claude Desktop · any MCP client

Add to the client's MCP config — Windsurf: Settings → MCP Servers; Claude Desktop: claude_desktop_config.json:

json
{  "mcpServers": {    "jira-delivery": {      "command": "npx",      "args": ["-y", "jira-delivery-mcp"],      "env": { "JIRA_BASE_URL": "https://your-domain.atlassian.net", "JIRA_EMAIL": "[email protected]", "JIRA_API_TOKEN": "your-api-token" }    }  }}
⌨️ Codex CLI

In ~/.codex/config.toml:

toml
[mcp_servers.jira-delivery]command = "npx"args = ["-y", "jira-delivery-mcp"]env = { JIRA_BASE_URL = "https://your-domain.atlassian.net", JIRA_EMAIL = "[email protected]", JIRA_API_TOKEN = "your-api-token" }

Check your setup: with the three variables exported, npx jira-delivery-mcp doctor verifies the login and prints the custom-field ids your site needs (acceptance criteria, story points, epic). Other agents can add the jira-delivery skill, also attached to each release.

Tools

StepTools
Startjira_search_issues · jira_get_issue · jira_prepare_work_brief
Verifydelivery_check_changes · delivery_traceability_matrix
Hand offdelivery_generate · jira_add_comment* · jira_update_issue*
Contextconfluence_search · confluence_get_page · delivery_project_patterns · delivery_generate_agent_pack

* Opt-in with JIRA_ENABLE_WRITES=true. Every tool returns typed structuredContent; see the tool reference.

Safe by default

  • 🔒 Local and private — runs on your machine over stdio; talks only to your Atlassian site; no telemetry.
  • ✋ Read-only unless you opt in — and then every write is previewed, waits for your approval, is sent once and audited.
  • 🧱 Ticket text is untrusted — fenced as data, scanned for prompt injection, never turned into instructions.
  • 🗝️ Credentials stay in your environment — never logged; redacted from all output.

Documentation

Usage · Tools · Configuration · Security · Troubleshooting · Migrating from 1.x · Changelog

Contributing

Issues and pull requests are welcome — see CONTRIBUTING.md. Security reports: SECURITY.md.

MIT © Teran Sarathchandra

Source: README.md at commit 521a77b

Tools

10

jira_get_issue

Get a Jira issue

Fetch a Jira issue as a developer brief: description, acceptance criteria, comments and attachments. Use depth "full" for parent/epic/linked-issue context and includeConfluence for related documentation. Use this to read a ticket. To start work, check readiness, verify changes or write a report, call jira_prepare_work_brief or the delivery_* tool directly: they fetch the issue themselves.

ParametersdepthissueKeyrequiredincludeConfluence

jira_search_issues

Search Jira issues

List open Jira issues assigned to the authenticated user, optionally limited to one project. Use this to find what to work on next. Pass jql to search with your own filter instead (e.g. "type = Bug AND sprint in openSprints() ORDER BY priority DESC"); it is limited to projectKey when given, and to the allowed projects when the strict allowlist is on. When more results exist, data.nextPageToken is set: pass it back as pageToken for the next page.

ParametersjqlpageTokenmaxResultsprojectKey

jira_prepare_work_brief

Prepare a work brief for a Jira issue

Turn a Jira issue into a ready-to-implement brief for a coding agent: goal, acceptance criteria, constraints and an implementation prompt. Use this when starting work on a ticket, or to check whether it is ready to start (readiness, blockers, missing acceptance criteria). Fetches the issue itself.

ParametersdepthissueKeyrequiredallowElicitationincludeConfluence

confluence_get_page

Get a Confluence page

Read a Confluence page by ID and return a cleaned, size-bounded summary of its content.

ParameterspageIdrequiredmaxChars

delivery_check_changes

Check local changes against a Jira issue

Check work on a Jira issue: does the branch cover the acceptance criteria and meet the Definition of Done? alignment and dod compare the local diff with them — run them before opening a PR. impact predicts the affected areas and works before any code is written, so use checks ["impact"] when planning. Each check runs independently. Returns a verdict (ready_for_pr, needs_work, insufficient_evidence; not_applicable when only impact ran) and per-criterion coverage. Fetches the issue itself.

ParameterschecksissueKeyrequiredrepoPathbaseBranchcompareRefmaxDiffCharsincludeConfluence

delivery_traceability_matrix

Build a requirement traceability matrix

Build a requirements traceability matrix: map each requirement and acceptance criterion of a Jira issue to the changed files that implement it, and flag gaps. Fetches the issue itself. For a ready-for-PR verdict use delivery_check_changes.

ParametersissueKeyrequiredrepoPathbaseBranchcompareRefincludePrDiffincludeConfluence

delivery_generate

Generate a delivery document for a Jira issue

Generate a delivery artifact from a Jira issue and the local diff: test_strategy, reviewer_report (needs persona), qa_handoff, release_notes (audience) or task_report (combined sections). Use test_strategy to plan tests and reviewer_report to review a ticket from a persona's point of view. Fetches the issue itself. Returns Markdown; writes no files.

ParameterstyperequiredpersonaaudienceissueKeyrequiredrepoPathsectionsbaseBranchcompareRefincludePrDiffincludeConfluence

delivery_generate_agent_pack

Write an agent workflow pack into the repo

Write reusable Jira delivery prompts/commands for a coding agent into the repository (claude: .claude/commands and .claude/skills, codex: .codex-prompts/, generic: .mcp-prompts/).

ParametersclientrequiredrepoPathoverwrite

delivery_project_patterns

Scan, read or clear stored project patterns

Detect the repository’s conventions (framework, test layout, tooling) and store them so other delivery tools can tailor their output. scan = detect and store, get = read stored patterns, clear = delete them. Storing requires DELIVERY_PATTERN_MEMORY_ENABLED=true in the server environment.

ParametersactionrequiredrepoPath

Version history

1
  1. v2.0.0LatestOct 25, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts