# @aaronsb/jira-cloud-mcp

Model Context Protocol (MCP) server for Jira Cloud - enables AI assistants to interact with Jira

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.11.2
- **Author:** aaronsb
- **License:** MIT
- **npm:** @aaronsb/jira-cloud-mcp
- **Source:** https://github.com/aaronsb/jira-cloud
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-05T18:15:29.843Z
- **Version scanned:** 0.11.2
- **CVEs:** none found by OSV at scan time

## Tools

17 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `backlog_health` — Run a data quality health check on a project backlog — surfaces rot, staleness, and planning gaps
- `project` — Jira project key (e.g. PROJ, ENG)
- `contributor_workload` — Per-contributor workload breakdown with staleness and risk — scopes detail queries to fit within sample cap
- `sprint_review` — Sprint review preparation — velocity, scope changes, at-risk items, and completion forecast
- `board_id` — Jira board ID (find via manage_jira_board list)
- `narrow_analysis` — Refine a capped analysis query — guides you to narrow JQL for precise detail metrics
- `jql` — The JQL query to refine (from a previous capped analysis)
- `manage_jira_filter` — Search for issues using JQL queries, or manage saved filters. Returns issue details (title, status, description). For quantitative questions (counts, totals, ov
- `manage_jira_sprint` — Manage sprints: create, start, close, and assign issues to sprints
- `manage_jira_issue` — Get, create, update, delete, move, transition, comment on, link, log work on, or explore hierarchy of Jira issues. For custom-field writes, consult `jira://capa
- `manage_jira_project` — List projects or get project configuration and metadata. For issue counts, workload, or cross-project comparison, use analyze_jira_issues with metrics: ["summar
- `manage_jira_board` — List boards or get board details and configuration
- `analyze_jira_issues`
- `manage_jira_plan` — Navigate and manage the strategic-to-execution hierarchy. Walks issue trees and Atlassian Goals via GraphQL. Read: analyze rollups (dates, points, progress, con
- `manage_jira_media` — Manage file attachments on Jira issues (remote). Operations here affect Jira — delete permanently removes an attachment from the issue for all users. Use manage
- `manage_workspace` — Manage files in the local workspace staging area (local only — no Jira impact). Files downloaded via manage_jira_media land here. Delete only removes the local 
- `queue_jira_operations` — Execute multiple Jira operations in a single call. Operations run sequentially with result references ($0.key) and per-operation error strategies (bail/continue

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"jira-cloud\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@aaronsb/jira-cloud-mcp\"\n      ],\n      \"env\": {\n        \"JIRA_API_TOKEN\": \"<YOUR_JIRA_API_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `JIRA_API_TOKEN` — Jira API Token (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40aaronsb%2Fjira-cloud-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40aaronsb%2Fjira-cloud-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40aaronsb%2Fjira-cloud-mcp
- HTML page: https://forgeregistry.com/registry/%40aaronsb%2Fjira-cloud-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.