← Index

Jira Delivery

io.github.teransarathchandra/jira-delivery-mcpv2.0.0Productivity & Project Mgmt

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

The current version, v2.0.0, was published to the official MCP registry on 2026-10-24. It is distributed as jira-delivery-mcp on npm, filed under Productivity & Project Mgmt by this index, and declares 4 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Jira Delivery in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Auditable install path →Watch it hold a drift →
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands. The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-25).

Contracts can change after screening, with no version bump. The gate pins Jira Delivery’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
JIRA_BASE_URL
required

Your Jira Cloud site, e.g. https://your-domain.atlassian.net

JIRA_EMAIL
required

Email of the Atlassian account the API token belongs to

JIRA_API_TOKEN
requiredsecret

Atlassian API token

JIRA_ENABLE_WRITES

true to register the write tools (comment, transition, assign, link); off by default

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
15
installability
25
documentation
15
stability
10
Alternatives in Productivity & Project Mgmt
Jira Alerts (JSM Operations)
io.github.rrvrs/jira-alerts-mcp

MCP server for Jira Service Management Operations — alerts, on-call schedules and responders

MagicInterview
io.github.samihalawa/magicinterview

Live interview and meeting coaching with saved context and Notion sync. Audio runs in the full app.

io.github.toolwright-adk/linear-bootstrap
io.github.toolwright-adk/linear-bootstrap

Bootstrap Linear projects from natural language — milestones, epics, issues, and dependencies.