Jira Delivery MCP Server

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.

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.

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.

Install

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

/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:

claude mcp add jira-delivery \
  -e JIRA_BASE_URL=https://your-domain.atlassian.net \
  -e JIRA_EMAIL=you@example.com \
  -e JIRA_API_TOKEN=your-api-token \
  -- npx -y jira-delivery-mcp

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

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:

{
  "servers": {
    "jira-delivery": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "jira-delivery-mcp"],
      "env": { "JIRA_BASE_URL": "https://your-domain.atlassian.net", "JIRA_EMAIL": "you@example.com", "JIRA_API_TOKEN": "your-api-token" }
    }
  }
}

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

{
  "mcpServers": {
    "jira-delivery": {
      "command": "npx",
      "args": ["-y", "jira-delivery-mcp"],
      "env": { "JIRA_BASE_URL": "https://your-domain.atlassian.net", "JIRA_EMAIL": "you@example.com", "JIRA_API_TOKEN": "your-api-token" }
    }
  }
}

In ~/.codex/config.toml:

[mcp_servers.jira-delivery]
command = "npx"
args = ["-y", "jira-delivery-mcp"]
env = { JIRA_BASE_URL = "https://your-domain.atlassian.net", JIRA_EMAIL = "you@example.com", 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

Step	Tools
Start	jira_search_issues · jira_get_issue · jira_prepare_work_brief
Verify	delivery_check_changes · delivery_traceability_matrix
Hand off	delivery_generate · jira_add_comment* · jira_update_issue*
Context	confluence_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