jira-cli-mcp
Jira Cloud + Confluence Cloud from your terminal — and 103 MCP tools for your LLM agents. One tool, both worlds, pure REST.
- Full practical surface — issues, JQL, sprints/boards/epics, worklogs, attachments, versions, users, identity map, dashboards, workflow maps, XML export, Confluence spaces / markdown pages / two-way file sync.
- LLM-first help — a
helptool over the same docs the package ships; every command and tool discoverable by topic or search (jira help --search). - Policy-guarded writes, managed rate limits — per-project read-write /
read-only policy, token bucket +
Retry-Afterhonoring, visible budget.
Quick start
npm install -g @dawlabs/jira-cli-mcp
jira config init --baseUrl https://yourteam.atlassian.net --email [email protected] --apiToken env:JIRA_API_TOKEN --project DEMO
jira mine # your open tickets — you're rolling
For agents: jira mcp serve --transport stdio --project DEMO — then ask
your client to call help (no args) for the full index.
Why this one
Most Jira CLIs cover a slice; this one aims at the whole practical REST v3
surface with the same core serving humans (tables, --json) and agents (MCP
tools, stdio/HTTP/SSE). Configuration lives centralized in ~/.jcm — nothing
ever lands inside your repositories. Confluence rides the same account, same
binary, same policy guard. Every user-facing error carries a hint and a
stable exit code; markdown ⇄ Jira/Confluence rich text converts both ways
with round-trip tests.
A day in six commands
jira mine --or dana # what's on our plates
jira done --when last-week # what we shipped
jira blocked # what's stuck (Blocked* labels)
jira issue move DEMO-15 --to "In Progress"
jira sprint create -b 7 --name "Sprint 4" --goal "ship 0.2.0"
jira confluence sync push docs/*.md --space DEV
Security & boundaries
- Talks only to standard Jira/Confluence REST APIs with your own API token — never Rovo, Atlassian Intelligence, Forge/Connect, JPD, or any paid endpoint (per-client allow-lists enforce this in code).
- Authorization is policy-only: each registered project declares
{mode: read-write|read-only, allowedAccounts}— no override flag exists. - Credentials stay in
~/.jcm(0600, atomic writes,env:VARindirection, redacted printing). Tokens never appear in logs or output.
Install
npm install -g @dawlabs/jira-cli-mcp # npmjs.org (public)
npm install -g @sikancil/jira-cli-mcp # GitHub Packages mirror
Node ≥ 22.19. Free to use under MIT; distributed as an obfuscated artifact
with full documentation — the readable reference is the shipped docs/
(including docs/help/ and docs/llms.txt for agents).
Docs
jira help · jira help --search "…" — help index ·
CLI reference · MCP setup ·
Confluence · config ·
architecture · XML export ·
llms.txt · CHANGELOG
Developer
Built and maintained by sikancil. The repo is private; issues and pull requests are not open — reach out via the GitHub profile above.