# Jira — connector pack

Access options in preference order. Probe each in order; use the first that answers. Research of record: `discussions/code-analysis-tools/research-tracker-connectors/02-jira.md` (2026-08-19).

## Option 1 — the official Atlassian Remote MCP Server (Cloud only)

Probe: an `atlassian` entry in `.mcp.json` / Atlassian MCP tools visible in-session.
Setup: `claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp/authv2`, then `/mcp` in-session for the OAuth 2.1 flow. **Cloud only — no Data Center.** Rate limits: 500–1,000 calls/hr by plan.
**Tool names are unpublished by Atlassian** — introspect the live tool list from your session (ToolSearch / the MCP tool listing) before planning calls; expect find/create/update/comment/transition capabilities per Atlassian's own examples.

## Option 2 — community MCP: `sooperset/mcp-atlassian` (Cloud + Server/DC)

The maintained community standard (5.8k★, MIT). Probe: an `mcp-atlassian` entry in `.mcp.json`.
Setup: `uvx mcp-atlassian` with env `JIRA_URL`, `JIRA_USERNAME`, `JIRA_API_TOKEN` (Cloud; token from id.atlassian.com) or `JIRA_PERSONAL_TOKEN` (Server/DC v8.14+).
Confirmed tool names: `jira_get_issue` · `jira_search` (JQL) · `jira_create_issue` · `jira_add_comment` · `jira_transition_issue` · `jira_update_issue` · `jira_get_transitions` · `jira_batch_create_issues`.

## Option 3 — CLIs

**acli** (Atlassian-official). Probe: `acli --version` + an authenticated site. **Namespace is `workitem`, not `issue`.**
`acli jira workitem view KEY-1 --json` · `workitem search --jql "..." --json [--paginate]` · `workitem create --summary --project --type` · `workitem comment create --key KEY-1 --body "..."`.

**jira-cli** (ankitpokhrel, 5.9k★, MIT). Probe: `jira me`. Setup: `jira init` (Cloud: email + `JIRA_API_TOKEN`; DC: PAT + `JIRA_AUTH_TYPE=bearer`).
`jira issue view ISSUE-1 --comments 5` · `jira issue list -q "<JQL>"` · `jira issue create -tBug -s"..." -b"..." --no-input` · `jira issue comment add ISSUE-1 "..."`.

## Option 4 — REST fallback (Cloud v3, v2 for plain text)

Basic auth `email:API_token`. Base `https://<domain>.atlassian.net/rest/api/3/`.
- Read: `GET /rest/api/3/issue/{KEY}`
- **JQL search: `GET /rest/api/3/search/jql`** — the old `/rest/api/3/search` is deprecated and being removed; do not use it.
- Create: `POST /rest/api/3/issue` — **`description` must be ADF** (`{"type":"doc","version":1,"content":[…]}`).
- Comment: `POST /rest/api/3/issue/{KEY}/comment` — body must be ADF.
- **ADF inconvenient → v2**: `/rest/api/2/issue` + `/rest/api/2/issue/{KEY}/comment` take plain-string bodies; v2 JQL endpoint is `/rest/api/2/search`.

## Composing for Jira

Map to the project's real issue types (`Bug`/`Story`/`Task` — list them, don't assume). Set `components` from the owning doc's `module:` where components exist. Atlassian renamed "issue" → "work item" in UI/acli — expect both vocabularies. Leave estimates, sprints, and epic links to humans unless instructed.

## Ecosystem notes (2026-08-19)

No official Anthropic Jira skill. Community skills exist at small adoption (JIRA-Assistant-Skills 42★, two atlassian-skills repos, an acli wrapper) — nothing to defer to; this pack is self-sufficient.