jirac CLI
jirac runs Jira from the terminal: a TUI, a JQL builder, bulk operations and an MCP server for agents in one binary.
- 54 ★ on the repository
- Last commit
Extended access
Why this level
- Jira tokens are stored in profiles and an agent gets access to issues through MCP.
- Bulk operations change many issues at once.
Install
- Works in
Manual install
brew tap mulhamna/tapThen `brew install jira-commands`. MCP server: `brew install jira-mcp`. Other options: `cargo install jira-commands`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Jira tokens are stored in profiles and an agent gets access to issues through MCP.
- Bulk operations change many issues at once.
This is third-party code. Review the repository files before installing.
What it does
jirac, Jira on the command line, offers an interactive TUI with mouse support and a split view: the issue list stays visible while description, comments, worklog, attachments, subtasks and links are open. You can create and edit issues, change type, move between projects, assign, comment, add time and upload files. Profiles store several accounts and deployments, and custom fields are discovered through the API at runtime. There is an interactive JQL builder, bulk comment, transition, update, archive and create operations from JQL, a key list or a JSON manifest, and raw calls to any Jira REST endpoint. `jirac-mcp` exposes Jira to agents and editors as typed tools, and `jirac mcp install` registers it with clients.
Who it is for. Developers and team leads who manage Jira issues and want to do it from the terminal and through an agent.
Good fit when
- You need to bulk comment on or transition dozens of issues from a JQL query.
- An agent reads and creates Jira issues through typed MCP tools.
- One person works across several Jira Cloud and Data Center accounts.
- You need to add time and an attachment to an issue without opening a browser.
Not a fit when
- You use a tracker other than Jira, since the tool is written for Jira only.
- You need protection from accidental bulk edits, as operations act immediately on selected issues.
- You want only a web interface without a terminal.
Example request
Find open Jira issues in project PAY with the release-blocker label, show the list and prepare a bulk comment, but do not send it without my confirmation.Limitations
It needs Jira access: sign-in is `jirac auth login` and tokens live in profiles, so use minimal permissions. Bulk operations change many issues at once, so test the JQL on a safe set before running. The license is stated as MIT and Apache-2.0 together, which GitHub does not reduce to one identifier. The MCP server installs separately from the main command. For Jira Server and Data Center, check that the API methods you need work on your version.
How to disable. Remove the `jirac` and `jirac-mcp` binaries the way you installed them, for example `brew uninstall jira-commands`, and unregister MCP in clients. Clear profiles and tokens separately.
FAQ
How do I install it?
Through Homebrew (`brew install jira-commands`), Cargo (`cargo install jira-commands`), Scoop or winget. Other methods are in `INSTALL.md`.
How do I connect it to an agent?
Install `jira-mcp` and run `jirac mcp install`: an interactive picker checks the binary and Jira sign-in, then registers the server.
Can I use several accounts?
Yes, `jirac auth profiles` lists profiles, `jirac auth use work-cloud` switches and `jirac auth update` refreshes a token.
How are JQL queries built safely?
The builder composes JQL with escaping of user values and rejects control characters and unsafe field names.
What is the raw REST passthrough?
A command calls any Jira REST endpoint when no dedicated command exists. It suits rare operations.
Discussion
No questions or reviews yet.
Related
CLI toolsJira, Confluence, Bitbucket and Jenkins MCP
Sberworks MCP
A local stdio MCP server for self-hosted Jira, Confluence, Bitbucket Server and Jenkins, with mTLS support and write tools disabled by default
A Bitbucket Cloud MCP server with six generic tools that reach any repository or pull request REST API path
A community MCP server for Azure DevOps work items, code and builds, with PAT authentication for on-premises Azure DevOps Server
JetBrains' official TeamCity CLI: start builds, tail logs, check the queue and shell into an agent from a terminal.
A self-hosted MCP and A2A gateway with identity provider integration, access control and observability for enterprise agents
A server-side web job runner with an MCP endpoint: Claude Code runs jobs and workflows, reads their results and answers notes
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| jirac (this card) | no | 54 | ||
| Jira CLI | no | 6,069 | difference: `jira-cli` in Go lacks attachment upload and worklogs, while jirac in Rust adds them plus an MCP server | |
| Jira MCP | no | key is optional | 96 | difference: `jira-mcp` offers only an MCP server, while jirac combines it with a command line and a TUI |
README in short
The README lists features, a comparison with `jira-cli` and `jira-cmd`, install methods, profiles, bulk operations, the MCP server and building from source.